The best practice methodology for migrating from AppMeasurement to AEP WebSDK for Adobe Analytics data collection involves running both implementations in parallel until the AEP WebSDK implementation is fully vetted.
Step 0: Create a copy of your report suite(s)
Go to the Adobe Analytics Admin section and create a copy of the report suite(s) that you presently use for data collection via AppMeasurement (the Adobe Analytics extension in Launch).
This/these new report suite(s) will be used to temporarily collect data via the AEP Web SDK in parallel to data collection via AppMeaurement. Be sure that these new report suites have the same configurations including any processing rules, VISTA, and marketing channel processing rules. By creating this/these new report suite(s), you will be able to run dual data collection in order to validate that the migration is working with full parity. Once you have validated that you have full parity in data collection you can confidently cut over to the new collection mechanism (AEP Web SDK) to your existing report suite(s) and decommission the old collection mechanism (AppMeasurement) with no data continuity issues.
Step 2: Configure Datastream and Schema for AEP Data Collection
Within AEP Data Collection, you will need to create a basic schema in the Adobe Experience Platform (AEP) that supports time-series data and includes the "Adobe Analytics ExperienceEvent" field group. The schema is a structure that defines the data that you want to collect and send to AEP. It specifies the fields (also known as dimensions and measures) that you want to include in your data, as well as their data types and any additional metadata.
To create a basic schema in AEP that supports time-series data and includes the "Adobe Analytics ExperienceEvent Template" field group, you will need to follow these steps:
Log in to the Adobe Experience Platform and navigate to the "Schemas" tab.
Click on the "Create" button to create a new schema.
Give your schema a name and select "Time-series" as the data model.
Select the "Adobe Analytics ExperienceEvent Template" field group from the list of available field groups. This will include common dimensions and measures for Adobe Analytics data, such as page views, visits, and conversion rates.
Click on the "Create" button to create your schema.
After this, you can create your datastream and associate it with the newly created schema.
Step 3: Update Your Apollo Implementation Type
Within Property Settings, update your implementation type from Adobe Analytics (AppMeasurement) to Adobe Analytics (AEP WebSDK).
Saving this change will remove report suite associations with your Apollo environments. You should associate the new test report suites with the Apollo environments and aslo update the Tag Manager Settings within Property Settings to include the new Datastream and schema IDs.
Note: These new report suites will be associated with the implementation only until you are done performing comparative testing between the AppMeasurement and AEP WebSDK implementations. Once testing is complete for all report suites, and you are pleased with data collection, you will replace the test report suites with the standard report suites your AppMeasurement implementation traditionally used.
Step 4: Deploy Your Apollo Implementation
From Deploy > Builds, create a new build and deploy this build to Tag Manager and Data Destination.
This deployment will ensure the following new items are deployed to the existing Launch property:
The Adobe Analytics - AEP Web SDK extension will be installed
The AEP Web SDK extension will also be installed.
Copies of each of your Apollo-managed AppMeasurement analytics rules will be created with the appropriate conditions and rule actions (e.g., Set Variables, Set Product String, Clear Variables, and Send Beacon). These new rules will have actions that use the AA - AEP Web SDK extension instead of the Adobe Analytics or AA Product String Builder extensions. Note the difference in the rule naming convention.
Note: Your old AppMeasurement rules and extensions will still exist in the Launch Property but will no longer be managed by Apollo. This is desired for the period when you are performing comparative testing. Once testing is complete, and you are pleased with data collection, you will disable and remove all AppMeasurement analytics rules and related extensions from the Launch property.
This deployment will also ensure variables are configured in your development report suite.
Step 5: Validate Reporting While AppMeasurement and AEP WebSDK Implementations Running in Tandem
Move the WebSDK implementation items through the standard publishing flow within Adobe Launch and perform the standard testing you perform for analytics tag updates.
It will be most helpful to compare the data that is flowing into your AEP WebSDK test report suite to your AppMeasurement production report suite.
Publish and test with dual collection. (manual)
Compare collected data between suites. (manual)
When satisfied, deactivate the rules that populate AA via appMeasurement. (manual)
Step 6: Deactivate your AppMeasurement Implementation
Replace the test report suite associations in your Apollo Property with your desired production flow report suites. Deploy this change to Tag Manager.
Deactivate legacy rules and extensions in Adobe Launch (ECID, Adobe Analytics, AA Product String Builder, Adobe Target) and publish this change. Validate that data is flowing to the desired report suite via the AEP Web SDK and only via the AEP Web SDK.
Remove legacy, AppMeasurement rules and extensions within Launch. Publish these changes.