Unexpected App Store Server Notification offerIdentifier

Question

Created Oct ’24

Replies 2

Boosts 0

Participants 2

My server receives App Store Server Notification v2 notifications. Recently, it has been receiving notifications for offer codes under offers that have been deactivated. The custom code value may be the same in the active offer as the deactivated offer.

When a user redeems the custom offer code for a deactivated offer, the notification payload's offerIdentifier value now contains the UUID associated with that offer in the URL in App Store Connect

(like https://appstoreconnect.apple.com/apps/my-app-id/distribution/subscriptions/my-subscription-id/pricing/offer-codes/offer-uuid)

The notification payload contains:

{"offerIdentifier": "offer-uuid"}

instead of

{"offerIdentifier": "<My offer identifier from App Store Connect>"}

Is it possible for a deactivated offer to be redeemed? If not, is this a known issue?
We need the actual offer identifier to understand which offers users are redeeming. Is this replacement with a UUID a known issue?

Boost

Answer 1

App Store Commerce Engineer OP

Apple

Oct ’24

@j_ptron Could you please file a ticket with a specific notification with this behavior in Feedback Assistant (feedback assistant.apple.com) and post the FB number here please

0

Answer 2

j_ptron OP

Oct ’24

Thanks. Filed FB15532459. After review, it looks like this has only happened for notifications of type EXPIRED, though we would still expect to get the correct offer identifier in the payload.

0