โžก๏ธ Push data to Salesmachine

Pushing data to Salesmachine

Once you've been creating your application, you can choose to start configuring the Adoption module (Customer Success) or the Conversion module (Trial Qualification). Select the one you are interested in starting with and then click on 'Start configuring' to select your primary source of data.

Source of references :

Once the module selected, you'll be asked to choose a source of reference. The source of reference will be the only data source to create contacts and accounts in Salesmachine.

We have 3 sources of data available, you can choose between the Salesmachine API, Intercom or Segment.

If you wish to use the API, follow the given instruction & use this documentation.

If you wish to use Intercom & Segment, you can refer to these pages for more information: Intercom - Segment.

Enrichment sources

Data regarding your customers can be distributed through the different solutions you're using: gathering them all is highly valuable and can save you a lot of time. To do so, we integrated directly the most commonly used solutions, such as:

  • CRM: Pipedrive, Hubspot, Salesforce

  • Ticketing: Zendesk

  • Payment: Stripe

  • Mailers: Sendgrid, Mailgun, Mailjet, Mandrill and/or an SMTP connexion

  • NPS: Delighted, Satismeter

  • Others: Slack & Zapier

Please note that these sources won't create any contact or account but updating the ones listed in Salesmachine.

โ€‹

Main accessible data:

There are two main kinds of data that can be pushed in Salesmachine: Events and Attributes.

Events:

An event is an action detected by a program, it's usually used to track the actions performed by your end-users. Tracking events is important as you'll need them for a lot of business cases (score customer's health, trigger automation, etc).

The events are performed by the contacts but aggregated at the account level

You can check the events you are pushing in Salesmachine in the Report sectionโ€‹

Attributes:

An attribute is an information regarding a customer. It is usually a static information but it can evolve over time: first_name, email, country, created_at, MRR, plan, periodicity, etc. They can be pushed at both levels (account or contact) and they are important to get a great overview of your customers' situation or to trigger automations/alerts.

The attributes can have different types (Text, Number, Date, True/False, Pick list), it is important to make sure that they are pushed in the right type/format, otherwise, you will not be able to run conditions on them properly.

Once the attributes are pushed, here is how it looks like in the solution: