[CAMPAIGNS] "Second applicant on same code" issue

[CAMPAIGNS] "Second applicant on same code" issue

Hi Daniel, John

as discussed, I am raising this ticket, so that in a quiet moment (if there ever is one of those) we can have a look at the "Second applicant on same code" issue.

Quick summary of issue:

We know of a couple of occurrences at least, during the Pernod campaign in Australia and now the GO Pro campaign in Russia.
We know it occurs in campaigns where we allow entry of "any" code for entry into the site (usually when serial numbers of participating products are used to take part.
When customers then use non unique numbers to enter the site, it can happen that two applications "merge" into one.
this is visible when looking at the activity log in the back office which will then show duplication of stage such as "code entered on front page"
The second applicant is then not properly logged int he system.
We also know that whilst this has happened, it has also happened that consumer have used a non unique code and received the error message "code already used"
Current example:

gprc4620014322613

Many thanks

Nina

    • Related Articles

    • [CAMPAIGNS] Code entry box not honouring campaign start / stop dates

      Hello Isabella, Yes, the campaign dates issue for when we don't pre-bank the codes is already in this Zoho ticket Kind regards, Daniel --------------------------------------------------------------------- Hi Isabella, (1) only seems to happen for ...

    • [CAMPAIGNS] IMG SLA's

      Nina Ahrens 25 Nov 2019 05:13 PM ( 93 days ago ) Hi Daniel, I believe it was generally for all step 3 applications. With the rebuild this issue may be resolved anyway!? As long as we can make sure that we can define our own SLA’s in the back office ...

    • All about demo codes for multi-tier campaigns

      All about demo codes for multi-tier campaigns [Q1] Can demo codes be created for each tier (and how to do that)? [A1] TODO [Q2] Do the created demo codes *basically* work? [A2] TODO [Q3] Do the demo codes have the normal demo code behaviour (around ...

    • Clarifying the default decline reasons (or "campaign checks")

      I can confirm that the following decline reasons (or "campaign checks") are defaults and are baked into the system: Name check (which is, for example, "Applicant/Passport Mismatch") DOB check (which is, for example, "The age of the participant does ...

    • Discouraged characters in campaign application codes

      Certain characters cause problems when they are used - or input - as part of an application code. The following table lists all known problematic characters and why they are discouraged: CHARACTER DISCOURAGEMENT REASON space internal technical ...