Web tracker reference
Install the AttribIQ browser tracker and collect sessions, pageviews, referrers, UTMs, custom events, goals, and checkout context.
The web tracker is the analytics base layer. It captures pageviews, sessions, referrers, UTMs, and local attribution identifiers that can later be passed into checkout.
- Install the browser tracker
- Understand the required script attributes
- Know where the tracker should run
- Connect tracker identifiers to revenue events
The AttribIQ web tracker records the visit context that revenue attribution needs later.
Use it on the pages that influence acquisition and checkout. That normally includes the marketing site, pricing page, guides, signup flow, and relevant app pages.
Script tag
<script async src="https://edge.attribiq.com/i/a7K4mN2qR8tP.js"></script>
The tracker install key maps events to the project. The script sends browser events to the matching edge endpoint.
For first-party loading from your own domain, read first-party tracker proxy.
CSP requirements
AttribIQ uses one browser-facing origin for direct installs: https://edge.attribiq.com.
Add it to the page owner's CSP where scripts and fetch/XHR requests are allowed:
script-src 'self' https://edge.attribiq.com;
connect-src 'self' https://edge.attribiq.com;
The current tracker does not load dynamic third-party scripts, use eval, execute inline code, or send events with image beacons. If your CSP uses nonces and strict-dynamic, the page template must add the matching nonce to the AttribIQ script tag.
Captured context
The tracker captures:
- Page path and hostname.
- Referrer.
- Source and UTM campaign fields.
- Visitor ID.
- Session ID.
- Device, browser, country, and other aggregate dimensions when available.
- Custom events and goals when your app sends them.
Avoid putting raw personal data into page paths, query strings, or custom event metadata.
Browser attribution object
Before checkout starts, your app can read the local attribution object:
const attribution = window.attribiq.getAttribution()
That object is the bridge between browser sessions and payment events. Read the browser attribution API for the expected fields.
Single-page apps
For React, Vue, Svelte, or other client-routed apps, pageviews should be sent when the route changes. If you use AttribIQ's default script, verify route changes in the dashboard after installing.
Next steps
Start with Install AttribIQ. Then connect checkout using Stripe metadata or the Payment API reference.
FAQ
Where should I install the tracker?
Install it on marketing pages, pricing pages, signup pages, and app pages that can influence checkout.
What is the required field?
Use the project-specific script URL from project settings. The install key in the URL maps events to the right project.
Does the tracker create payment events?
No. The tracker captures attribution context. Payment events come from Stripe webhooks or the Payment API.
Can I use the tracker in a single-page app?
Yes. The tracker should record route changes as pageviews when the app navigation changes.
Connect payments to the dashboard
Install the tracker, pass attribution into checkout, and report revenue by source, campaign, landing page, and path.
Related guides
AttribIQ browser attribution API
Reference for reading AttribIQ visitor, session, landing page, referrer, and UTM context before checkout starts.
Payment API reference
Reference for sending custom revenue events to AttribIQ with idempotency, normalized event types, and attribution identifiers.
AttribIQ CLI reports
Run AttribIQ overview, revenue, campaign, goal, and funnel reports from scripts, release checks, and internal tools.