Skip to content

Commit bac3a14

Browse files
Thomas Gilbertstayseesong
authored andcommitted
add docs for new attentive mobile destination
1 parent f99f4bb commit bac3a14

File tree

1 file changed

+59
-0
lines changed
  • src/connections/destinations/catalog/attentive-mobile

1 file changed

+59
-0
lines changed
Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
---
2+
title: Attentive Mobile Destination
3+
id: 62bcba2e1db8cc043e95f370
4+
---
5+
6+
[Attentive Mobile](https://www.attentivemobile.com/?utm_source=partner-generated&utm_medium=partner-marketing-&utm_campaign=partner-generated-4.15.22-segment.io) with Segment makes it easy to sync customer and event data from Segment to Attentive so that you can send highly personalized and timely messages.
7+
8+
This destination is maintained by Attentive Mobile. For any issues with the destination, [contact the Attentive Mobile Support team](mailto:[email protected]).
9+
10+
## Getting Started
11+
12+
{% include content/connection-modes.md %}
13+
14+
### Installing from Attentive
15+
16+
1. Follow the the [Attentive documentation](https://docs.attentivemobile.com/pages/developer-guides/third-party-integrations/customer-data-platforms/segment/) to install the Segment integration in Attentive.
17+
18+
### Installing from Segment
19+
20+
Note: To be able to install an additional Attentive destination from the Segment UI, the integration must already be installed in Attentive. If not already done so, please follow [the Installing From Attentive steps](#installing-from-attentive).
21+
22+
1. From the Destinations catalog page in the Segment App, click **Add Destination**.
23+
2. Search for "Attentive Mobile" in the Destinations Catalog, and select the "Attentive Mobile" destination.
24+
3. Choose which Source should send data to the "Attentive Mobile" destination.
25+
4. Go to the [Attentive Mobile dashboard](https://www.ui.attentivemobile.com/integrations){:target="\_blank"}. Find and select the installed 'Segment (Beta)' integration. In the settings page, find and copy the "API key".
26+
5. Enter the "API Key" in the "Attentive Mobile" destination settings in Segment.
27+
28+
## Supported methods
29+
30+
The Attentive Mobile destination supports the following methods, as specified in the [Segment Spec](/docs/connections/spec).
31+
32+
### Identify
33+
34+
Send [Identify](/docs/connections/spec/identify) calls to add attributes to the Attentive subscriber. These attributes are used to target Attentive subscribers in the [Attentive Segments product](https://help.attentivemobile.com/hc/en-us/categories/360004558392-Subscriber-segments). For example:
35+
36+
```js
37+
analytics.identify("userId123", {
38+
phone: "+13334445555",
39+
favoriteColor: "red",
40+
});
41+
```
42+
43+
Segment sends Identify calls to Attentive Mobile as an `identify` event. The event's `traits` are saved to the Attentive subscriber with phone `+13334445555`.
44+
45+
It may take up to 10 minutes for the `identify` attributes to appear in Attentive.
46+
47+
> Note: For the Attentive destination to work best, it's desirable to send at least one identify call that contains both 1) the Segment userId, and 2) an email and/or phone. This allows Attentive to "link" the Segment UserId with an Attentive subscriber.
48+
49+
### Track
50+
51+
Send [Track](/docs/connections/spec/track) calls to save the event to the Attentive subscriber as an Attentive "Custom Event". These events are used to target Attentive subscribers. For example:
52+
53+
```js
54+
analytics.track("Login Button Clicked");
55+
```
56+
57+
Segment sends Track calls to Attentive Mobile as a `track` event. The event is saved to the Attentive subscriber, and is usable in both the [Attentive Segments product](https://help.attentivemobile.com/hc/en-us/categories/360004558392-Subscriber-segments) and the [Attentive Journeys product](https://help.attentivemobile.com/hc/en-us/categories/6084285157396).
58+
59+
It may take up to 10 minutes for the track events to appear in Attentive.

0 commit comments

Comments
 (0)