FEDERATED IDENTITY RESOLUTION FRAMEWORK

1 . A federated identity resolution framework comprising:

a federated identity resolution framework email extension;

a unique identifier, the unique identifier being an ESP identifier, where the ESP identifier is associated with a user email in an ESP log, and where the ESP identifier maps the users cookies to the users plain text email;

a single sign-on service provider;

an email, the email having one or more of content or an advertisement URL, one or more of content or an advertisement URL of the mail including the unique ESP identifier;

a web page having a URL, the URL including the unique ESP identifier;

a tag on the web page that collects the unique ESP identifier and the user's first and third party cookies;

where when a user revisits the website, the single sign-on service provider queries the federated identity resolution framework, providing as input the users cookies, and receiving as output the users email address;

and where the website uses one or more of the users email address or cookies to prefill a prompt in the user interface with one or more of the users email address or cookies, such that the user is able to login to the website with a single click and without having to enter their email address.

2 . The federated identity resolution framework of claim 1 , where the website has a verification email sent to the user at the users email address to verify the login.

3 . A federated identity resolution framework comprising:

A centralized unit, a data store that can serve real-time requests, the centralized unit including two portions, a first portion containing raw emails associated with a fp cookie and that can return the raw email of a user when one or more of a cookie and session id is passed as input, and a second portion containing a hashed email address associated with other online identifiers including one or more of: IP, maids, cookies including SSP or DSP 3p cookies, and other identifiers recognized by DSPs that may be generated in real-time such as one or more of UID2 tokens and Ramp ID envelopes;

data governance including identifier opt-outs;

where the framework allows for interoperability between identifiers;

and where the framework allows for the enrichment of data connections.

4 . The federated identity resolution framework of claim 3 , where the real-time endpoints do a two-step look up that connects a hashed email to a unified client identifier, where a unified client identifier is an internal proprietary identifier that represents an app running on a device.

5 . The federated identity resolution framework of claim 3 , where partner specific identifiers are synced to a graph using pixel sync and mapped to a unified client identifier.

6 . The federated identity resolution framework of claim 3 , supporting publishers working with multiple identity providers.

7 . The federated identity resolution framework of claim 3 , where data is acquired by resolving through varied identifiers and sources.

8 . The federated identity resolution framework of claim 3 , including an identity graph for running campaigns in email media.

9 . The federated identity resolution framework of claim 3 , including batch jobs that process logs and create linkages.

10 . The federated identity resolution framework of claim 3 , including cookie cluster unification.

11 . The federated identity resolution framework of claim 3 , including deterministic UID to UID mappings.

12 . The federated identity resolution framework of claim 3 , including user created accounts with two clicks, the first click to request a verification email be sent with a pre-signed URL and the second click being from the email sent for verification which allows the user to sign in upon the second click.

13 . The federated identity resolution framework of claim 3 , where raw emails are linked to first-party cookies on user pages.