Skip to content

Commit 234d482

Browse files
pwsegstayseesong
authored andcommitted
Update index.md
1 parent bac3a14 commit 234d482

File tree

1 file changed

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

1 file changed

+2
-2
lines changed

src/connections/destinations/catalog/attentive-mobile/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ This destination is maintained by Attentive Mobile. For any issues with the dest
1717

1818
### Installing from Segment
1919

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).
20+
Note: To install an additional Attentive destination from the Segment UI, the integration must already be installed in Attentive. If you've not already done so, please follow [the Installing From Attentive steps](#installing-from-attentive).
2121

2222
1. From the Destinations catalog page in the Segment App, click **Add Destination**.
2323
2. Search for "Attentive Mobile" in the Destinations Catalog, and select the "Attentive Mobile" destination.
@@ -44,7 +44,7 @@ Segment sends Identify calls to Attentive Mobile as an `identify` event. The eve
4444

4545
It may take up to 10 minutes for the `identify` attributes to appear in Attentive.
4646

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.
47+
> Note: For the Attentive destination to work best, 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.
4848
4949
### Track
5050

0 commit comments

Comments
 (0)