Skip to main content

Discord Conversions API

Send server-side application events to Discord for conversion tracking and Quest fulfillment.

API Documentation: Discord Application Events API specification.

Configuration

To configure Discord Conversions API as a destination, you'll need a bot token for the Event Source Application that Discord created for your title or game.

Authentication

This connector authenticates with Discord bot-token authentication:

Authorization: Bot <bot_token>

Connection validation does not send a synthetic event. Discord token or payload problems are reported during the first run that sends real events.

Events

Each source record maps to one Discord application event. Extract sends events to:

POST https://discord.com/api/v9/applications/@me/events

@me is literal. Discord resolves it from the bot token's application.

For Discord app event types 1 and 2, include a non-empty app object. Discord rejects those events with app is required for app events when app metadata is missing.

Delivery Behavior

  • Extract sends { "events": [...] }.
  • Discord may return HTTP 200 with a failures array. Extract counts those entries as failed records and logs their error messages.
  • HTTP 4xx and 5xx responses fail the batch unless continue_on_errors is enabled.
  • User identifiers are removed from network log payloads.

Hashing and normalization

  • When Apply hashing (SHA256) is enabled for user.emails_sha256, Extract trims and lowercases email addresses before hashing. Gmail and Googlemail addresses also have dots and plus tags removed before hashing.
  • When Apply hashing (SHA256) is enabled for user.phone_numbers_sha256, Extract strips non-digit characters before hashing.
  • When Apply hashing (SHA256) is enabled for advertising IDs, Extract uppercases iOS IDFA values and lowercases Android GAID values before hashing.
  • If you choose Source values are already hashed, normalize the values according to the rules above before hashing them upstream.
  • More detail: Identifier Hashing and Normalization.

Data Contract

Loading ....