Miscellaneous Cohort Sync Features

Features not specific to any one Cohort Sync Partner

Initially, the Cohort Sync feature was very narrow. It synced cohorts to only a few destinations, and in a very rigid form. For example, all the properties we exported were fixed for each Integration type, with no flexibility. Over time and in response to customer requests, we’ve added some features that make it easier and more flexible to sync your Cohorts to your desired destinations.

 

Multiple Connections for each Integration

Before, we only supported a single outgoing Connection to each partner. Now, we allow customers to have as many Connections to each partner as they need. This allows customers to keep all of their data in a single project, and sync to multiple instances of a Partner. For example, if you have a different Facebook Ads Account for different geographies or different partner accounts for different verticals in your organization. To make a new Connection beyond the first, click the Dropdown that lists Connection names and click "+ Add Connection":

Screen_Shot_2022-04-14_at_10.39.58_AM.png

After clicking "+ Add Connection", the flow is identical to setting up your first Connection.

Once you've set up the Connection, you can mark Cohorts for Export through the usual flow, and your different Connections will be differentiated by their Connection Name in parentheses after the name of the Integration. In the screenshot of the Cohorts page below, we have 3 Integrations connected with the Default name, and one Segment integration that has name test_segment.

mceclip3.png

 

Selecting a specific User ID Property to export

For Integrations that attempt to match users between Mixpanel and the target destination, such as OneSignal, we used to require that a specific property, such as $onesignal_user_id in OneSignal's case, to exist on each profile to be matched. Retroactively tracking this property if it did not exist was cumbersome for customers, and many customers had a 1-to-1 mapping between $distinct_id and $onesignal_user_id. To enable this use case for OneSignal and other Integrations, we allow customers to select which property they want to use as a join key between the two systems at Connector creation time, such as in the picture below:

UserIDProperty1.png

UserIDProperty2.png

Once selected, the partner will receive the value of the selected property as part of the payload of the Cohort Export. This feature should help to simplify implementations that involve Mixpanel and other technology partners.

Choosing which User Profile Properties to export

With the addition of our Custom Webhook option and the increasing power and flexibility of many of our integration partners, we also added the ability to select which properties you want to export to your destination. If this feature is available for an Integration, you can select the properties at Connector creation time.ExportProperties1.png

ExportProperties2.png

We recommend reading the documentation for the Custom Webhook feature and using a site such as webhook.site to test your integration for best results.

Did this answer your question?

Comments

0 comments

Article is closed for comments.