Guides
  1. tracking-script

Supported Integrations

Overview

The Convert tracking script can send experience and conversion data to 22 third-party platforms. Integrations are enabled per-experience in the Convert UI — each experience can connect to different platforms or different accounts on the same platform.

Supported Platforms

Analytics

PlatformNotes
Google Analytics (GA4)Special handling — sends experience_impression event, supports send_to matching and revenue interception
Google Analytics (Universal Analytics)Legacy GA3 support with custom dimensions
Adobe Analytics (SiteCatalyst)Enterprise analytics
Baidu AnalyticsChina-focused analytics
CNZZChina-focused analytics
ClickyReal-time analytics
EcondaE-commerce analytics
EulerianMarketing analytics
GoSquaredReal-time analytics
Piwik / MatomoOpen-source analytics
WoopraCustomer journey analytics
YandexRussia-focused analytics
YsanceAnalytics

Product Analytics & CDPs

PlatformNotes
MixpanelProduct analytics
Heap AnalyticsProduct analytics
KISSmetricsProduct analytics
SegmentCustomer data platform

Heatmaps & Session Recording

PlatformNotes
HotjarHeatmaps and feedback
Crazy EggHeatmaps and session recording
ClickTaleSession replay
Lucky OrangeHeatmaps and chat
MouseflowSession replay

Tag Management

PlatformNotes
Google Tag ManagerTag management

How Integrations Work

  1. The tracking script waits for the page DOM to be ready (ensuring third-party libraries have loaded)
  2. For each experience the visitor is bucketed into, it checks which integrations are enabled
  3. It formats the experience data (experience ID, variation ID, experience name) according to each platform's requirements
  4. It calls the platform's JavaScript API to send the data

Google Analytics Special Handling

Google Analytics receives dedicated processing because it supports two versions (Universal Analytics and GA4) with different APIs:

  • GA4: Sends an experience_impression event via the dataLayer
  • Universal Analytics: Sets custom dimensions

For details on GA event interception and send_to matching, see the GA Event Interception guide.

What Data Is Sent

Each integration receives:

  • Experience ID — The numeric ID of the experience
  • Variation ID — The numeric ID of the variation the visitor sees
  • Experience name — The human-readable name
  • Variation name — The human-readable name

The exact format varies by platform. For example:

  • GA4: Event name experience_impression with exp_variant_string: "CONV-{experienceId}-{variationId}"
  • Hotjar: Trigger "CONV-{experienceId}-{variationId}"
  • Segment: analytics.track('Experiment Viewed', { ... })

Configuration

Integrations are configured in the Convert UI at the experience level:

  1. Open an experience in the Convert app
  2. Go to the integrations section
  3. Enable the platforms you want to connect
  4. Configure platform-specific settings (measurement IDs, custom dimensions, etc.)

Each experience can have different integration settings. An integration is considered enabled unless explicitly set to disabled.

Notes

  • Preview mode: No data is sent to integrations when previewing an experience. This prevents test data from contaminating your analytics.
  • Missing libraries: If a third-party library isn't loaded on the page, the integration silently skips it. This never blocks other integrations from processing.
  • Timing: Integrations fire after the DOM is ready, ensuring third-party scripts have had time to load.

Updated about 1 month ago