Show Menu
TOPICS×

Reporting FAQ

List of frequently asked questions about reporting in Target.

How are the New Visitors and Returning Visitors metrics counted?

The following information explains how New Visitors and Returning Visitors are counted and provide examples of why the sum of these two segments don't always add up to the number of total visitors.

New Visitors

A visitor is included in the New Visitors segment if one of the following conditions is met:
  • It is the visitor’s first time visiting the site.
  • It is the visitor's first time visiting the site since clearing cookies.
  • It is the visitor’s first time visiting the site since the Visitor profile lifetime has expired.

Returning Visitors

The visitor is included in the Returning Visitors segment if the user previously visited the site, left for at least 30 minutes, and returned to the site again with the same cookies. As long as a visitor returns within their profile lifetime, they will be a returning visitor.
Suppose your profile lifetime is set for 14 days (the default). A visitor is included in the Returning Visitors segment if the following conditions are met:
  • A visitor visits the site for the first time and is recorded as a New Visitor.
  • The visitor leaves the site, but returns six days later.
Because the profile lifetime is set for 14 days, this visitor is included in the Returning Visitors segment. Note that if the visitor has deleted cookies within that six-day period, that visitor will be included in the New Visitors segment.

Examples that explain discrepancies between metric counts

Example 1 : If these two segments are applied to an activity, the New Visitors segment and the Returning Visitors segment do not always add up to the total number of visitors.
Consider the following example, taking in the conditions mentioned above for New Visitors and Returning Visitors:
  • A visitor visits the site for the first time and is counted as a New Visitor.
  • The visitor returns to the site after the conditions are met for Returning Visitors and is counted as a Returning Visitor.
This visitor is counted as a single visitor in the activity’s overall visitor count even though being counted in both the New Visitors and Returning Visitors segments.
Example 2 : Discrepancies between the counts for New Visitors and Returning Visitors also depend on how you configure the activity's success metrics .
For example:
A number of new visitors visit your site and are qualified for an activity. These new visitors are counted towards the New Visitors segment. All of these visitors also recorded a visit into that activity.
Some visitors hit the conversion metric, which was configured as "Increment Count & Keep User in Activity." Suppose some of these users hit the conversion metric multiple times, the conversion metric won't increase. Given that setup, however, some users might hit the conversion metric and then navigate back to the home page, qualifying into the activity again to record a new visit.

Why do my Experience Targeting (XT) reports contain metrics for control experiences?

XT activities should always have a control experience. If you are using an XT activity in a similar manner to an A/B Test activity, which is a fairly common scenario, the control experience data is useful. You can ignore the control experience data if you find it not useful in your reports.

Why are the number of visits lower in Target than in other Adobe Experience Cloud solutions?

Metric numbers, for example visits, reported by Target will always be lower than the reported numbers in other Experience Cloud solutions for a number of reasons:
  • Target counts visits only for visitors that qualified for the activity. Other solutions count visits for visitors that display the page, regardless of which activity brought them to the page.
  • There might be situations where different activities compete for the same location (mutually exclusive). As a result, visitors see different content on a web page, which affects the metric numbers reported by Target.

Why is there no data available for my activity's report?

If an activity's content was successfully delivered to users but its report contains no data, ensure that you have the correct environment ( host group ) selected in the report's settings.
If you have a development environment selected, you might see the following error message: "There is no data available for the selected report settings."
To change the environment for an activity's report:
  1. Click Activities , click the desired activity from the list, then click the Reports tab.
  2. Click the gear icon to configure report settings.
    The gear icon is not available for Automated Personalization (AP) reports.
  3. From the Environment drop-down list, select Production .
    Report data might not be available if you have a development environment selected.
  4. Click Save .
For more information about environments, see Hosts .

Why is the traffic split between my experiences uneven in my A/B or MVT activity?

For example, I set the traffic split to be 50/50 or 25/25/25/25 but I'm seeing a vastly different distribution between experiences in the reporting. There are a number of explainable reasons for uneven visitor counts in Target reporting:
  • When a Target activity is first launched, the traffic distribution might be uneven because of the edge node architecture that Target uses to optimize experience delivery. The best practice is to give an activity some time to collect additional data and the distribution will normalize. For more information on Adobe Target architecture and Edge nodes, see How Adobe Target works .
  • If you are in Target or Analytics and you're using the Visits metric, remember that Target is a visitor-based system and the traffic distribution for an A/B or MVT test is assigned at the visitor level. Thus, if you examine activity results using the Visits metric, the traffic distribution may appear uneven because certain visitors might have multiple visits. Visitors is the standard normalizing metric when evaluating activity performance.
  • The best practice for A/B and MVT tests is to keep traffic splits even. Changing the traffic distribution between experiences (say from 90/10 to 50/50) during a test can lead to uneven visitors across experiences. The lower traffic experience may never "catch up."
  • If you are following the above best practices and the traffic split does not normalize over time, you should check the following:
    • Are you using the latest at.js library? For more information about the current version and associated release notes, see at.js version details .
    • Is it a redirect test? Incorrect timing of tags firing on the page can lead to uneven traffic splits, especially when using Analytics as the data source for a Target activity. For details to remedy uneven traffic distribution on a redirect activity with Analytics for Target (A4T), see Redirect offers - A4T FAQ .