WAM FAQs
- Men-hau Luc (Deactivated)
Retency of Data in builder ?
My Data CS : 30 days
My CRM CS : 395 days
My Media CS : 30 days
Retency of Data in Audience Monitoring ?
Audience: 30 days
Retency of cookie
30 days and can be extended if user profile has been updated
Bootstrap
Limited by account and per day to 20 million users
Gender Attribution
Only the threshold of 10 is considered,
any user with male >= 10 is counted as male,
any user with female >= 10 is counted as female
== users with male >= 10 and female >= 10 are counted as both, and those with male < 10 and female < 10 are counted as none
How is a cookie attributed to the male or female gender ?
this is based on Data science results from Panel of users ( Toluna )
Is the strongest quantile retained for each cookie ?
no, in WAM, for gender, we count all profiles >= 10
== so if a user is quantile 12 male and quantile 13 female, it will be counted 2 in the calculation of the % of the breakdown
If so, how are the cases of equal quantiles handled ?
== both gender are counted one if quantile >10 for both,
if they are below 10 , none is counted in WAM.
=> same of age, education, income
Cookies starting with an @
Here is the meaning on WAM interface audience builder
IDFA = @weboid (= Mobile ID)
User app = Xdevice profile with at least 1 IDFA (this profile can have other IDFA and/or AfficheW)
User Web = Xdevice profile with at least 1 AfficheW (this profile can have other IDFA and/or AfficheW)
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
SFTP connection on File onboarding
When file ingestion has failed on ingesting to the server, another try is done and if this last one fail as well, the server connection will be disabled and a notification is sent to the user (mail link to the setup CRM or Proxy) to inform that the server connection has been disabled and to make proper adjustement.
(TBC by R&D)
When we have several cookies for a same ID CRM, which one is saved ?
only the last cookie detected is associated to an idcrm and up to 5 cookies are in a xdevice grape based on an idcrm
What happens when a cookie is associated with an array of CRM IDs (in the WAM tag) ?
only the first id in the array is stored and used
When ingesting a CRM profile, which cookies are associated with the processed CRM profiles?
the last seen cookie associated to an idcrm plus the xdevice grape
WAM DM VS Audience builder
not the same metric at all.
one counts how many attributions occured in a single day (DM files) while the other is a snapshot of the account at the end of the day (Audience Monitoring).