For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Personas sends an Identify call with the property
order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Personas sets that value to
When you first create an audience, Personas sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.
Supported Sources and Connection Modes
Before you start, make sure Natero supports the source type and connection mode you’ve chosen to implement. You can learn more about connection modes here.
Segment offers an optional Device-based Connection Mode for Mobile data going to Natero, so that you can use Natero features that collect data directly from the mobile device. To do this, you must package the Segment-Natero mobile SDK with the Segment mobile library.
Segment lets you change these destination settings from the Segment app without having to touch any code.
To retrieve your Auth Key first navigate to Sources > List Sources. Select your source, and then click the ‘Select View’ dropdown, and select ‘View Settings’.
If you are located in the EU, set the Natero API endpoint to “EU” to send your data to Natero’s EU endpoint to ensure compliance with GDPR’s data storage rules.
To retrieve your Send Key first navigate to Sources > List Sources. Select your source, and then click the ‘Select View’ dropdown, and select ‘View Settings’.
This page was last modified: 25 Nov 2019
Questions? Problems? Need more info? Contact us, and we can help!