Millennial Media Destination
You’ll need to map from the Segment event name to the Millennial Media Pixel ID in your Segment source’s Millennial Media Destination page.
Getting your Pixel ID
We built this destination off this documentation please refer to that or let us know if you have any questions!
For user-property destinations, an identify call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property
order_completed_last_30days: true, and when this user no longer satisfies we will set that value to
When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.
Supported Sources and Connection Modes
The first step is to make sure Millennial Media supports the source type and connection mode you’ve chosen to implement. You can learn more about what dictates the connection modes we support here.
To learn more about about Connection Modes and what dictates which we support, see here.
This destination requires a Device-based Connection Mode for Mobile data. Follow the steps above to ensure you have packaged the Millennial Media SDK with Segment’s.
Segment lets you change these destination settings from your Segment dashboard without having to touch any code.
Millennial Media recognizes pixel ids, not custom events. When you
analytics.track(event, properties) an event that represents a Millennial Media ad conversion, you’ll need to map the event name on the left to it’s corresponding Millennial Media pixel id on the right in the integration panel.
Questions? Problems? Need more info? Contact us, and we can help!