...
=> same of age, education, income
Cookies starting with an @
Here is the meaning on WAM interface audience builder
IDFA = @weboid (not true IDFA)
User Apps = Match @weboid & IDFA
2/ Some cookies starting with @ are not IDFA. => do you have an example ?
in WCM collect, there is a few parameters that can identify a mobile user.
g.ism: is the hit a mobile one
g.did: device identifier
g.dty: device type (1 for Apple, 2 for Android)
Xdevice, Weboid and CRM ID
weboid and crmid
A weboid can be associated to more than one idcrm.
A crmid can be linked to more than one weboid.
user metric
it is an aggregate of unique users. It contains unique IDFA, unique cookies and crm user.
thus, the formula you mention is not necessarly right: Volume (User) <= Volume (cookie + IDFA).
in theory and in most case yes though.
Volume discrepancies Builder and DM WAM file
Datamining files shown users who had activity in the last 24h from the moment datamining run.
Audience monitoring show the number of users added in the audience each hour until 23h.
We can have discrepancies where users shown on datamining and monitoring are not in the the timeframe, and users shown in audience monitoring is only users added in the audience (not removed)
Graph - audience monitoring VOLUME
What does the volume on the audience display on the graph of audience monitoring :
It is cookie plus idfa unique per day with a slight margin of error of 1-3%
Safari collect
Safari is set by default to not collect 3rd party cookies except if user activate this setting.
Client can activate the tracking with WAM tag and setting to "do not track".
adblocker can also have an incident on the collect.
Redirect occurs when client does not have a weborama cookie, redirect to set the cookie.
If it occurs everytime, it is because the client does not accept/store weborama cookie