Keep your libraries updated
Old Experience Cloud libraries prevent you from taking advantage of new features. Also, by not having the latest version for every solution, you increase your risk of having library compatibility issues among Adobe products.
Keep track of your library versions by using the Adobe Experience Cloud Debugger Chrome extension, or by passing your library versions into an Analytics variable.
With Attribution IQ, you can use up to 10 attribution models right in Workspace, and you apply models to any eVar - think search keywords, days of the week, internal campaigns, products, you name it!
And although you can use attribution with any eVar, the most popular use case for using attribution models is still for marketing campaigns. In order to get a complete and holistic view of all the channels bringing users to your site or app, make sure that you have your Adobe Analytics marketing channels set up properly.
Experience Cloud ID syncing
Experience Cloud ID syncing is used to:
- allow for cross device user identification in Audience Manager
- upload offline CRM data into Customer Attributes, in order to use this data in Analytics and Target
If you are using Audience Manager or Customer Attributes, make sure you are declaring your hashed unique user IDs in your implementation.
Profile Merge Rules
The purpose of Profile Merge Rules is to tell Audience Manager which traits to consider when qualifying a person into a segment. Learn more about Profile Merge Rules and how to use them for each one of your use cases.
Configuring your global report suite in Analytics
- Either create a brand new report suite or pick on that has a variable map that suites all areas of your organization
- Set your report suite to timestamp optional
- Review your internal URL filters
- Review your paid search detection rules
- Review your marketing channels processing rules
- Create virtual report suites for your different business units, product teams or channels
Global report suite migration tips
- Make sure variables align across all properties
- Tidy up your variables - ask yourself (or your teams) what business question is being answered by each variable
- Use classifications to group similar data into eVars and then split them up into reporting
- Use the description field in the variables UI to help your users understand what each variable means, when to use it, what makes sense to combine it with.
- Think about how you want to deal with historical data and how to communicate your users.