# mParticle (Legacy) mParticle is a customer data platform that allows you to unify your customer data and connect it anywhere to improve marketing performance, enhance analytics, and transform the customer experience. With mParticle you can easily connect Customer.io to your data stream to begin receiving real time event and audience data in Customer.io. ## Send Events to Customer.io[](#send-events-to-customerio) Send event data to Customer.io by setting up Customer.io as an Event Output in mParticle. From the mParticle activity overview screen select **Setup** > **Outputs** > **Event** > **Add Event Output** and select or search for Customer.io from the dropdown list. [![Customer.io Mparticle Add Event Output](https://docs.customer.io/images/Customer.io%20Mparticle%20Add%20Event%20Output.png)](#f9c1e7bf17fdf43317810b36270812c2-lightbox) Next navigate to the Customer.io workspace you’d like to send your data to. From the main dashboard select > **Integrations** > **Customer.io API** (Settings). Here you will find your Site ID and API Key. [![Customer.io Mparticle API Key](https://docs.customer.io/images/Customer.io%20Mparticle%20API%20Key.png)](#7634f03497ff33b962eaee107bfd77da-lightbox) Next enter your API Key and Site ID keys into mParticles event configuration, name the configuration, and select the settings relevant to you. [![Mparticle Customer.io Event Configuration ](https://docs.customer.io/images/Mparticle%20Customer.io%20Event%20Configuration%20.png)](#ac3043fd3bae899f0d4b0c287cbe5098-lightbox) Success! –– You have connected mParticle to Customer.io for Events ## Send Audience data to Customer.io[](#send-audience-data-to-customerio) Send audience data to Customer.io by setting up Customer.io as an Audience Output in mParticle. Start by navigating to the mParticle activity overview screen. Click **Setup** > **Outputs** > **Audience** > **Add Audience Output** and select or search for Customer.io from the dropdown list. [![Customer.io Mparticle Add Audience Output](https://docs.customer.io/images/Customer.io%20Mparticle%20Add%20Audience%20Output.png)](#29e72449069fa22f0c743565584d3560-lightbox) Next navigate to the Customer.io workspace you’d like to send your data to. From the main dashboard select > **Integrations** > **Customer.io API** (Settings). Here you will find your Site ID and API Key [![Customer.io Mparticle API Key](https://docs.customer.io/images/Customer.io%20Mparticle%20API%20Key.png)](#7634f03497ff33b962eaee107bfd77da-lightbox) Next enter your API Key and Site ID keys into mParticles audience configuration, name the configuration, and select the settings relevant to you. [![Mparticle Customer.io Audience Configuration ](https://docs.customer.io/images/Mparticle%20Customer.io%20Audience%20Configuration%20.png)](#e307254ae163326c1ca69200f733d90e-lightbox)  Create One user Attribute per Segment: If enabled, mParticle will forward membership information for each segment as a seperate user attribute. For example, if you’re forwarding a segment named “New Users” mParticle will forward membership information for this segment in a user attribute called “In New Users, with a value of “true” or “false”. If disabled, mParticle will forward a single user attribute called “Segment Membership”, and it’s value will be a comma-separated list of mParticle segment IDs that the user is a member of, wrapped in single quotes. If you’re unsure what to select here we recommend enabling this feature. Success! –– You have connected mParticle to Customer.io for Audience ## Send message event data to mParticle[](#send-message-event-data-to-mparticle) By setting up Customer.io as an mParticle Feed, you can pipe messaging activity out of Customer.io and into any one of mParticle’s hundreds of Output integrations. Data will be sent to mParticle as a [custom event](https://docs.mparticle.com/developers/apis/json-reference/). ### Setup[](#setup) 1. Start by creating a new Input Feed in mParticle. Click **Setup** > **Inputs** > **Feeds** > **Add Feed Input** and select or search for Customer.io from the dropdown list. [![mparticle_add_feed_input.png](https://docs.customer.io/images/image%28521%29.png)](#90c59aa50411926aefc83a7a6357ec2e-lightbox) 2. In the Feed Configuration modal, name your configuration and click **Save** to get your *Server Token* and *Secret*. You’ll need these to configure the integration in Customer.io. [![mparticle_configure_feed_input.png](https://docs.customer.io/images/image%28523%29.png)](#8cea697651b3bf546dbdb87781840bdb-lightbox) 3. In Customer.io go to *Data & Integrations* > *Integrations* and click the **mParticle Source** card. 4. Enter your mParticle *Server Key* and *Secret* and click **Connect** to test the connection. [![Add your mParticle credentials](https://docs.customer.io/images/mparticle-creds.png)](#98107a407ba3cd8ff2a1e50ffe4f2d72-lightbox) 5. Select the events that you want to send to mParticle, enable the integration, and save your changes to start sending events from Customer.io to mParticle.  Send only the first time the event occurs: This setting tells Customer.io to forward messaging events the first time they occur, and only the first time they occur. We won’t send subsequent events, even if a customer opens or clicks on a message multiple times. If you’re unsure what to select here we recommend that you select this option. [![Select the events you want to send](https://docs.customer.io/images/mparticle-setup.png)](#c5279c17cdbd120bdf1db2c862420cec-lightbox) ### Events[](#events) The following events are available in the feed: Name Description email\_sent An email was sent from Customer.io to the delivery provider email\_delivered The delivery provider reported the email was delivered to an inbox email\_opened An email was opened email\_clicked A tracked link in an email was clicked email\_converted A person matched conversion criteria attributed to an email email\_bounced The delivery provider was unable to deliver the email email\_spammed An email was marked as spam by the recipient email\_failed An email couldn’t be sent to the delivery provider push\_sent A push notification was sent from Customer.io to the delivery provider push\_opened The app on a person’s device reported the push notification was opened push\_clicked A tracked link in a push notification has been clicked push\_converted A person matched conversion criteria attributed to a push notification push\_bounced The delivery provider reported at least one invalid device token push\_failed A push notification couldn’t be sent to the delivery provider sms\_sent An SMS was sent from Customer.io to the delivery provider sms\_delivered The delivery provider reported the SMS was delivered sms\_clicked A tracked link in an SMS has been clicked sms\_converted A person matched conversion criteria attributed to an SMS sms\_bounced The delivery provider was unable to deliver the SMS sms\_failed An SMS couldn’t be sent to the delivery provider If you have a specific request for an event not listed here that you would like to be notified of, please let us know at [win@customer.io](http://win@customer.io). ## Event Attributes[](#event-attributes) Attribute Description action\_id If the delivery was created as part of a Campaign or API Triggered Broadcast workflow, this is the ID for the unique workflow item that caused the delivery to be created. It can be used to retrieve full message details, including content, via the Campaign endpoint of [our API](/integrations/api/app/). broadcast\_id If applicable, the ID of the API Triggered Broadcast that generated the message. It can be used to retrieve full message details, including content, via the Campaign endpoint of [our API](/integrations/api/app/). campaign\_id If applicable, the ID of the Event-triggered, Segment-triggered, or Date-triggered Campaign that generated the message. content\_id If the message was part of a newsletter split test, this is the ID of the split test variation. delivery\_id The unique ID of the delivery record associated with the message. journey\_id The ID for the path a person went through in a Campaign or API Triggered Broadcast workflow. In our [Data Warehouse Sync](/journeys/data-warehouse-sync), this is referred to as subject\_id. newsletter\_id If applicable, the ID of the Newsletter that generated the message. It can be used to retrieve full message details, including content, via the Newsletters endpoint of [our API](/integrations/api/app/). recipient The address of the message recipient. This could be an email address, a phone number, a mobile device ID, a Webhook URL, or a Slack username or channel. source\_message\_id The unique ID of the event being sent. This can be useful for deduplicating purposes. timestamp\_unixtime\_ms The timestamp at which the event being reported took place. ## Additional Documentation[](#additional-documentation) * [mParticle Event Documentation](https://docs.mparticle.com/integrations/customerio/event/) * [mParticle Audience Documentation](https://docs.mparticle.com/integrations/customerio/audience/) * [mParticle Feed Documentation](https://docs.mparticle.com/integrations/customerio/feed/)