For a full list, see “Supported Activity Types” in Adobe Analytics as the Reporting Source for Adobe Target (A4T).

Do not use the same activity name for two activities from separate workspaces that are using A4T reporting.

Although this is supported when using Target as the reporting source, using the same activity name for two activities is not supported when using Analytics for Target as the reporting source.

For activities using Analytics as the reporting source (A4T), the goal metric uses the “Increment Count & Keep User in Activity” and “On Every Impression” settings. These settings are not configurable.

For more information, see “While configuring my goal metrics, why can’t I access the Advanced Settings options?” in Metric definitions - A4T FAQ.

When an activity is created, Target sends a classification file to Analytics. Although Analytics is capturing and processing the data, it does not show that in the reports until the classification file has been updated. This process can take 24 to 72 hours to complete. If after 72 hours you don’t see your data, contact Client Care. Alternately, if you know you launch an activity, you can create the activity a few days beforehand and the classifications are sent when the activity is saved. That way, data appears in the reports upon launch. Please note that it takes 45-90 minutes for data to be processed in Analytics.

You can change your Reporting Settings options in Administration.

1. In Target, click Administration.
2. In the Experience Cloud solution used for reporting drop-down list, click Select per Activity.

The Reporting Source drop-down list is enabled in the Goal & Settings screen for creating and editing activities.

To always use Analytics as the reporting source, select Adobe Analytics from the drop-down list in Administration.

The following is true assuming the visitorId does not change for a visitor between visits.

If the traffic-allocation percentage is adjusted mid-activity, it’s possible that a visitor could move between targeted and control experiences.

If the percentages are not adjusted mid-activity, a visitor who initially sees the control is always sent to control. A visitor that is sent to targeted experiences is always sent to targeted experiences.

• After being in the targeted “bucket” of traffic, the visitor can be sent to a different experience from visit to visit if the machine-learning models determine that a different experience is relevant for the new visit.
• After being assigned to the control “bucket” of traffic, a visitor will always see the same experience because experience assignment is based on a deterministic pseudo-random hash of the visitor’s visitorId.

You cannot use an Analytics metric with a segment applied as the optimizing goal in an Auto-Allocate activity. As a workaround you can define a Custom Event that achieves the same objective and use that as the optimizing goal metric.