mParticle
Introduction
The mParticle connector is a Reverse ETL destination that authenticates against the mParticle Conversions (Server-to-Server Events) API.
At this time, the connector’s load/sync behavior is still in development. You can use it to validate credentials, but production data delivery is not yet available.
Setup
- In mParticle, create or locate an API key/secret pair that has access to send events via the S2S Events endpoint.
- Identify your mParticle pod (your mParticle data center/cluster), which is used to form the API base URL.
The connector sends requests to:
https://s2s.{pod}.mparticle.com/v2/events
Authentication
This connector uses HTTP Basic Auth:
- Username:
api_key - Password:
api_secret
During credential validation, the connector performs a test request to the S2S Events endpoint.
Configuration fields
| Field | Type | Required | Description |
|---|---|---|---|
pod | string | ✓ | Your mParticle pod, used to build the endpoint https://s2s.{pod}.mparticle.com/v2/events. |
api_key | string | ✓ | mParticle API key used as the Basic Auth username. |
api_secret | string | ✓ | mParticle API secret used as the Basic Auth password. |
Hashing and normalization
This destination connector does not currently expose field-level hashing.
Data contract
Not yet available. The destination load/sync implementation is still in development, so there is no stable, documented mapping of input fields to mParticle event payload fields at this time.
Streams
Not yet available.