Pulse Analytics

Pulse is cookie-free web analytics by Ciphera. The tracker leaves nothing in the browser, no cookie and no stored identifier; Pulse works out who a visitor is on its own servers, from rotating hashes. It honours Do Not Track and Global Privacy Control without extra config. The script reference lists every attribute this composable maps.

Proxying is not supported

Pulse builds visitor identity on its server from the connecting IP address and user agent. Route the beacons through your Nuxt server and they all arrive from one IP, so every visitor on the same user agent collapses into a single identity. Its bot filtering counts a datacenter or hosting-provider origin as a signal too, which is where a proxied server sits.

So Nuxt Scripts bundles the tracker and serves it from your origin, but its beacons go straight to the Pulse API. Nothing is lost client-side: the tracker keeps no identifier in the browser for a first-party proxy to shield.

Self-hosted or proxied API

apiUrl sets the origin the tracker posts to. Leave it unset for the hosted Pulse API.

useScriptPulseAnalytics({
  domain: 'YOUR_DOMAIN',
  apiUrl: 'https://pulse-api.example.com',
})

Custom events

Use the composable's proxy object for track calls. Call it before the script has loaded and Nuxt Scripts holds the call, then replays it once the tracker is in. If the visitor has opted out, the tracker never runs and the queue is dropped.

const { proxy } = useScriptPulseAnalytics()
function trackSignup() {
  proxy.track('signup', { plan: 'pro' })
}

const { onLoaded } = useScriptPulseAnalytics()
onLoaded(({ track }) => {
  track('purchase', { product: 'annual_plan' }, 99)
})

Event names may contain letters, numbers and underscores. Property values must be strings, and the optional third argument is revenue. See the custom events reference.

Example

The default trigger waits until Nuxt is ready:

<script setup lang="ts">
useScriptPulseAnalytics({
  domain: 'YOUR_DOMAIN',
})
</script>