Request inputs on Data Collection tag for AEMaaCS | Community
Skip to main content
S
SrikanthPo3
Level 5
March 10, 2025
Solved

Request inputs on Data Collection tag for AEMaaCS

  • March 10, 2025
  • 1 reply
  • 346 views

Hi Team,

We are working on to move our website from AMS to AEMaaCS in a phased manner i.e. few web pages (in Phase 1) would be rendered from AEMaaCS while the rest of the pages continue to be rendered from AMS. Since we are using/extending the core components in AEMaaCS the analytics datalayer structure is different when compared to datalayer (custom object) in AMS. So that existing data elements and data rules might not work because of change in the datalayer object notation and structure.

I am looking for inputs on whether to create a new Data Collection tag/property for AEMaaCS or use the same one as AMS but create new data elements and data rules to capture data from pages rendering from AEMaaCS from best practices perspective.

Best answer by FarazHusain

Hey @srikanthpo3 

For migrating from AMS to AEMaaCS, you have two main options for Adobe Analytics Data Collection:

  1. Use the Same Data Collection Property 

    • Standardize the data layer across both environments (e.g., use Adobe Client Data Layer).
    • Implement conditional logic within the existing property to handle differences.
    • Ensures centralized management and minimizes duplication.

  2. Create a Separate Property for AEMaaCS

    • Allows tailored tracking for AEMaaCS but requires alignment with AMS data for consistent reporting.
    • More overhead but easier to manage different data layer structures


You can work with developers to understand data layer differences and ensure consistent tracking (eVars, events, etc.) across both properties.

1 reply

FarazHusain
Adobe Employee
FarazHusainAdobe EmployeeAccepted solution
Adobe Employee
March 11, 2025

Hey @srikanthpo3 

For migrating from AMS to AEMaaCS, you have two main options for Adobe Analytics Data Collection:

  1. Use the Same Data Collection Property 

    • Standardize the data layer across both environments (e.g., use Adobe Client Data Layer).
    • Implement conditional logic within the existing property to handle differences.
    • Ensures centralized management and minimizes duplication.

  2. Create a Separate Property for AEMaaCS

    • Allows tailored tracking for AEMaaCS but requires alignment with AMS data for consistent reporting.
    • More overhead but easier to manage different data layer structures


You can work with developers to understand data layer differences and ensure consistent tracking (eVars, events, etc.) across both properties.

    Terms & ConditionsAccessibility statement

    Loading footer...