Configure Contentsquare and ABConvert
1
Install and approve the Contentsquare tag
Add the Contentsquare tag to your storefront through the approved Shopify or theme installation path. Confirm the tag ID is approved for the storefront domain and follows your consent policy.
2
Enable Contentsquare in ABConvert
In Integrations, enable Contentsquare. ABConvert uses the existing
window._uxa queue and does not need a separate API key.3
Visit an eligible active test
Use a fresh, consented visitor on a storefront page where the test can assign them. ABConvert sends the dynamic variable after assignment.
4
Verify the dynamic variable
In Contentsquare, inspect the session or use the Contentsquare Tracking Setup Assistant. For network-level diagnosis, Contentsquare documents a
dvar request after trackDynamicVariable runs.What Contentsquare receives
ABConvert sends one dynamic variable for each assigned test.
The key is capped at 512 characters and the value at 255 characters. ABConvert uses a distinct key for each test, so concurrent tests retain separate values. Contentsquare keeps only the last value for a repeated key on the same pageview.
Use cases
- Compare journeys: segment a journey analysis by an ABConvert dynamic variable to see where Control and another test group diverge.
- Analyze zones: filter page analysis or zone metrics by a test group before comparing clicks and scroll behavior.
- Inspect replay context: find a collected session with the dynamic variable before watching a replay for qualitative evidence.
Things to know
- A Contentsquare tag loading on a page is not proof that its project accepts the domain or stored an ABConvert variable.
- Dynamic variables describe an assigned test group. They do not create a purchase event or calculate test significance.
- Do not put personal data in test or test-group names. Dynamic-variable values are sent to Contentsquare.
- Verify in an ordinary eligible browser. Preview and forced-assignment visits are excluded from ABConvert integration tagging.