Setup
Integration Guide
Everything you need to get set up: tag installation, per-network configuration, and CVR tracking.
1. Installing the tracking tag
Place the tag issued on the dashboard's Setup page inside the head tag of every page on your site. The tag loads asynchronously and does not affect page speed.
Never place two tracking tags on the same page (visits would be double-counted). When you enable CVR tracking, REPLACE your existing tag with the newly issued LP tag.
2. Per-network click IDs (required for per-network reports)
Per-network verdicts and CVR are identified by the click ID appended to your URL when an ad is clicked. Most networks append it automatically — there is usually nothing to do.
| Network | Parameter | What you need to do |
|---|---|---|
| TikTok Ads | ttclid | Nothing (appended automatically on ad click) |
| Meta Ads (Facebook / Instagram) | fbclid | Nothing (appended automatically) |
| Google Ads | gclid | Confirm auto-tagging is ON (default ON — Settings → Account settings) |
| Yahoo! Ads | yclid | Turn ON auto-tagging in the ad console's account settings |
Traffic without a click ID is still attributed via a two-tier fallback (referrer, then utm_source). In-app browsers can strip referrers, so click IDs (auto-tagging) are the most reliable.
3. Enabling CVR tracking (Pro plan and above, optional)
Verify whether the traffic we flag as invalid actually converts. Once enabled, the dashboard shows real-vs-invalid CVR and per-network CVR.
- Setup page → Edit the target site → turn the "Conversion tracking" toggle ON
- Press Save — the toggle alone does not apply the change
- Replace the existing tag on every page with the newly issued LP tag (with data-cvr)
- Place the CV tag (with data-conversion) on your purchase-complete page
The LP tag and CV tag must live on the SAME domain. The tracking cookie is domain-scoped, so a setup where the article LP and the checkout page are on different domains cannot be linked.
CVR tracking uses one first-party cookie (7-day retention, never shared with third parties). Please make sure your privacy policy mentions cookie usage. Bot detection itself uses no cookies.
Test it: open your LP with a parameter such as ?ttclid=TEST123 and proceed to the purchase-complete page — the conversion appears on the dashboard CVR card with its network.