This topic covers some common issues that have been encountered when using Analytics as the reporting source for Target (A4T).
There are several reasons why this could happen:
Classification in Target hasn’t fully processed.
Classification generally takes between 24 and 72 hours to classify reports after the first save.
The report suite doesn’t contain any data, but Target has tried to classify hits. Target cannot classify data until the first hit occurs.
Ensure that the report suite has had at least one hit.
The classification call from Target to Analytics failed.
Contact Customer Care for assistance.
If you break down the “unspecified” row by the “Analytics for Target” dimension and it consists no activity ids, it means everything is classified properly. If activity ids are listed there, then it serves as an indication for a classification issue.
Sometimes data displays correctly in reports, but then reverts back to “unspecified” because a new activity was added that hasn’t completed classification. Remember that it generally takes between 24 and 72 hours to classify reports after the first save.
No data is lost when listed as “unspecified.” The data is properly assigned to the appropriate activity or experience after the classification runs.
There might be an “Unspecified” events row shown in your report, depending on the metric you use to display your data with.
Typically, this row displays if you choose a common metric in the report that is not Target-specific (for example, Page Views, Visits, Unique Visitors, etc). In this case, the “Unspecified” row includes all the Page Views, Visits, and Unique Visitors that are not associated to Target activities.
That row won’t have any Target-associated information (e.g. no visitors, visits, or impressions). For more information, see “Unspecified,” “None,” “Other,” and “Unknown” in reporting in the Analytics tech notes.
If you choose a Target-specific metric in the report, that “Unspecified” row does not display. The only way to avoid having it in the report altogether is to set a Target call on every request sent from that page, which is not common or necessary.
For more information, see Minimizing Inflated Visit and Visitor Counts in A4T.
Lift and confidence details are not available in Analytics. They are, however, available in the Target reports.
A4T activities require an analytics tracking server to be specified. See Using an Analytics Tracking Server to make sure your Analytics Tracking Server is set up correctly.
If you use Adobe Analytics as your activity’s reporting source, you do not need to specify a tracking server during activity creation if you are using mbox.js version 61 (or later) or at.js version 0.9.1 (or later). The mbox.js or at.js library automatically sends tracking server values to Target. During activity creation, you can leave the Tracking Server field empty on the Goals & Settings page.
Make sure you have the right permissions before you start creating A4T activities:
This is a known issue.
Although these metrics are negative, the lift is shown as if they were positive in the Target reports. For example, even though you want a lower bounce rate, the higher bounce rate is shown as the winner with highest lift. Be aware of these and similar metrics, and whether you’d prefer to decrease or increase the numbers, when making decisions based on your reports.
The list of report suites that appears in Target Standard/Premium is the list of report suites that have been configured for Analytics as the reporting source for Target (A4T). This means you might not see every report suite you have.
Also, if you are using multiple reporting sources, the report suites must be present in the default reporting source set in Target as well; otherwise, the reports suites will not display.
If you still don’t see the report suite you are looking for, contact Client Care to get it enabled.
Review your implementation, especially on pages where your visitors qualify for experiences and ensure that the supplemental data IDs match in the Target and Analytics calls.
mboxMCSDIDparameter. In the Analytics call, the supplemental ID is contained in the
experienceCloud.analytics.supplementalDataId. In the Analytics call, the supplemental ID is contained in the
The easiest way to examine the supplemental ID is by using the Adobe Experience Platform Debugger.
If you have not installed the debugger, see Introduction to the Adobe Experience Platform Debugger.
If there is no supplemental data ID in the Target call, confirm that the VisitorAPI.js file is loaded before at.js or mbox.js. If there is no supplemental data ID in the Analytics call, confirm that the Target call fires before the Analytics call.