Salesforce Marketing Cloud
Insert events into Salesforce Marketing Cloud data extensions via its REST API with OAuth2 client credentials. Distinct from the Salesforce CDP / Data Cloud integration — Marketing Cloud uses different authentication and payload shapes.
⚠️
Status: alpha. Scaffolded entry. Data extension field-mapping presets are pending. OAuth2 token refresh handling is in place via the Datafly delivery workers.
Prerequisites
- A Marketing Cloud business unit (MID) with API access enabled.
- An Installed Package with a Server-to-Server API integration component. Configure under Setup > Apps > Installed Packages.
- The installed package’s Client ID and Client Secret (for OAuth2 client-credentials grant).
- A data extension in the target business unit that will receive events. Note its External Key — this is what Signal inserts rows into.
- Your Marketing Cloud tenant-specific REST Base URI subdomain (e.g.
mc-abc123xyzfromhttps://mc-abc123xyz.rest.marketingcloudapis.com).
Configuration fields
| Field | Required | Notes |
|---|---|---|
subdomain | Yes | Tenant-specific REST subdomain. |
client_id | Yes | Installed package client ID. |
client_secret | Yes | Installed package client secret (kept secret). |
account_id | Yes | Business unit MID. |
data_extension_key | Yes | External key of the target data extension. |
Authentication flow
Signal requests an access token from:
POST https://{subdomain}.auth.marketingcloudapis.com/v2/tokenthen uses the returned bearer token on subsequent data-extension insert calls. Tokens are cached and refreshed automatically.
Next steps
- Ensure the target data extension’s columns match the fields you intend to send. Signal will map pipeline field names to column names; unmatched columns default to null or fail depending on the column’s nullability.
- For Marketing Cloud Journey Builder triggers, use the Entry Event API instead. A separate integration is planned.