Natero Destination

Segment makes it easy to send your data to Natero (and lots of other destinations). Once you've tracked your data through our open source libraries we'll translate and route your data to Natero in the format they understand. Learn more about how to use Natero with Segment.


Personas

You can send computed traits and audiences generated through Segment Personas to this destination as a user property. To learn more about Personas, reach out for a demo.

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 false.

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

WebMobileServer
📱 Device-based
☁️ Cloud-based

To learn more about about Connection Modes and what dictates which we support, see here.

Settings

Segment lets you change these destination settings via your Segment dashboard without having to touch any code.

Auth Key

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’.

Endpoint Region

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.

Send Key

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’.


If you have any questions, or see anywhere we can improve our documentation, please let us know!