Initial provisioning - A4T FAQ

To implement a basic multi-page A4T use-case:

• Implement the JavaScript libraries for both Target and Analytics on the activity landing URL/page. Implementing both solutions stitches the Target data with the Analytics data for each visitor. This data remains in Analytics until it expires with the default expiration set to 90 days.

• For the remaining pages on the site, where just the Analytics metrics are to be tracked, implement Analytics on those pages. It is not necessary to implement Target on those pages. The Analytics metrics captured across those pages are automatically stitched to the Target activity the user initially qualified for, based on the Target information attached to that visitor from the preceding bullet.

Before a report suite can be selected when defining an Analytics activity, you need both an Analytics user account and a Target user account. Your user accounts must be configured as described in the documentation. See User Permission Requirements.

After you are a member of one or more Experience Cloud groups that have access to Analytics and Target and you have access to all report suites, you should see the option to create an A/B test using Analytics under Create Activity.

If provisioning issues occur, check whether A4T is provisioned correctly.

Check the following if any of these problems occur:

• Make sure that your Analytics and Target accounts are linked in the Experience Cloud.
• Some customers use multiple Analytics company logins in the same Experience Cloud company. If you use multiple logins, make sure that the last Analytics company you logged in to is the one that is tied to the Target account for the integration.
• If you have been logged in to the Experience Cloud for several hours, sometimes the Analytics session can expire. Log out and log back in to try again.