/Docs

Adobe Analytics Integration

The Adobe Analytics integration sends experiment enrollment events to Adobe Analytics using either Adobe Experience Platform Launch (formerly Adobe Launch) or the legacy AppMeasurement library. A vs B auto-detects which library is loaded on your page and uses the appropriate method to send the event.

Setup

1

Go to Project Settings > Integrations

Open your project, click Settings, then click the Integrations tab.
2

Enable Adobe Analytics

Find the Adobe Analytics card and toggle it on.
3

Enter your Report Suite ID

Enter the Report Suite ID (RSID) that you want experiment events to appear in. You can find this in Adobe Analytics under Admin > Report Suites. This is required for the integration to work.
4

Enter your Tracking Server

Enter your Adobe Analytics tracking server (for example, yourcompany.sc.omtrdc.net). This is required for AppMeasurement-based tracking.
5

Save

Click Save. The snippet will begin sending events on the next page load.

Two integration modes

A vs B detects which Adobe library is loaded on the page and uses the appropriate method.

Adobe Experience Platform Launch (recommended)

If your site loads Adobe Experience Platform Launch (which sets window._satellite), A vs B sends the event using the Launch Direct Call rule mechanism:

javascript
1_satellite.track('avsb_experiment', {
2 experiment_id: 'exp_abc123',
3 experiment_name: 'Homepage Hero Test',
4 variation_id: 'var_xyz789',
5 variation_name: 'Variation B',
6 event_name: 'experiment_viewed'
7});

To receive this event in Adobe Analytics, you will need to create a Direct Call Rule in Adobe Launch that fires on the identifier avsb_experiment and maps the data object properties to Adobe Analytics eVars or props.

AppMeasurement (legacy)

If your site uses the legacy AppMeasurement library (which sets window.s), A vs B sends the event as a link tracking call:

javascript
1s.linkTrackVars = 'eVar1,eVar2,prop1,prop2';
2s.eVar1 = 'Homepage Hero Test';
3s.eVar2 = 'Variation B';
4s.tl(true, 'o', 'avsb_experiment');

The exact eVar and prop mapping depends on your Adobe Analytics implementation schema. Contact your Adobe Analytics administrator to determine which variables are appropriate for experiment data.

Launch-based implementation is preferred
If you have both _satellite and s available on the page, A vs B will use _satellite.track() (the Launch method) as the primary mechanism. AppMeasurement is the fallback.
Adobe Launch rule configuration is required
Simply enabling this integration is not enough if you are using Adobe Launch. You must also configure a Direct Call Rule in Adobe Launch to receive the avsb_experiment event and map the data to the correct Adobe Analytics variables. Without this rule, the event will fire but no data will reach Adobe Analytics reports.