Skip to main content

Discord

Overview​

The Discord connector lets you configure a destination for sending conversion events to Discord via the Discord Conversions API.

Status​

The Discord Conversions API destination is currently in development. You can save credentials, but runs are not supported yet.

Setup​

  • A Discord application/bot with an associated bot token.
  • Your destination stream must be attached to the Application Events data contract.

Get your bot token​

  1. In the Discord Developer Portal, open your application.
  2. Go to Bot.
  3. Copy the Token (or reset it if needed).

Authentication​

This destination uses a single credential:

  • Bot Token: The Discord bot token used to authenticate requests.

Configuration​

FieldTypeRequiredDescription
bot_tokenstring✅Discord bot token used for authentication.
continue_on_errorsbooleanIf true, the connector will continue sending subsequent batches when a batch fails. If false, the sync stops on the first batch error.

Streams / Data model​

This connector is a destination (not a source), so it does not expose streams.

Limitations​

  • Runs are not supported yet. Attempting to run a sync/load will fail with an “in development” error.
  • Only credential storage/validation flow is available at this time.

Data Streams​

The Discord connector writes Application Events to the Discord Conversions API.

Each record is sent as a Discord Conversions API event. The connector supports nested objects and will map flattened fields back into the expected object structure for the following top-level objects:

  • user.*
  • device.*
  • app.*
  • content.*

Email fields​

If you provide scalar email values, the connector will wrap them into the structure expected by Discord before sending. In practice, this means email fields under user are normalized from a scalar into an object form (for example, user.email: "a@b.com" becomes an object payload for user.email).

This wrapping happens after hashing is applied (if configured) and before null fields are removed.

Notes​

  • The Discord Conversions API destination validates credentials on the first sync run. The connector does not send a test request during Login because Discord’s event endpoint does not provide a read-only credential check.
  • This destination must be attached to the Application Events data contract. If no data contract is configured, the sync will fail.
  • Events older than 72 hours are rejected by the connector and will not be sent.
  • Records are sent in batches (up to 1000 events per request) with concurrent workers (up to 10) to improve throughput.
  • The connector can optionally continue processing when a batch fails. Configure continue_on_errors to control whether the sync stops on the first error or proceeds while logging failures.
  • For compatibility with Discord’s expected payload shape, scalar email fields are automatically wrapped as objects (for example, an email value may be sent as { "email": { "address": "..." } }).
  • Sensitive fields are redacted in request logs (for example, tokens and other secrets).