mParticle

Datafly Signal delivers events server-to-server into the mParticle Customer Data Platform using the Events API (POST /v2/events). Signal sends behavioural events together with the user’s identities, so mParticle’s IDSync can resolve a stable profile, enrich it, and forward it to every downstream output you have connected (ad platforms, analytics, warehouses, marketing tools).

Prerequisites

Before configuring mParticle in Signal you need an mParticle account and a Server-to-Server (S2S) input feed with API credentials.

Configuration

Configure in Signal

1. Go to Integrations > Add Integration > mParticle.
2. Select the Default preset.
3. Enter your api_key, api_secret, and s2s_host.
4. Select the consent categories that should gate delivery (typically marketing).
5. Click Save.

API Endpoint

POST https://{s2s_host}/v2/events
Authorization: Basic base64(api_key:api_secret)
Content-Type: application/json

A successful request returns 202 Accepted. Each request carries a single user’s identities at the root and that user’s events in the events array.

Identity Signals

mParticle resolves a profile from the user_identities object using IDSync. Signal populates these automatically:

First and last name and phone are sent as mParticle reserved user attributes ($firstname, $lastname, $mobile). Marketing consent maps to consent_state.gdpr.marketing.consented.

Event Mapping

Signal maps GA4-style event names to mParticle’s three event envelope types — screen_view, custom_event, and commerce_event:

Events not in the mapping are dropped (defaults.action: drop). To add or change a mapping, edit the integration’s Field Mappings in the Management UI.

Example: Order Completed

Datafly.js call:

datafly.identify("user-123", { email: "jane.doe@example.com" });
 
datafly.track("Order Completed", {
  order_id: "ORD-001",
  revenue: 129.99,
  currency: "USD",
  tax: 8.00,
  shipping: 4.99,
  products: [
    { product_id: "SKU-A", name: "Widget", price: 49.99, quantity: 2 },
    { product_id: "SKU-B", name: "Gadget", price: 30.01, quantity: 1 }
  ]
});

mParticle payload sent by Signal:

{
  "environment": "production",
  "schema_version": 2,
  "ip": "203.0.113.50",
  "user_identities": {
    "customer_id": "user-123",
    "email": "jane.doe@example.com",
    "other": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
  },
  "device_info": {
    "http_header_user_agent": "Mozilla/5.0 ..."
  },
  "events": [
    {
      "event_type": "commerce_event",
      "data": {
        "currency_code": "USD",
        "timestamp_unixtime_ms": 1706540000000,
        "source_message_id": "evt_abc123def456",
        "product_action": {
          "action": "purchase",
          "transaction_id": "ORD-001",
          "total_amount": 129.99,
          "tax_amount": 8.00,
          "shipping_amount": 4.99,
          "products": [
            { "id": "SKU-A", "name": "Widget", "price": 49.99, "quantity": 2 },
            { "id": "SKU-B", "name": "Gadget", "price": 30.01, "quantity": 1 }
          ]
        }
      }
    }
  ]
}

Testing

1. Configure the integration with your feed credentials and the correct s2s_host.
2. Trigger events on your site.
3. In mParticle, open Activity > Live Stream and select your feed input. Events appear within a few seconds.
4. Confirm the resolved profile under Activity > User Activity by searching for the customer_id or email you sent.
5. A successful delivery is 202 Accepted in Signal’s event debugger.

Troubleshooting