User Identification
Adnuntius supports multiple methods of identifying users, both with and without 3rd party cookies. Here you will find an overview that explains how.
Last updated
Adnuntius supports multiple methods of identifying users, both with and without 3rd party cookies. Here you will find an overview that explains how.
Last updated
User identification is an important part of advertising, and conscious usage of methods is important not least because of privacy legislation and concerns, but also to provide a better service to ad buyers. Adnuntius delivers a comprehensive set of ID methods to ensure that users can be identified with and without cookies, combined with controls that ensures that you respect user privacy in accordance with legislation.
This page describes the methods that can be used to either avoid user identification altogether (applies with cookieless ad serving), or to identify them with various data.
The different approaches that Adnuntius uses to read a user identifier are described below, in order of priority. When an identifier is found, it may then (if the user has consented) be written to the user's device. This means, for example, that when a new user is first encountered an identifier may be assigned via Fingerprinting (item 4 below) and then written to a Third Party Cookie. Subsequent requests then may read the identifier via the cookie (item 2 below).
What it is: An external user identifier can be supplied with the ad request. This will always take precedence over any other user identification method.
Required consent (TCF2): None; as a customer you will be able to choose whether or not to send such an external identifier.
How to enable/disable it: The publisher controls this by explicitly including the user identifier in the ad tags on their page.
Used for: Frequency capping, user segment lookup, and unique user counts.
More information:
What it is: Third-party cookies are used to tag and identify users across different publisher domains. Note: third party cookies can be blocked by browser privacy settings, and this is increasingly the default setting in many popular browsers such as Firefox and Safari.
Required consent (TCF2): Purpose 1.
How to enable/disable it: Enabled by default. Can be disabled using the Adnuntius cookieless settings: adn.useCookies(false)
Used for: Frequency capping, re-targeting, conversion tracking and unique user counts.
What it is: Web storage is used to tag and identify users on the same publisher domain.
Required consent (TCF2): Purpose 1.
How to enable/disable it: Enabled by default. Can be disabled using the Adnuntius cookieless setting: adn.useLocalStorage(false);
Used for: Frequency capping, re-targeting, conversion tracking and unique user counts.
What it is: A user “fingerprint” can be generated using identifying information that the browser automatically includes with every ad request, such as the IP address and user agent string. This fingerprint is very effective at distinguishing between requests coming from different locations and devices, but can also provide reasonable accuracy for matching requests from the same user.
Required consent (TCF2): Feature 3 (Purpose 1).
How to enable/disable it: Disabled by default. Can be enabled via a setting in Adnuntius consent.
Used for: Frequency capping and unique user counts.
More information: Work in progress, coming soon.
Adnuntius also offers CRM matching through Adnuntius Data, though it is not part of ad serving. If a publisher and an advertiser are sharing data, then they will each use a different user id when communicating with the ad server. The matching is done when looking up segments, and relies upon Adnuntius having a user id generated via one of the methods above.
More information:
More information:
Read more: