Integrate Convert with Exatom
Track Convert Experiment and Variation Data in Exatom for Deeper Form Analytics
| Author: | Dionysia Kontotasiou |
THIS ARTICLE WILL HELP YOU:
- Get an Overview
- Understand how the Convert-Exatom integration works
- Review the prerequisites
- Retrieve the Convert experiment and variation IDs
- Make the Convert identifiers available to Exatom
- Retrieve experiment data using Convert's JavaScript API
- Configure custom dimensions in Exatom
- Verify the integration
Overview
Convert.com can be integrated with Exatom to help you understand how different A/B testing experiences affect form performance.
By passing Convert experiment and variation identifiers to Exatom, you can segment form analytics data according to the experiment a visitor experienced.
This allows you to:
- Analyze form completion rates across different experiment variations.
- Identify which variations improve or negatively affect form interactions.
- Understand how changes to page layouts, messaging, and form elements influence form performance.
- Combine experimentation insights with detailed form analytics.
How the integration works
Convert exposes experiment and variation information when a visitor is assigned to an experiment.
You can use this information to pass two identifiers to Exatom:
| Convert identifier | Purpose |
|---|---|
experimentID |
Identifies the Convert experiment |
variationID |
Identifies the variation assigned to the visitor |
Exatom can then use these values as custom segments, allowing you to filter and compare form analytics across experiments and variations.
Prerequisites
Before configuring the integration, make sure that:
- You have an active Convert.com project with an experiment running.
- The Convert tracking code is installed on your website.
- The Exatom tracking tag is installed on the website.
- You have access to the Exatom configuration to create or configure custom dimensions.
Step 1: Retrieve the Convert experiment and variation IDs
Convert assigns visitors to experiments and variations. These identifiers can be used to distinguish which experience a visitor has seen.
You will need:
- Experiment ID: The unique identifier of the experiment.
- Variation ID: The unique identifier of the assigned variation.
Make sure the identifiers are available on the page after Convert has evaluated the visitor's experiment assignment.
Step 2: Make the Convert identifiers available to Exatom
Exatom supports several methods of collecting additional website data, including JavaScript variables, cookies, dataLayer events, and browser storage.
A recommended implementation is to expose the Convert identifiers through the website's data layer and configure Exatom to collect them as custom dimensions.
For websites using Google Tag Manager or a compatible data layer, the implementation can follow this pattern:
window.dataLayer = window.dataLayer || [];
window.dataLayer.push({
event: "convert_experiment_assignment",
experimentID: "EXPERIMENT_ID",
variationID: "VARIATION_ID"
});
Important: The values above are placeholders. They must be populated dynamically using the actual experiment and variation assignment returned by Convert. Do not use static IDs in production.
The code should execute only after the visitor has been assigned to the experiment and the relevant identifiers are available.
Step 3: Retrieve experiment data using Convert's JavaScript API
To populate the dataLayer dynamically, use Convert's _conv_q queue to ensure the experiment data is available before sending it to Exatom.
Add the following JavaScript to your website:
window._conv_q = window._conv_q || [];
window._conv_q.push([function() {
if (window.convert && convert.currentData && convert.currentData.experiences) {
window.dataLayer = window.dataLayer || [];
var experiences = convert.currentData.experiences;
for (var experimentID in experiences) {
var experience = experiences[experimentID];
if (experience.variation) {
window.dataLayer.push({
event: "convert_experiment_assignment",
experimentID: experimentID,
variationID: experience.variation.id,
variationName: experience.variation.name
});
}
}
}
}]);
This implementation:
- Waits for Convert's experiment data to become available.
- Retrieves the active experiment IDs.
- Retrieves the variation IDs and names.
- Pushes the information into the website's dataLayer.
- Makes the data available for third-party tools such as Exatom.
The implementation follows Convert's documented method for accessing convert.currentData.experiences through _conv_q.
Step 4: Configure custom dimensions in Exatom
Once the experiment information is available in the dataLayer, configure Exatom to collect the following custom dimensions:
| Custom dimension | Data source |
|---|---|
experimentID |
experimentID |
variationID |
variationID |
variationName |
variationName |
In Exatom:
- Open your website configuration.
- Navigate to the data integrations/custom dimensions configuration.
- Add the Convert experiment and variation properties as custom dimensions.
- Map the properties to the corresponding dataLayer values.
- Save the configuration and verify that the values are being collected.
Exatom supports collecting custom dimensions from dataLayer events and JavaScript variables. The exact configuration and naming should be confirmed against your Exatom account setup.
Step 5: Verify the integration
After completing the implementation, run an experiment and verify that the correct values are available in Exatom.
You should be able to:
- Identify visitors assigned to a specific Convert experiment.
- Distinguish visitors assigned to different variations.
- Filter form analytics by experiment ID.
- Compare form completion and abandonment rates across variations.
- Analyze field-level performance for each variation.
This allows teams to understand not only which variation generates more conversions, but also which variations provide a better form-filling experience.