Sizmek maintains a table with advertiser device IDs and user IDs; this table reflects a history of user IDs retrieved from advertiser device IDs. (In this article, this is the ID table.)
The following list illustrates the steps that Sizmek uses to recognize users on devices or in browser windows.
NOTE: Sizmek does not save any information about users who opt-out of this process.
- If there is an advertiser device ID (for devices such as tablets, smart TVs, and dongles) present on the call to Sizmek servers (using the advertising ID tokens), Sizmek can look up the user ID in the ID table and use it to recognize the user.
- Otherwise, if there is a Sizmek cookie on the page, Sizmek retrieves the user ID from the cookie and uses it to recognize the user.
- Otherwise, Sizmek retrieves the user ID from the device/app caching, if it exists. For example, an app on a mobile device might allow Sizmek to save the user ID in the cache, which Sizmek will use to recognize the user.
- Otherwise, the client collects device data and sends it to the server. The server creates a key from the parameters and tries to match it to a user in the user database.
Note: SizmekDI (device identification) is the name of the technique that identifies a user by device settings.
- Otherwise, Sizmek creates a new user ID and does the following:
- If an advertiser device ID exists, Sizmek inserts the new user ID, with the corresponding device ID, into the ID table.
- If an app cache is available, Sizmek saves the new user ID in that cache for later use.
- If the environment supports cookies, Sizmek sets the new user ID in a Sizmek cookie.