Adobe Analytics Integration
A vs B sends your experiment data to Adobe Analytics through Adobe Experience Platform Launch, which is already running on your page. There is no report suite ID or tracking server to paste in: if window._satellite.track is there, we talk to it. Events land in whichever report suite your existing Adobe setup uses.
Setup
Go to Project Settings > Integrations
Open your project, click Settings, then open the Integrations tab.
Turn on Adobe Analytics
Find the Adobe Analytics card and switch it on.
Choose anything else you want sent
Under Also send, tick conversions, purchases, or recommendation events. Experiment views are always sent.
Create a Direct Call Rule in Adobe Launch
This step is not optional. See below.
Save
Click Save. Your changes reach your live site within about a minute.
- The on/off switch, top right of the card.
- The Also send checklist for conversions, purchases, and recommendation events.
What is sent
When a visitor is shown a variation (one specific version being tested, the control or one of the challengers):
// `_satellite` is the global the Adobe Launch embed installs on the page.declare const _satellite: { track(name: string, detail: Record<string, unknown>): void };_satellite.track('avsb_experiment_viewed', { experiment_id: '482', experiment_name: 'Homepage hero', variation_id: '1913', variation_name: 'Variant B', event_id: '3f9a2b1c-7d4e-4a58-9c02-5e6d1f8b3a47'});| Event | Default identifier | Extra fields |
|---|---|---|
| Experiment view | avsb_experiment_viewed | none |
| Conversion | avsb_goal | goal_key, plus revenue or value when you sent one |
| Purchase | avsb_purchase | revenue, currency, transaction_id |
| Recommendation seen | avsb_rec_impression | the recommendation details, such as recipe and items |
| Recommendation clicked | avsb_rec_click | the recommendation details, such as recipe, item, and position |
Empty fields are left out rather than sent as blanks.
A conversion carries the same five fields, plus the goal it belongs to:
_satellite.track('avsb_goal', { experiment_id: '482', experiment_name: 'Homepage hero', variation_id: '1913', variation_name: 'Variant B', event_id: 'b2a7e6c4-1f3a-4d8e-9b02-8c4a2e7f19d0', goal_key: 'click:31'});goal_key identifies which goal fired. For a metric you built in the metric builder, it is the metric's type and short ID joined by a colon, like click:31. For a custom event you track yourself, it is just your event's name. Add revenue or value here too, whichever one that goal was set up to send.
Set up the Direct Call Rule
Adobe only records what your Launch property tells it to. Without a rule, the call above fires and nothing reaches your reports.
Create a rule
In your Launch property, go to Rules > Add Rule and name it A vs B experiment view.
Add a Direct Call event
Under Events, choose Core > Direct Call and set the identifier to avsb_experiment_viewed.
Create data elements
Add a data element for each field you want to keep. Each one is Core > Custom Code returning event.detail.experiment_name (and the same for variation_name, experiment_id, variation_id, and event_id).
Map them to eVars
Under Actions, add Adobe Analytics > Set Variables and assign your data elements to eVars. Most teams use one eVar for the experiment and one for the variation.
Send the beacon and publish
Add Adobe Analytics > Send Beacon and publish the library. Repeat with a rule per identifier for anything else you switched on.
Sending the ID as well as the name means you can classify on the ID in Adobe and keep reports stable even after an experiment is renamed.
Renaming events
Every identifier in the table can be changed on the card. Leave a box empty to keep the standard one shown inside it. If you rename one, update the matching Direct Call Rule at the same time, or the events stop being picked up.
Turning it off
Switch the Adobe Analytics card off to stop sending to Adobe entirely. To keep it on for every other experiment but skip just one, use the Analytics forwarding switch on that experiment's review step instead.
Check it works
On the Integrations tab, use Send a test event. It opens your site in a new tab and sends one clearly labelled test event, avsb_test_event, to every tool you have switched on. Adobe Launch's debugger shows the direct call arriving. Your project needs at least one live experiment first: the test event is sent against the first one you have.
A vs B talks to Adobe through Launch only. Sites running the older AppMeasurement library on its own (window.s, without Launch) do not receive experiment data. That path's link tracking call could not carry the experiment and variation fields, so it delivered almost nothing. If you are in that position, move to Launch. Or send the events yourself from the event bus, setting your own eVars before your beacon.