SECURE CROSS SITE IDENTITY MAPPING
The subject technology includes an identity mapping module that implements a system of networked communications that establish a consent based framework for creating and managing cross site identifiers across multiple publisher websites. The identity mapping module implements a call flow that coordinates multiple publisher sites with an authenticator website and an identity database to create a cross site identifier upon receiving a consent confirmation. The cross site identifier may be stored in local storage of a web client. One or more tags on the publisher website may communicate with the identity mapping module 106 to provide access to the cross site identifiers to enable other publisher websites with access to the authenticator website to quickly access the cross site identifier.
1 . A system comprising:
one or more processors; and
a memory storing instructions that, when executed by at least one processor in the one or more processors, cause the at least one processor to perform operations for exchanging identity data in a cookieless environment, the operations comprising:
sending, in a bid request included in bidstream data published by an online exchange, a first party identifier corresponding to a website of a first publisher, wherein the first party identifier is readable by only the first publisher;
collecting at the website a consent confirmation from a web client, the consent confirmation corresponding to the first party identifier;
displaying an authentication website viewable in the web client, the authentication website generating an encrypted user identifier for the web client;
setting, by the authentication website, the encrypted user identifier as the cross site identifier for the web client;
returning the cross site identifier to the first publisher by recording the cross site identifier in a cross site id storage location of the web client, the cross site identifier used to create a user profile associated with the web client; and
reading the cross site identifier in a cross site id store of the web client.
2 . The system of claim 1 , wherein the encrypted user identifier is generated by collecting the first party identifier from a tag on the website of the first publisher;
passing the first party identifier to an identity graph including one or more identifiers linked to the first party identifier; and
selecting the encrypted user identifier from the one or more linked identifiers.
3 . The system of claim 2 , wherein the operations further comprise decrypting the encrypted user identifier to resolve an email hash associated with the web client;
modifying one or more aspects of an email message based on the user profile; and
sending, using an email server, the modified email message to an email address represented by the email hash.
4 . The system of claim 1 , wherein the encrypted user identifier is generated by collecting the first party identifier from a tag on the website of the first publisher;
passing the first party identifier to an identity graph;
failing to resolve a user identifier for the first party identifier using the identity graph;
encrypting a random user identifier; and
providing the encrypted random user identifier as the encrypted user identifier.
5 . The system of claim 1 , wherein the operations further comprise, collecting by an SSO tag, an impression activity for an email message delivered by an email server, the impression activity navigating the web client to the website associated with the first publisher;
determining an encrypted user identifier associated with the impression activity; and
replacing, on the authenticator site, the random user identifier with the encrypted user identifier; and
resetting the cross site identifier to the encrypted user identifier.
6 . The system of claim 1 , wherein the operations further comprise modifying one or more aspects of the website of the first publisher based on the profile.
7 . The system of claim 1 , wherein the operations further comprise, collecting, using a tag on a webpage of a second publisher, a new first party identifier corresponding to the webpage of a second publisher;
collecting at the website a consent confirmation from a web client, the consent confirmation corresponding to the new first party identifier;
accessing, using an SSO tag on the webpage of the second publisher, the cross site id store of the web client; and
retrieving, from the cross site id store, the cross site identifier.
8 . The system of claim 6 , wherein the SSO tag provides access to the cross site id store by passing the consent confirmation in a call of a storage access API used by the web client to control access to the cross site identifier.
9 . The system of claim 1 , further comprising, passing the cross site identifier to an identity graph to obtain one or more user attributes included in an identity cluster including one or more identifiers linked to the cross site identifier.
10 . The system of claim 1 , wherein the user profile maps the first party identifier to the cross site identifier, the mapping associating one or more user attributes linked to the first party identifier with the cross site identifier.
11 . The system of claim 1 , wherein the operations further comprise, causing, by an SSO tag on the website, a displaying of a pop up UI element on the website, the pop up window including a UI element for inputting the consent indica.
12 . The system of claim 11 , wherein the SSO tag configures one or more styling CSS elements of one or more UI elements in the popup UI element to match the color, font, and style of one or more styling CSS elements of one or more UI elements on the website.