Skip to main content
Set up tracking for the tools your brand already uses before sending campaign traffic. You do not need every integration in this list. Start with your tracking owner’s existing measurement plan.

1. Choose the tool and installation path

Use GA4, Meta Pixel, or TikTok Pixel for their supported direct connections. Use GTM when your team manages those tags in a container. For your existing measurement partners, follow Northbeam, Axon, Polar Analytics, Triple Whale, or Blotout. Shopify Analytics has a separate setup. Avoid installing the same tag through both a native field and GTM or Custom Scripts for the same purpose.

2. Get the required values

Each provider guide explains where to retrieve its ID or URL. The connection-details directory summarizes them. Some integrations use a switch or authorization flow rather than an API key.

3. Save in Jurni

Open Settings → Integrations → Data Integrations. Enter the appropriate IDs under Tracking Pixels and select Save Changes. Complete the separate Shopify Analytics or Triple Whale controls when those are part of your setup. This is a shop-level configuration. The native tracking fields are not a per-page targeting interface. Custom Scripts has separate targeting when your implementation uses that route.

4. Verify the shopper journey

Open the actual campaign link, follow the relevant consent flow, and perform the actions you need to measure. Confirm the events arrive in the intended provider account. Test page activity and the final cart/checkout separately: a PageView alone does not verify a purchase connection. For Shopify Pages, check the installation already present in the theme and apps. For headless/non-Shopify stores, agree the downstream tracking and conversion connection with the Jurni team.

Troubleshooting

If data is missing, check the account/ID, the published URL, consent, browser blocking, and the required event mapping. If it is duplicated, inspect overlapping native fields, GTM tags, theme apps, and Custom Scripts. Jurni’s reported sessions and attributed orders can differ from another platform’s definitions. Use Analytics differences before treating a totals mismatch as proof of broken tracking.