How Attribution Works
The Attribution ID (cr_attrib)
Every visitor gets a unique cr_attrib UUID when they arrive on your site. This ID follows them through the entire funnel:
- Page visit — The attribution script generates and stores
cr_attribin a cookie and localStorage - CTA view — GTM fires a
cta_viewevent with thecr_attrib - CTA click — The script appends
cr_attribas a URL parameter on the CTA’s destination link - Form submission — HighLevel captures
cr_attribfrom the URL via a hidden form field - Webhook — HighLevel sends the form submission (including
cr_attrib) back to WisePilot - Join — WisePilot links the form submission to the original CTA click, content asset, and visitor session
The Attribution Script
The script (attribution-tracker.js) runs on your website pages and handles:
- Generating and persisting the
cr_attribcookie - Rewriting CTA links to append
cr_attriband UTM parameters (idempotent — won’t double-append) - Pushing the attribution ID to the GTM
dataLayer - Handling HighLevel iframe forms
What Gets Linked
Once attribution is working, WisePilot can tell you:| Question | Data Source |
|---|---|
| Which content asset did this lead see? | page_path + asset_content_id |
| Which CTA did they click? | cta_id + cta_position |
| Where did the form submission originate? | cr_attrib link to CTA click |
| What was the conversion path? | Full session: view → click → submit |
Privacy
Attribution operates with configurable privacy modes:- Strict (default) — Nulls referrer and click IDs immediately after join
- Standard — Retains data with retention caps
- Debug — Full data retention, auto-expires after 7 days