Skip to contentSkip to navigationSkip to topbar
On this page
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

UserMotion (Actions) Destination


Destination Info
  • Accepts Page, Alias, Group, Identify and Track calls.
  • Refer to it as UserMotion (Actions) in the Integrations object
  • This integration is partner owned. Please reach out to the partner's support for any issues.
  • This destination is in Beta

UserMotion(link takes you to an external page) is AI-powered predictive lead scoring software that discovers intention signals and scores leads on potential to buy, expand, or churn.

This destination is maintained by UserMotion. For any issues with the destination, contact their Support team.


Getting started

getting-started page anchor
  1. From your workspace's Destination catalog page(link takes you to an external page) search for "UserMotion (Actions)".
  2. Select UserMotion (Actions) and click Add Destination.
  3. Select an existing Source to connect to UserMotion (Actions).
  4. Go to the UserMotion dashboard(link takes you to an external page), find and copy the API key.
  5. Enter the API Key in the UserMotion destination settings in Segment.
  6. Save your changes and enable the destination.

Property nameTypeRequiredDescription
API Keystring
required

Your UserMotion API Key


UserMotion (Actions) has the following presets

Preset NameTriggerDefault Action
Identify UserEvent type = "identify"Identify
Identify GroupEvent type = "group"Identify Company
Track Analytics EventEvent type = "track", Event type = "page"Track Analytics Event

Build your own Mappings. Combine supported triggers with the following UserMotion-supported actions:

(information)

Mapping limits per destination

Individual destination instances have support a maximum of 50 mappings.

Identify Company

identify-company page anchor

Create or update a company in UserMotion

Identify Company is a Cloud action. The default Trigger is type = "group"

Property nameTypeRequiredDescription
User IDSTRING

Optional

A identifier for a known user.


Anonymous IDSTRING

Optional

An identifier for an anonymous user


Group IDSTRING
required

A identifier for a known company.


TraitsOBJECT

Optional

Traits to associate with the company

Send user and page events to UserMotion

Track Analytics Event is a Cloud action. The default Trigger is type = "track" or type = "page"

Property nameTypeRequiredDescription
User IDSTRING

Optional

A identifier for a known user.


Anonymous IDSTRING

Optional

An identifier for an anonymous user


Event NameSTRING
required

The name of the track() event or page() event


Context propertiesOBJECT

Optional

Context properties to send with the event


Event PropertiesOBJECT

Optional

Properties to send with the event.

Identify user in UserMotion

Identify is a Cloud action. The default Trigger is type = "identify"

Property nameTypeRequiredDescription
User IDSTRING
required

A identifier for a known user.


Anonymous IDSTRING

Optional

An identifier for an anonymous user


EmailSTRING
required

The email address of the identified user


TraitsOBJECT

Optional

Traits to associate with the user


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(link takes you to an external page).

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.

(information)

Real-time to batch destination sync frequency

Real-time audience syncs to UserMotion (Actions) may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.


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

Property nameTypeRequiredDescription
API Keystring
required

Your UserMotion API Key