Cookie-less requests


This document describes how EmediateAd can handle cookie dependent functionality when cookies are not available in requests.

Typical usage areas

There are some environments where a normal cookie cannot be used to communicate with the user. For example you could have a Flash player that is communicating directly with the ad server or you could have a mobile proxy server that translates the calls from the mobile phones.

Cookie dependent functionality

EmediateAd is using cookies to handle the following situations:

  1. To store a unique id per user. This is used to report on number of unique visitors per campaign, calculate speed of frequency campaigns, etc.
  2. Store frequency targeting data per campaign
  3. Store frequency targeting data per creative
  4. Store frequency targeting data per frequency group
  5. Cache geo data
  6. Store data used to calculate post-impressions and -clicks. Campaigns with post-click logging enabled will be displayed, but no post-click data will be stored.
  7. Store data about which retargeting source campaigns have been seen. The source campaign will be displayed.
  8. Campaign inclusivity, if the content unit tag does not contain a pageviewid.
  9. Campaign exclusivity, if the content unit tag does not contain a pageviewid.

This functionality is lost if the client does not support cookies. However, if you can provide the user-id in the url of each request, you can get the functionality 1-4 above.

Using user-id in the request urls

If the application making the requests to EmediateAd can store a persistent user-id per user, that user-id can be used to replace some functionality that you lose when cookies are not available.

The user-id should be constructed like this:

[Unix-time in seconds][nine random digits]



Here 1235381000 is Unix time, and 999888777 are the nine random digits

To use this user id in the request, you add it like this:


User-id in click urls

EmediateAd will automatically insert the eas_uid value in the resulting click-urls.

Mixing cookie uid:s with url uid:s

If you provide eas_uid in the request url, and the cookie contains a UID, EmediateAd will use the eas_uid from the url.

Frequency capping inside the system

Normally the frequency capping is stored in each user's cookie. If eas_uid is provided in the url, EmediateAd will use an internal database to store campaign frequency per user per campaign, creative or frequency group.

Cxense © 2012 | Support