Salesmachine Destination
Salesmachine quick info
Salesmachine accepts Track, Page, Identify, Group, and Alias calls. If you reference it in the Integrations object, call it “Salesmachine”.
Salesmachine accepts cloud-mode data from all Segment source types. It does not offer device-mode connections.
This destination is maintained by Salesmachine.
Getting Started
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.
Page
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.
Identify
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.
_
Track
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.
Group
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.
Alias
When you call alias
, we will send an alias call to Salesmachine.io.
Personas
You can send computed traits and audiences generated using Segment Personas to this destination as a user property. To learn more about Personas, contact us for 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, 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 false
.
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 Salesmachine supports the source type and connection mode you’ve chosen to implement. You can learn more about connection modes here.
Web | Mobile | Server | |
---|---|---|---|
📱 Device-mode | ⬜️ | ⬜️ | ⬜️ |
☁️ Cloud-mode | ✅ | ✅ | ✅ |
Segment offers an optional Device-based Connection Mode for Mobile data going to Salesmachine, so that you can use Salesmachine features that collect data directly from the mobile device. To do this, you must package the Segment-Salesmachine mobile SDK with the Segment mobile library.
Settings
Segment lets you change these destination settings from the Segment app without having to touch any code.
API secret
Your Salesmachine API secret is available inside the administration panel. You first have to create an app in Salesmachine.
API token
Your Salesmachine API token is available inside the administration panel. You first have to create an app in Salesmachine.
This page was last modified: 22 Nov 2019
Need support?
Questions? Problems? Need more info? Contact us, and we can help!