PRODUCT
Follow

Summary

User falling into Group2B bucket have the retargeting cookie in their browser – i.e even though the cookie was more than 24 hours old, it was still present in the browser when ad was requested. This is not the same as users who are seeing the ad for the very first time (Group1). The effect is that the server was not able to identify a bucket to put users in Group2B into. As a result the server put these users back into the last bucket they fell into when their retargeting cookie was active.

Environment

  • MDX 2.0

Required information

  • Ad ID

Solution

  • Client has setup a mass versioning ad with several versions. All versions are classified into their respective targeting buckets, with the targeting logic defined as follows:

    Group1. If a user is seeing the ad for the very first time (ie they user doesn’t have retargeting cookie), then serve them “Creative Version A”.

    Group2A. If a user who has seen an ad and the retargeting cookie in present in their user agent and the cookie age is less than 24 hours, then serve them “Creative Version B”.

    Group2B. If a user falls into Group2A and their re targeting cookie age is more than 24 hours, the client is expecting that the user gets served “Creative Version A” (i.e same as Group1).

  • Create a separate target audience for users who already have a retargeting cookie and the cookie is more than 24 hours old.

Case Examples

Ticket IDSummary
ID of the ticket Summary of the issue and solution used for this ticket.
ID of the ticket Summary of the issue and solution used for this ticket.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments