Natero Destination

Destination Info

• Accepts Page, Alias, Group, Identify, and Track calls
• Refer to it as Natero in the Integrations object

Components

• Server

Connection Modes

Device-mode	Cloud-mode
Web	Web
Mobile	Mobile
Server	Server

Natero, also known as Freshdesk Customer Success helps customer success managers better understand their customers by integrating all of your customer data in one place and leveraging it to help with prioritization and context. By reaching out to customers in the right way at the right time, CSMs can reduce churn, increase upsell and create advocates for your business. For more details on how the segment integration for Natero works, visit the Natero developer site.

Getting Started

1. From the Destinations catalog page in the Segment App, click Add Destination.
2. Search for “Natero” in the Destinations Catalog, and select the “Natero” destination.
3. Choose which Source should send data to the “Natero” destination.
4. Within Natero, navigate to IT Administration from the cogwheel in the left navigation bar.
5. Go to the tab labeled “Source Overview” and retrieve the “Event API / Send key” and the “Event auth key”.
6. Enter those keys in the “Natero” destination settings in Segment.

Supported methods

Natero supports the following methods, as specified in the Segment Spec.

Group

Send Group calls to provide updated metadata about the account that a user is associated with. For example:

analytics.group('accountId123', {
  name: 'Example Inc.',
  description: 'Description of Example Inc.'
});

Segment sends Group calls to Natero as a group event.

Identify

Send Identify calls to update detail about a user. For example:

analytics.identify('userId123', {
  email: 'john.doe@example.com'
});

Segment sends Identify calls to Natero as an identify event.

Track

Send Track calls to capture user actions within your application as features within Natero. For example:

analytics.track('Login Button Clicked')

Segment sends Track calls to Natero as a track events.

Engage

You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.

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, Engage 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), Engage sets that value to false.

When you first create an audience, Engage 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.

Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.