Integration · JavaScript helper
The click context server-side tracking misses.
The visit begins in the browser, with UTMs and click identifiers in the URL. The helper captures that context and hands it to your server-side events, so attribution knows where each customer came from.
Captures
Everything attribution needs from the landing page.
UTM parameters
Source, medium, campaign, term, and content.
Click identifiers
gclid and fbclid, for matching with Google and Meta.
Page and referrer
Landing URL, current page, and referring site.
Anonymous ID
A first-party identifier used to stitch the visit to a person later.
Installation
Installed by the SDK, or with one line.
Server-rendered Python apps get the helper injected automatically by the SDK. Single-page and static frontends add a one-line script tag.
Either way, the helper sends a heartbeat, and the Instrumentation Health panel shows whether it is live in each environment.
Instrumentation health
Norvelle
| Env | Events | Last heartbeat | Helper |
|---|---|---|---|
| prod | 1.84M | 14s ago | v1.4.2 |
| stage | 42.1K | 6h ago | v1.3.9 |
| test | 8.9K | 52s ago | v1.4.2 |
Illustrative data
See it on your own numbers.
A two-week pilot runs your conversions through Quantiv alongside what you report today. The difference between the two is the business case.