Skip to content

Commit cf6e848

Browse files
Merge pull request #6528 from xtremepush/actions-xtremepush/destination
Add Xtremepush (Actions) Destination docs.
2 parents 86676ea + 75bef8d commit cf6e848

File tree

1 file changed

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

1 file changed

+78
-0
lines changed
Lines changed: 78 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,78 @@
1+
---
2+
title: Xtremepush (Actions) Destination
3+
beta: true
4+
hidden: false
5+
id: 661e9787658d112ba31b59a7
6+
versions:
7+
- name: Xtremepush Destination
8+
link: /docs/connections/destinations/catalog/xtremepush/
9+
---
10+
{% include content/plan-grid.md name="actions" %}
11+
12+
[Xtremepush](https://xtremepush.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} 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.
13+
14+
This destination is maintained by Xtremepush. For any issues with the destination, [contact the Xtremepush Support team](mailto:[email protected]).
15+
16+
## Benefits of Xtremepush (Actions) vs Xtremepush Classic
17+
18+
Xtremepush (Actions) provides the following benefits over the classic Xtremepush destination:
19+
20+
- **Easier setup**: Users see fewer initial settings which can decrease the time spent configuring the destination.
21+
- **Increased transparency**: Users can see both the exact data that is sent to the destination and the time that Segment sent it.
22+
- **Improved customization**: Users can determine how the events their sources trigger map to actions supported by the Xtremepush (Actions) destination.
23+
24+
## Getting started
25+
26+
1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank”} search for "Xtremepush".
27+
2. Select **Xtremepush (Actions)** and click **Add destination**.
28+
3. Select an existing Source to connect to **Xtremepush (Actions)**, and click **Next**.
29+
4. Enter a name for your Xtremepush (Actions) destination and click **Create destination**.
30+
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](https://docs.xtremepush.com/docs/segment){:target="_blank"}.
31+
32+
{% include components/actions-fields.html %}
33+
34+
## Identify
35+
36+
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:
37+
38+
```
39+
analytics.identify('userId123', {
40+
41+
phone: '1234567890',
42+
firstName: 'John'
43+
});
44+
```
45+
46+
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.
47+
48+
Some user traits are also passed as additional user identifiers:
49+
50+
| Segment Trait | Xtremepush User Identifier |
51+
| ------------- | -------------------------- |
52+
| email | email |
53+
| phone | mobile_number |
54+
55+
For any additional traits you want to save, create [User Profile Attributes](https://docs.xtremepush.com/docs/attributes-tags){:target="_blank"} in your Xtremepush Project.
56+
57+
If a trait does not match a custom Xtremepush User Profile Attribute and is not recognized as a User Identifier, Xtremepush ignores the trait.
58+
59+
## Track
60+
61+
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:
62+
63+
```
64+
analytics.track('Product Purchased', {
65+
productName: 'Some Product'
66+
})
67+
```
68+
69+
Track calls are sent to Xtremepush as a `event hits` and you can use them to [trigger a campaign](https://docs.xtremepush.com/docs/campaign-events){:target="_blank"} for a user.
70+
71+
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.
72+
73+
## Enabling Push and In-App Notifications
74+
To enable Xtremepush push and in-app notifications you must also install the relevant Xtremepush SDKs.
75+
76+
[Xtremepush iOS SDK Docs](https://docs.xtremepush.com/docs/ios-integration){:target="_blank"}
77+
78+
[Xtremepush Android SDK Docs](https://docs.xtremepush.com/docs/android-integration){:target="_blank"}

0 commit comments

Comments
 (0)