Salesmachine Destination

In order to push segment data to Salesmachine.io, you need to provide Salesmachine.io api_token and api_secret. This tokens are available on the administration panel.

Salemachine.io supports the identify, track, page, group and alias methods.

When you call a page event, we send a pageview to Salesmachine.io which manages automatically new sessions. When your page is named, we send a pageview to Salesmachine.io and an event with the name of this page. You must add account_uid in event parameters to automatically link this pageview to an account. However, if the contact that performed the pageview has only one account, Salesmachine.io will automatically link the event to his account.

When you identify a user, we'll pass that user's information to Salesmachine.io. For a better experience with Salesmachine.io we encourage you to add at least name and email traits. You must add account_uid in traits to automatically link this user to a Salesmachine.io account.

When you track an event, we will send that event to Salesmachine.io. (include details about how that event is sent). You must add account_uid in event parameters to automatically link this event to an account. However, if the contact that performed the event has only one account, Salesmachine.io will automatically link the event to his account.

When you call group, we will send an account call to Salesmachine.io and link the provided user to this account. Group's traits will be sent as Salesmachine.io account's information.

When you call alias, we will send an alias call to Salesmachine.io.

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.

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