When player.marketing_consent.updated webhook is sent

The player.marketing_consent.updated webhook is sent only when the player’s marketing consent status actually changes. Marketing consent is tied to the player_id and is not reset between purchases.

When the event is sent

• During hub.purchase, if the player changes consent status while making a purchase:

  • No consent → checkbox checked: consent is granted and the event is sent.

  • Consent exists → checkbox unchecked: consent is revoked and the event is sent.

• Through S2S API calls:

  • s2s.player.marketing_consent.grant

  • s2s.player.marketing_consent.revoke

• Through checkout profile actions:

  • checkout_profile.player.marketing_consent.revoke

When the event is not sent

• Consent exists → checkbox remains checked: no event, because status did not change.

• Consent exists → player makes another purchase without changing consent: no event.

• No consent → checkbox remains unchecked: no event, because status did not change.

• Changing the player email alone does not trigger the event unless the consent status changes.

Example: consent revoked via S2S, then granted again on purchase

If consent was previously revoked via S2S and the player later makes a purchase with the marketing consent checkbox checked, consent is granted again and player.marketing_consent.updated is sent.

Where players can manage consent

Players can manage their email subscription preferences in My Aghanim:

https://my.aghanim.com/en?settings=subscriptions

Dashboard limitations

At the moment, the dashboard does not display a player’s marketing consent status, and consent cannot be revoked directly from the dashboard.