Integrations
A vs B can send experiment data to the analytics and experimentation tools you already use. When a visitor is enrolled in an experiment, the A vs B snippet forwards the event — including the experiment name, variation name, and any revenue data — to connected platforms. This lets you analyze experiment results inside your existing analytics dashboards alongside all your other data.
How auto-detection works
Most integrations support auto-detection. When an experiment event fires, the snippet checks for the presence of the third-party library on the page — for example, it checks whether window.gtag exists for Google Analytics, or whether window.mixpanel exists for Mixpanel. If the library is found, the snippet sends the event to it automatically, with no configuration required beyond enabling the integration.
If you want to specify a particular account ID or project token (rather than relying on the already-initialized library), you can enter those details in the integration settings.
Where to configure integrations
Integrations are configured in Project Settings > Integrations. Each integration has an enable toggle and optional configuration fields. Enable the toggle, fill in any required fields, and save — the snippet will start sending events on the next page load.
What data is sent
Every integration event includes the following properties:
- experiment_id — the unique ID of the experiment
- experiment_name — the human-readable name of the experiment
- variation_id — the unique ID of the variation the visitor was assigned
- variation_name — the human-readable name of the variation
- event_name — the type of event (e.g., "experiment_viewed")
- revenue — the revenue amount, if applicable