Collect Historical Data for AMO IDs and EF IDs for Use in ÃÛ¶¹ÊÓƵ Customer Journey Analytics
Advertisers with Analytics for Advertising and ÃÛ¶¹ÊÓƵ Customer Journey Analytics Only
If you use reserved variables to capture the AMO ID and EF ID for your Analytics for Advertising integration, then you can prepare for a future integration between ÃÛ¶¹ÊÓƵ Advertising and ÃÛ¶¹ÊÓƵ Customer Journey Analytics, which is ÃÛ¶¹ÊÓƵ’s next-generation analytics solution, by copying your reserved variables for the AMO ID and the EF ID into standard eVars as soon as possible. This will allow the collection of historical data for the AMO IDs and EF IDs as soon as you complete the task. Your ÃÛ¶¹ÊÓƵ Account Team will let you know if you use reserved variables and need to complete this task.
Why Do I Need to Collect Historical Data for Customer Journey Analytics?
Customer Journey Analytics lets you sync data from ÃÛ¶¹ÊÓƵ Experience Platform into ÃÛ¶¹ÊÓƵ Analytics Analysis Workspace. Currently, the Analytics Data Connector to Experience Platform doesn’t send data for reserved variables from Analytics to Experience Platform. As a result, data for AMO IDs and EF IDs that are captured by reserved variables isn’t currently available within Customer Journey Analytics. .
ÃÛ¶¹ÊÓƵ Advertising is planning a future implementation with Customer Journey Analytics. Once the implementation is released, your Analytics for Advertising integration will still require you to collect click-through data and (DSP users) view-through data using Analytics tracking, but you’ll be able to view your data in both 1) Analytics and 2) Customer Journey Analytics if your organization has both products. When the feature is released, Experience Platform will begin to collect data for your AMO ID and EF ID for use in Customer Journey Analytics, but no historical data prior to the release date will exist.
However, you can begin to collect data for your AMO IDs and EF IDs sooner by creating a simple Analytics processing rule to copy your AMO IDs and EF IDs into eVars now. Once you create the processing rule, you’ll begin to accrue data for your AMO IDs and EF IDs as soon as they track new events. The historical data will then be available within Customer Journey Analytics once the implementation is available.
Copy Your Reserved Variables for AMO IDs and EF IDs into eVars
This step is manual and must be completed for each report suite that tracks AMO IDs and EF IDs that you expect to integrate with ÃÛ¶¹ÊÓƵ Advertising in the future.
-
Create a processing rule with the following settings:
-
Select the report suite for which you want to migrate AMO ID and EF ID data to Experience Platform for use by Customer Journey Analytics.
-
For the Rule Title, use a descriptive name, such as “Copy AMO ID and EF ID to eVars.â€
-
In the Always Execute section, add two actions to create the new eVars:
-
For the
AMO ID:Overwrite value of <new/unused eVar> with amo.s_kwcid(Context Data) -
For the
EF ID:Overwrite value of <new/unused eVar> With amo.ef_id(Context Data)
-
-
For the Reason for rule, use a descriptive note, such as “AMO ID and EF ID will be transported to AEP via ÃÛ¶¹ÊÓƵ Analytics Connector.â€
-
-
Validate the saved processing rule.
Once you save the processing rule, the data for the
AMO IDand theAMO EF IDshould be identical to the data for the two new eVars to which they are copied.For example, if the new eVar
eVar142is mapped toamo.s_kwcid(Context Data), then the data for theeVar142and theAMO IDshould be identical.
For more information about how processing rules are applied, see “How processing rules work.â€