Skip to main content

mParticle

Server Source code Package Beta

Server-side event delivery to mParticle via the HTTP Events API. Events are packaged into batches and POSTed to the regional mParticle pod using HTTP Basic auth (apiKey / apiSecret). Supports user identities, user attributes, consent state, and environment targeting.

Where this fits

mParticle is a server destination in the walkerOS flow:

Receives events server-side from the collector and forwards them to mParticle's input feed for fan-out to downstream destinations.

Installation

Loading...
Loading...

Configuration

This destination uses the standard destination config wrapper (consent, data, env, id, ...). For the shared fields see destination configuration. Package-specific fields live under config.settings and are listed below.

Settings

PropertyTypeDescriptionMore
apiKey*stringmParticle input feed API key from the mParticle dashboard (Setup > Inputs > Feeds).
apiSecret*stringmParticle input feed API secret paired with apiKey. Used for HTTP Basic auth.
pod'us1' | 'us2' | 'eu1' | 'au1'mParticle data pod selecting the regional endpoint. Default: 'us1'.
environment'production' | 'development'Environment the batch targets. Default: 'production'.
userIdentitiesRecord<string, any>Mapping that resolves to user_identities per batch. Keys are mParticle identity types (like customer_id, email); values are walkerOS mapping values.
userAttributesanyMapping value that resolves to the user_attributes object placed on the batch.
consentRecord<string, any>Static consent_state envelope forwarded verbatim on the batch. See mParticle consent_state docs.
ipanyMapping value resolving to the client IP for the batch.
sourceRequestIdanyMapping value resolving to the source_request_id for the batch. Falls back to event.id when unset.
* Required fields

Mapping

Per-event rules under config.mapping. For the standard rule fields (consent, condition, data, batch, name, policy) see mapping.

PropertyTypeDescriptionMore
eventTypePer-event mParticle event type. Default: 'custom_event'.
customEventTypeCustom event type category for 'custom_event'. Default: 'other'.
commerceanyMapping value resolving to the commerce fields (product_action, currency_code, products, ...) for a commerce_event.
userIdentitiesRecord<string, any>Per-event override mapping for user_identities. Merged over settings.userIdentities.
userAttributesanyPer-event override mapping for user_attributes.

Examples

commerce purchase

Event
Mapping
Out

custom event

Event
Out

identity and attributes

Event
Out

screen view

Event
Mapping
Out

The apiKey and apiSecret come from an mParticle input feed (Setup, Inputs, Feeds, Custom Feed). Each batch posts to https://s2s.{pod}.mparticle.com/v2/events using HTTP Basic auth.

Identities and attributes

  • userIdentities: map walkerOS event fields to mParticle identity types (customer_id, email, other, etc.).
  • userAttributes: resolved from each event and placed on the batch's user_attributes object.
  • consent: forwarded verbatim as consent_state on the batch.
  • sourceRequestId: defaults to event.id if unset; used by mParticle for deduplication.
💡 Need implementation support?
elbwalker offers hands-on support: setup review, measurement planning, destination mapping, and live troubleshooting. Book a 2-hour session (€399)