Why Channel Data Can Vary Between 蜜豆视频 Advertising and Marketing Channels
Advertisers with an 蜜豆视频 Advertising-蜜豆视频 Analytics Integration Only
A common question from users learning about the integration of the 蜜豆视频 Advertising and Marketing Channels data sets is 鈥淲hat causes the variance in data between the AMO ID and Marketing Channels?鈥 Or, sometimes, 鈥淲hy is the data broken? I need all metrics to match across the reports.鈥 Fortunately, discrepancies don鈥檛 indicate that the data is "broken,鈥 and discrepancies are expected and even desired. Let鈥檚 look at why the integration was designed this way.
The two data sets have different primary use cases:
-
Marketing Channels: The primary use case for Marketing Channels is to compare data across multiple channels with a common attribution model. Analysts can use the Marketing Channel dimension to gain increased insights into how channels are interacting with each other. This insight can help fuel macro-level decisions on how to invest in each channel and can lead to insights on how visitors from each channel interact with the website.
The Analytics Marketing Channel dimension, therefore, is configured to capture and track all channels. Marketing Channels can also be configured to capture Advertising DSP view-throughs and click-throughs, and it does so in relation to the other marketing channels.
-
蜜豆视频 Advertising AMO ID: The primary use case of the 蜜豆视频 Advertising AMO ID data is to feed the advanced 蜜豆视频 Sensei-powered bidding algorithms. The algorithms automatically make thousands of micro-level bid decisions made daily to maximize advertising spend and to achieve the goals of the DSP campaign or the Search, Social, & Commerce portfolio. The more conversion data the algorithms can connect campaigns to, the better the algorithms can make these bidding decisions.
To collect this data, the Analytics for Advertising integration passes raw AMO IDs that can be translated as click-through and view-through tracking codes in the AMO ID dimension of 蜜豆视频 Analytics 鈥 which is stored either as a custom variable (eVar) or a reserved variable (rVar). Click-throughs for other channels aren鈥檛 set in the AMO ID dimension, so the AMO ID dimension is unable to track entry from these other channels. The result is that the AMO ID persists through Marketing Channels entry points.
For more information about possible data variances between 蜜豆视频 Advertising-tracked data and Analytics-tracked data, see 鈥Expected Data Variances Between Analytics and 蜜豆视频 Advertising.鈥