Outbound Check Failed - Coupon Code Redeemed

[vervinckt_joyca]

Hi all,

I've been doing tests with Offers & Coupons, but have the following strange behavior. I can't find much documentation about it.

When using "multi-coupon-codes", when I make an email with this offer and send it to person X, he gets code ABC, and person Y gets code DEF.

If I send the campaign again to both persons, they get their exact same codes again, person X still gets ABC, person Y gets DEF (which is fine).

If person X uses his code ABC (Offer Redemption interaction came in), if I then send the campaign again, I get an "Outbound Check Failed - Coupon Code Redeemed" interaction. Which is also great.

However, this is different when using Single Codes.

I have a coupon with a single code, with setting Redemption Limit for Each Contact 1.

Same scenario, I send this Offer/Coupon to person X and Y, both now get CODESINGLE.

But when adding an Offer Redemption for person X,

and then sending the campaign again, there is just an Outbound email, instead of an "Outbound Check Failed - Coupon Code Redeemed".

I would have expected a failed send, because this offer can only be redeemed once according to its settings...

Is this normal behavior, or could this be a bug?

Kr

Joyca Vervinckt

[vervinckt_joyca]

Hi,

From the ticket with SAP Support, we finally found the issue:

Authorizations

Background:

Coupon management holds a DB table ("usages") where it stores which interaction contact received which coupon code. This table also holds a redemption counter that is increased when you post a redemption interaction. Figuring this counter out of the interaction table would be too time consuming during campaign execution runtime, so we store it redundantly. And this counter is used to find out if the redemption limit for a interaction contact has been reached during campaign execution runtime. In your case, the redemption interaction somehow doesn't increase this counter, and so the campaign execution doesn't know that the redemption limit has been reached.

This Counter can be checked via:

https://<yourserver>/sap/opu/odata/SAP/API_MKT_COUPON_SRV/CouponCodeUsages?$select=InteractionContac... eq (guid'00163e54-d8b1-1ee9-9df7-e98ee95eff32') and CouponUUID eq (guid'00163e54-d8b1-1eea-85a2-a55ab2cc7cb4')&$top=10

Turned out that our interface user had only authorization on the Communication Arrangement for Interactions,

and he needed access to the Communication Arrangement for Coupons additionally.

And in my earlier tests with multi coupon codes, I was using another user for testing from Postman, while later we started testing with the actual interface system with another user.

[guipaulino]

Hello vervinckt.joyca,

What type of scenario are you using? "Single Coupon Code and No Contact Assigned" or "Single Coupon Code and Contact Assigned Dynamically"

If you are using a 'no contact assigned' scenario, the 'Redemption Limit' will limit the number of redemptions in an offer, which means the e-mails and code can sent multiple times but only 1 redemption can be created (either for contact X or Y). In this scenario, contacts are able to use the code more than once, but since you have a limit for 1, then the redemption cannot be created more than once. If this is happening then there really might be a bug.

For the 'contact assigned dynamically' scenario it works a bit different. I am sure you have read this.

If you do create a ticket for a SAP I will love to hear what they have to say, too!

BR,

Guilherme.

[vervinckt_joyca]

Hi,

I'm using "Single Coupon Code and Contact Assigned Dynamically".

I'm not using the overall "Redemption Limit", only the "Redemption Limit for Each Contact" which is 1.

I didn't test whether or not I can add a second "Offer Redemption" interaction for person X, my problem occurs earlier, being that an email containing this offer does get sent a second time to person X, while the setting sais he could only redeem it once and he already redeemed it once, so already at the time of the email this should be blocked (as is correctly working in the case of a multi-coupon-code).

I'll update this question when SAP replies on the ticket.

Kr

Joyca

[former_member601701]

Hi Joyca,

Could you please create an incident with all the steps you did to reproduce your problem and we will investigate to see if there is a bug.

Best Regards,

Ryan