Collect Historical Data for AMO IDs and EF IDs for Use in Adobe Customer Journey Analytics

Last update: February 28, 2025

CREATED FOR:

  • User
  • Developer

Advertisers with Analytics for Advertising and Adobe 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 Adobe Advertising and Adobe Customer Journey Analytics, which is Adobe’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 Adobe 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 Adobe Experience Platform into Adobe 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. .

Adobe 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 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.

NOTE
  • As of 28 February 2025, this process tracks click-through data but not view-through data.
  • Processing rules are applied only to new data that’s received. They don’t work retroactively to collect past data.

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 Adobe Advertising in the future.

  1. 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:

        1. Select Overwrite the value of.
        2. Select <the new/unused eVar>.
        3. Select Query String Parameter.
        4. Enter s_kwcid.

        Example: Overwrite the value of rVar10 with Query String Parameter s_kwcid

      • For the EF ID:

        1. Select Overwrite the value of.
        2. Select <the new/unused eVar>.
        3. Select Query String Parameter.
        4. Enter ef_id.

        Example: Overwrite the value of rVar11 with Query String Parameter ef_id

    • For the Reason for rule, use a descriptive note, such as “AMO ID and EF ID will be transported to AEP via Adobe Analytics Connector.”

  2. Validate the saved processing rule.

    Once you save the processing rule, the data for the AMO ID and the AMO EF ID should be identical to the data for the two new eVars to which they are copied.

    For example, if the new eVar eVar142 is mapped to amo.s_kwcid(Context Data), then the data for the eVar142 and the AMO ID should be identical.

For more information about how processing rules are applied, see “How processing rules work.”

Related Articles
Previous pageUsing the Last Event Service JavaScript Library with Adobe Experience Platform Web SDK
Next pageAppend Analytics for Advertising Macros to Flashtalking Ad Tags

Advertising