1 / 7

Creating a User ID

Creating a User ID. (1) User makes any HTTP request. (2) Server creates unique user ID. (3) Web server responds, storing the user ID in a cookie. Website.com.

thor
Télécharger la présentation

Creating a User ID

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Creating a User ID (1) User makes any HTTP request (2) Server creates unique user ID (3) Web server responds, storing the user ID in a cookie. Website.com A different ID set for each user, browser, login, and device, from each domain, which means the typical user has 100’s of cookies.

  2. Opt Out (1) User visits Web site Opt-Out interface. (2) Web server sets specific Opt-Out cookie. (3) User visits a 3rd party’s Opt-Out interface (4) 3rd party sets a specific Opt-Out cookie Website.com Coordinator 3rd party (5) [Optional] A coordinator like the NAI or DAA Opt Out system can instruct a web browser to make Opt-Out requests to all participating domains.

  3. Data Flow – Client and Server (1) Any HTTP request within a cookie-compliant client results in [previously set] cookies appended to that request (2) Server reads the cookies sent in the request (3) Web server can optionally respond with more cookies, or add/edit/delete the information within a cookie Website.com Modern browsers can store as much as 4093 bytes per cookie, and that data may only be read by the domain setting the cookie.

  4. ID Sync (1) User visits Web site (2) Web/ad server reads cookie, responds with a redirection to a 3rd party. (3) The redirection contains an ID from website.com in the URI-Query. (4) 3rd party reads their cookie & the website.com ID, associating these server-side. Website.com 3rd party

  5. Cookie/ID Accessed at Run-Time (1) User visits Web site (2) Web/ad server reads cookie, responds with page (ad tag). (3) Ad tag on Web page makes ad request to 3rd party (4) 3rd party reads their cookie & user ID, then serves ad targeted and fcapped to that user. Website.com RTB 4th party 3rd party (5) [Optional] 3rd party sends bid request to RTB 4th party with the 4th party’s user ID in the bid request (3rd and 4th party previously synced IDs), so they can match to a targeted ad, fcap, etc.

  6. Data (1) User visits Web site (2) Web/ad server sets a cookie. Because cookies are sent on every HTTP request, it’s best to keep them as small as possible, using them to store an ID that can look up more information on the server. Modern browsers can store as much as 4093 bytes per cookie, and that data may only be read by the domain setting the cookie. Website.com

  7. Market Coverage

More Related