The Adobe Target-to-Adobe Analytics integration, known as Analytics for Target (A4T) supports Auto-Allocate and Auto-Target activities.
The A4T integration lets you:
Make sure you have implemented A4T for use with A/B Test and Experience Targeting activities. If you are using analyticsLogging = client_side
, you must also pass the sessionId
value to Analytics. For more information, see Analytics for Target (A4T) reporting in the Adobe Target SDKs guide.
To get started:
While creating an A/B Test activity, on the Targeting page, select one of the following options as the Traffic Allocation Method:
For more information and step-by-step instructions, see Create an Auto-Allocate activity and Create an Auto-Target activity.
Select Adobe Analytics for your Reporting Source on the Goals & Settings page and select the report suite corresponding to your desired optimization goal.
Choose a Primary Goal metric.
See Supported goal metrics below for more information.
Save and activate your activity.
Auto-Allocate uses your selected metric to optimize the activity, driving visitors to the experience that maximizes your goal metric.
Or
Auto-Target uses your selected metric to optimize the activity, driving visitors to a personalized best experience.
Use the Reports tab to view your activity’s reporting by your choice of Adobe Analytics metrics. Click View in Analytics to dive deep and further segment your reporting data.
A4T for Auto-Allocate and Auto-Target let you choose any of the following metric types as your primary goal metric for optimization:
A4T for Auto-Allocate and Auto-Target requires you to choose a metric that is based on a binomial event. A binomial event either does or does not happen. Binomial events include a click, a conversion, an order, and so forth. These types of events are also sometimes referred to as Bernoulli, binary, or discrete events.
A4T for Auto-Allocate and Auto-Target does not support optimization for continuous metrics. Continuous metrics include revenue, number of products ordered, session duration, number of page views in session, and so forth. These unsupported types of metrics are also sometimes referred to as non-binomial or non-Bernoulli metrics.
The following metric types are unsupported as primary goal metrics:
Adobe Target engagement and revenue metrics
Adobe Analytics engagement and revenue metrics
It is possible to select an Analytics engagement or revenue metric as your primary goal metric because Target cannot identify and exclude all engagement and revenue metrics from Analytics. Select only binomial conversion metrics or custom events from Analytics.
Adobe Analytics calculated metrics
Some limitations and notes apply to both Auto-Allocate and Auto-Target activities. Other limitations and notes apply to one activity type or the other.
For more information, see Attribution models and lookback windows in the Analytics Tools Guide.