Xtremepush (Actions) Destination
Additional versions of this destination are available
This page is about the Xtremepush (Actions) Destination. See below for information about other versions of the Xtremepush destination:
Xtremepush is a complete digital engagement platform that empowers global brands to create personalized, real-time experiences for their customers across mobile, web, email, SMS and social. Xtremepush’s clients are increasing revenue through data-driven, contextually-relevant interactions. The software is flexible, reliable and quick to deploy, backed up by a team of expert strategists and technical support.
This destination is maintained by Xtremepush. For any issues with the destination, contact the Xtremepush Support team.
Benefits of Xtremepush (Actions) vs Xtremepush Classic
Xtremepush (Actions) provides the following benefits over the classic Xtremepush destination:
- Easier setup: Users see fewer initial settings which can decrease the time spent configuring the destination.
- Increased transparency: Users can see both the exact data that is sent to the destination and the time that Segment sent it.
- Improved customization: Users can determine how the events their sources trigger map to actions supported by the Xtremepush (Actions) destination.
Getting started
- From your workspace’s Destination catalog page search for “Xtremepush”.
- Select Xtremepush (Actions) and click Add destination.
- Select an existing Source to connect to Xtremepush (Actions), and click Next.
- Enter a name for your Xtremepush (Actions) destination and click Create destination.
- From the Segment destinations settings page, enter the “API Key” and “API Endpoint”. You can find these values in your Xtremepush Project under Settings > Integrations as described in the Xtremepush Segment integration user guide.
Destination Settings
Setting | Description |
---|---|
API Key | Required. Auth token for API can be found on the Xtremepush integration overview page |
URL | Required. Xtremepush integration URL can be found on the Xtremepush integration overview page |
Available Presets
Xtremepush (Actions) has the following presets:
Preset Name | Trigger | Default Action |
---|---|---|
Send Analytics Events | Event type = "track" |
Track |
Send User Profile Data | Event type = "identify" |
Identify |
Available Actions
Build your own Mappings. Combine supported triggers with the following Xtremepush-supported actions:
Mapping limits per destination
Individual destination instances have support a maximum of 50 mappings.
Track
Send Analytics Events to XtremePush
Track is a Cloud action. The default Trigger is: type = "track"
Field | Description |
---|---|
Event type* | Type: STRING The type of the event |
Identifiers | Type: OBJECT The unique identifiers for the user |
Event Name* | Type: STRING The name of the Segment track() event. |
Event Properties | Type: OBJECT The properties of the Segment track() event. |
Timestamp* | Type: STRING The timestamp of the event. |
Message ID* | Type: STRING The message ID of the event. |
Identify
Send User Profile Data to XtremePush
Identify is a Cloud action. The default Trigger is: type = "identify"
Field | Description |
---|---|
Event type* | Type: STRING The type of the event |
Identifiers | Type: OBJECT The unique identifiers for the user |
User Attributes | Type: OBJECT Attributes assocatiated with the user. |
Timestamp* | Type: STRING The timestamp of the event. |
Message ID* | Type: STRING The message ID of the event. |
Identify
If you’re not familiar with the Segment Specs, take a look to understand what the Identify method does. An example call would look like:
analytics.identify('userId123', {
email: 'john.doe@example.com',
phone: '1234567890',
firstName: 'John'
});
When you identify a user, Segment passes that user’s information to Xtremepush and creates a new user, if no profile exists with that user_id
, or updates an existing profile if the user_id
already exists.
Some user traits are also passed as additional user identifiers:
Segment Trait | Xtremepush User Identifier |
---|---|
phone | mobile_number |
For any additional traits you want to save, create User Profile Attributes in your Xtremepush Project.
If a trait does not match a custom Xtremepush User Profile Attribute and is not recognized as a User Identifier, Xtremepush ignores the trait.
Track
If you’re not familiar with the Segment Specs, take a look to understand what the Track method does. An example call would look like:
analytics.track('Product Purchased', {
productName: 'Some Product'
})
Track calls are sent to Xtremepush as a event hits
and you can use them to trigger a campaign for a user.
Event properties can be used as merge tags in the message content. You can also define additional rules on where to trigger the campaign based on event properties value.
Enabling Push and In-App Notifications
To enable Xtremepush push and in-app notifications you must also install the relevant Xtremepush SDKs.
This page was last modified: 17 May 2024
Need support?
Questions? Problems? Need more info? Contact Segment Support for assistance!