Xtremepush (Actions) Destination

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.

1. From your workspace's Destination catalog page search for "Xtremepush".
2. Select Xtremepush (Actions) and click Add destination.
3. Select an existing Source to connect to Xtremepush (Actions), and click Next.
4. Enter a name for your Xtremepush (Actions) destination and click Create destination.
5. 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.

Xtremepush (Actions) has the following presets

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

• Track
• Identify

Send Analytics Events to XtremePush

Track is a Cloud action. The default Trigger is type = "track"

Send User Profile Data to XtremePush

Identify is a Cloud action. The default Trigger is type = "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:

1
analytics.identify('userId123', {
2
  email: 'john.doe@example.com',
3
  phone: '1234567890',
4
  firstName: 'John'
5
});

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:

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.

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:

1
analytics.track('Product Purchased', {
2
  productName: 'Some Product'
3
})

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.

To enable Xtremepush push and in-app notifications you must also install the relevant Xtremepush SDKs.

Xtremepush iOS SDK Docs

Xtremepush Android SDK Docs

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.