Frequently Asked Questions About Analytics Integration (Deprecated)

Several questions about the integration between Target and Analytics surface often.

As of April 17, 2014, the information in this section has been deprecated, and is replaced by the Adobe Analytics as the Reporting Source for Adobe Target functionality. Adobe is continuing to support the former integration methods, but it is recommended that you use the new functionality.

How much does this integration cost?

There's no charge for this integration, although professional services fees apply should they be required.

With what variables can I subrelate campaigns and experiences?

You can subrelate with the variables listed below. Consult with your account representative about enabling further subrelations.

  • Monitor Resolutions
  • Search Engines
  • Search Keywords
  • Referring Domains
  • Time Spent on Site
  • Visit Number
  • Products
  • Pages
  • Your choice of 5 custom eVars

Do I need to use one of my custom eVars towards this integration?

No, the integration does not use one of your custom eVars.

Can I correlate Target campaign and experience data with traffic variables?

No, Target campaign and experience data behave like conversion variables (eVars), and therefore can't be correlated (with props, for example).

Can I perform pathing analysis with Target campaign and experience variables?

No, pathing reports are not possible at this time.

Can I perform analysis in Analytics with data from my Target MVTs (multivariate tests)?

You can analyze the experiences explicitly defined in the MVT campaign definition, but Analytics does not provide information about best predicted experiences or element contribution.

Can I analyze my Target-defined segments in Analytics?

No, segments explicitly defined in your Target campaign definition are not available in Analytics. Of course, you can break down your campaign and experience traffic with Analytics variables.

Comparing my reports in Target and Analytics, I notice that my conversion data differs for the same campaign. Why?

Reports in Target show performance based on the conversion mbox selected when defining the campaign, but this conversion mbox data is not sent to Adobe Analytics, which has its own conversion variables as defined by your Analytics tagging implementation. In cases where you may expect identical data (for example, if a retailer's order confirm page contains both a conversion mbox and an Analytics purchase event), data may differ due to the placement of these tags. In general, trends in the two products' reports should be the similar. See Understanding Expected Data Variances for more information.

Why is it that when I look at my page's generated JavaScript, I see numbers with a format like "s_tnt=1323,1,0" instead of my campaign and experience names?

Target serves the ids of the campaign and experience, rather than the human-readable names. Iif you examine the special integration offer, you can infer that ${campaign.id} and ${campaign.recipe.id} are replaced by the campaign and experience ids, respectively. The traffic type is also included (${campaign.recipe.trafficType}), but there's no need to pay attention to that. Target assigns this data to a global variable named s_tnt, which the s_code.js later assigns to the s.tnt reporting variable before sending it along with other data to the analytics reporting server. Behind the scenes, Target sends classification files to analytics reporting, which perform the mapping. With this strategy, changes to the campaign or experience name in Target are automatically updated in analytics reports.

The integration with Analytics uses something called a "tntvar." Is this variable available all the way through into Analytics?

The tntvar is in the raw data warehouse files. However, it is not available in the Analytics user interface. You can always get at data in a data warehouse report, even if it is not available directly in Analytics by using a VISTA rule to copy the value to an empty prop or eVar. The "tntvar" contains raw data and is not available in reports, but other Target reports are available (campaign, campaign > recipe, recipe, etc.).