For some traits, I'm seeing that the unique visitor volume in Audience Manager is as low as 50% of the volume that we're seeing in Adobe Analytics. Is that normal or does that seem to low? I know that AAM doesn't accept visitors with 3rd party cookies, so I'm sure the discrepancy varies by industry.
Are there any other reasons besides tagging mistakes and 3rd party cookies as to why there would be a discrepancy?
Thanks in advance,
Yes, you can use d_rs variable and create a trait using this signal to filter users from a specific report suite.
For more info on this variable check this :
https://marketing.adobe.com/resources/help/en_US/aam/c_profiles_audiences.html there are no limitations on using it with other AA signals or AAM signals.
If we have set up server-side forwarding, and if I can see an event (e.g. prodview) has been tracked in Adobe Analytics but after I created a trait using that event, it has been returning 0 in AAM. What could be the reason of that?
Thank you for the confirmation!
I used c_events that contains "prodview", cart addition and purchase events all work fine.
Also, is "d_rs" the one to use when I want to include data from only one specific reporting suite. It is in the unused signal report and the "unique" look fine after i used it to create traits and segments in AAM. Are there any limitations when using it with others such as c_evar, c_prop, c_events, etc?
Did you use c_ in AAM while creating trait with that Analytics variable ? Example : c_evar21 or c_prop20 in AAM ?
Are you seeing that variable in unused signal reports ? Did you create that as a rule based trait ?
After creating a trait, it takes 3-4 hours for that trait to become active, and the reporting of that trait starts showing after 24 hours.
Since question is mainly related to Adobe Audience Manager. I'm moving this question to AAM community.
Feel free to ping us if there are some doubts about the difference between AAM uniques and Analytics unique visitors.
There could be a number reasons. I'll list a few below:
The Marketing Cloud ID service (likely to be changed to the Experience Cloud ID service) is helping to combat some of these difference. Before we had MCID, each solution identified a visitor or user in a different way. It's best not to compare these numbers to each other. If you want a better representation, try looking at numbers after you've deployed MCID.