Campaign exclusivity

Exclusivity without cookie dependence

The inclusivity and exclusivity functions of EmediateAd have been completely rewritten to allow for better scaling and more predictable behavior under high traffic. The new functions also allow for inclusivity and exclusivity even when the user does not have a cookie set.

What do I need to do to get the best out of the new exclusivity and inclusivity?

You need to add a new parameter to your Emediate tags. This parameter is called “pageviewid” and

  • all tags on the same page must have the same ID (pageviewid)
  • all page reloads must generate a new, unique ID (pageviewid)

Example

Bob visits a web site. There are three banners on the front page: cu 1, cu 2 and cu 3.

The page source looks like this:

<script
src="http://eas.emediate.eu/eas?cu=1;pageviewid=aaaaaa;js=y"></script>
<script
src="http://eas.emediate.eu/eas?cu=2;pageviewid=aaaaaa;js=y"></script>
<script
src="http://eas.emediate.eu/eas?cu=3;pageviewid=aaaaaa;js=y"></script>

Bob reloads the page. Now the page source looks like this:

<script
src="http://eas.emediate.eu/eas?cu=1;pageviewid=aabaaa;js=y"></script>
<script
src="http://eas.emediate.eu/eas?cu=2;pageviewid=aabaaa;js=y"></script>
<script
src="http://eas.emediate.eu/eas?cu=3;pageviewid=aabaaa;js=y"></script>

A function EAS_uuid() is available in EAS_tag.1.0.js to generate a UUID to be used as page view ID.

Read more about the Pageviewid functionality here

What happens if I don't add a pageviewid parameter?

For a while longer, inclusivity and exclusivity will keep working as it does today - only for users with cookies and with a less predictable way of deducting if the user has moved to a new page.

The eas_uid in the request (through cookie or in the tag) will be used as a session id.

For composed javascript request: eas_uid + current time as a session id

Otherwise: eas_uid as session id

As you can see, the system calculates the session id differently in a composed javascript tag than in another type of tag. Therefore if composed javascript tags are mixed with other types of tags, the requests will get different session ids and will not check each other for inclusivity/exclusivity. Using a combination of composed javascript and other tags will work if you use pageviewid.

A session has a lifetime of 15 seconds. After that it is removed, the system assumes that if two ads were loaded within a longer time, they probably don't belong to the same page and should not consider inclusivity/exclusivity between each other. (This cannot happen if the ads are in the same composed javascript tag.)

In the future we will remove the possibility to use inclusivity and exclusivity without the pageviewid parameter.

Cxense © 2012 | Support