Skip to content

Commit 779f31f

Browse files
author
Ivan Vovchak
committed
Add Xtremepush (Actions) Destination docs.
1 parent 9ab735d commit 779f31f

File tree

1 file changed

+74
-0
lines changed
  • src/connections/destinations/catalog/actions-xtremepush

1 file changed

+74
-0
lines changed
Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
---
2+
title: Xtremepush (Actions) Destination
3+
---
4+
{% include content/plan-grid.md name="actions" %}
5+
6+
[Xtremepush](https://xtremepush.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} is a complete digital engagement platform. Empowering global brands to create personalised, 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.
7+
8+
This destination is maintained by Xtremepush. For any issues with the destination, [contact the Xtremepush Support team](mailto:[email protected]).
9+
10+
> success ""
11+
> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Xtremepush (Actions) Segment destination. There's also a page about the [classic Xtremepush destination](/docs/connections/destinations/catalog/xtremepush/). Both of these destinations receive data from Segment.
12+
13+
## Benefits of Xtremepush (Actions) vs Xtremepush Classic
14+
15+
Xtremepush (Actions) provides the following benefits over the classic Xtremepush destination:
16+
17+
- **Easier setup**. Users see fewer initial settings which can decrease the time spent configuring the destination.
18+
- **Increased transparency**. Users can see the exact data that is sent to the destination, and when Segment sends it.
19+
- **Improved customization**. Users can determine how the events their sources trigger and map to actions supported by the destination.
20+
21+
## Getting started
22+
23+
1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank”} search for "Xtremepush"
24+
2. Select **Xtremepush (Actions)** and click **Add Destination**
25+
3. Select an existing Source to connect to **Xtremepush (Actions)**.
26+
4. Enter the "API Key" and "API Endpoint" into your Segment Settings UI which you can find from your Xtremepush Project under *Settings > Integrations* as described in the [user guide](https://docs.xtremepush.com/docs/segment){:target="_blank"}.
27+
28+
{% include components/actions-fields.html %}
29+
30+
## Identify
31+
32+
If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like:
33+
34+
```
35+
analytics.identify('userId123', {
36+
37+
phone: '1234567890',
38+
firstName: 'John'
39+
});
40+
```
41+
42+
When you identify a user, we'll pass that user's information to Xtremepush and will try to update or create a new user based on whether a Profile exists with that `user_id`.
43+
44+
Some special traits will also be used as additional user identifiers:
45+
46+
| Segment Trait | Xtremepush User Identifier |
47+
| ------------- | -------------------------- |
48+
| email | email |
49+
| phone | mobile_number |
50+
51+
For any additional traits you want to save you should create [User Profile Attributes](https://docs.xtremepush.com/docs/attributes-tags){:target="_blank"} in your Xtremepush Project.
52+
53+
If a trait does not match a custom Xtremepush User Profile Attribute and is not recognized as a User Identifier it will be ignored.
54+
55+
## Track
56+
57+
If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like:
58+
59+
```
60+
analytics.track('Product Purchased', {
61+
productName: 'Some Product'
62+
})
63+
```
64+
65+
Track calls will be sent to Xtremepush as a `event hits`, so you can use it to [trigger a campaign](https://docs.xtremepush.com/docs/campaign-events){:target="_blank"} for a user.
66+
67+
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.
68+
69+
## Enabling Push and In-App Notifications
70+
To enable Xtremepush push and in-app notifications you will also need to to install the relevant Xtremepush SDKs.
71+
72+
[Xtremepush iOS SDK Docs](https://docs.xtremepush.com/docs/ios-integration){:target="_blank"}
73+
74+
[Xtremepush Android SDK Docs](https://docs.xtremepush.com/docs/android-integration){:target="_blank"}

0 commit comments

Comments
 (0)