You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[OneSignal](https://onesignal.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} is the market leader in driving customer engagement with multi-channel messaging across Web and Mobile Push, In-App Messages, SMS, and Email subscribers.
9
-
This destination is maintained by OneSignal. For any issues with the destination, [contact the OneSignal Support team](mailto:support@onesignal.com).
10
9
11
-
> info ""
12
-
> The OneSignal Destination is available to customers on OneSignal Growth, Professional and Enterprise plans.
13
-
14
-
## Getting Started
10
+
This destination is maintained by OneSignal. For any issues with the destination, [contact the OneSignal support team](mailto:support@onesignal.com){:target="_blank"}.
15
11
12
+
> info ""
13
+
> The OneSignal Destination is available to customers on OneSignal Growth, Professional, and Enterprise plans.
16
14
15
+
## Getting started
17
16
18
-
1. Log in to the [OneSignal Dashboard](https://app.onesignal.com/){:target="_blank"}
19
-
2. Navigate to **Segment App** -> **Settings** -> **Analytics** -> **Segment.com** and click **Activate**.
17
+
1. Log in to the [OneSignal dashboard](https://app.onesignal.com/){:target="_blank"}.
18
+
2. Navigate to **Segment App > Settings > Analytics > Segment.com** and click **Activate**.
20
19
3. The Segment App opens in a new window. Log in to authenticate the connection from OneSignal.
21
-
4. Select the Workspace and Source to connect with OneSignal.
22
-
20
+
4. Select the workspace and source to connect with OneSignal.
23
21
24
22
> info ""
25
23
> OneSignal maps the `userId` field to the **[External User ID](https://documentation.onesignal.com/docs/onboarding-with-onesignal#step-3-connect-user-data-to-onesignal){:target="_blank"}** field in OneSignal.
26
24
27
-
28
25
## Supported methods
29
26
30
27
OneSignal supports the following methods, as specified in the [Segment Spec](/docs/connections/spec).
31
28
32
29
### Identify
33
30
34
-
Send [Identify](/docs/connections/spec/identify) calls to update Users. For example:
31
+
Send [Identify](/docs/connections/spec/identify) calls to update users. For example:
35
32
36
33
```js
37
34
analytics.identify('userId123', {
@@ -62,39 +59,37 @@ analytics.track('Add to Cart', {
62
59
})
63
60
```
64
61
65
-
OneSignal stores Track properties as Data Tags but drops the eventname. In the above example, `Add to Cart` is dropped.
62
+
OneSignal stores Track properties as Data Tags but drops the eventname. In the example, `Add to Cart` is dropped.
66
63
67
64
To keep the event names on OneSignal Data Tags, append the event name to the properties. For example, `Add_to_Cart_brand` instead of`brand`.
68
65
69
-

66
+

70
67
71
68
## Engage
72
69
73
-
Send Computed Traits and Audiences generated using [Engage](/docs/engage) to OneSignal
70
+
You can send Computed Traits and Audiences generated using [Engage](/docs/engage) to OneSignal.
74
71
75
72
### Audiences
76
73
77
-
Engage Audiences appear as a [segment](https://documentation.onesignal.com/docs/segmentation){:target="_blank"} in OneSignal.
74
+
Engage audiences appear as a [segment](https://documentation.onesignal.com/docs/segmentation){:target="_blank"} in OneSignal.
78
75
79
-
TrackcallsfromAudiencescreateaOneSignal [segment](https://documentation.onesignal.com/docs/segmentation){:target="_blank"} with the Audience Name.
76
+
TrackcallsfromAudiencescreateaOneSignal [segment](https://documentation.onesignal.com/docs/segmentation){:target="_blank"} with the audience name.
80
77
81
-
IdentifycallsfromAudiencescreateaOneSignal [segment](https://documentation.onesignal.com/docs/segmentation){:target="_blank"} with the Audience Name and add Data Tags on all the matching user records.
78
+
IdentifycallsfromAudiencescreateaOneSignal [segment](https://documentation.onesignal.com/docs/segmentation){:target="_blank"} with the audience name and add Data Tags on all the matching user records.
OneSignalstoresTrackandIdentifycallsfromEngageComputedTraitsas [DataTags](https://documentation.onesignal.com/docs/add-user-data-tags){:target="_blank"} for the OneSignal User/Player's records.
90
87
91
-
## OneSignalDestinationFAQ
92
-
### ManagingSegment's Reserved and Custom Traits
93
-
94
-
* Segment sends user traits to OneSignal as Data Tags. The number of data tags OneSignal allows depends on your OneSignal pricing plan. OneSignal drops the data tags that go over your set number. .
95
-
96
-
* OneSignal always updates the `firstName` and the `lastName` properties for matching users. All other traits are added/updated on a first-come basis. `firstName` and `lastName` tags are stored as `first_name` and `last_name`.
88
+
## FAQ
97
89
98
-
* Send User properties to OneSignal with blank/null values to remove the corresponding Data Tag from the OneSignal user record.
90
+
#### HowdoImanageSegment's Reserved and Custom Traits?
99
91
92
+
* Segment sends user traits to OneSignal as Data Tags. The number of data tags OneSignal allows depends on your OneSignal pricing plan. OneSignal drops the data tags that go over your set number.
93
+
* OneSignal always updates the `firstName` and the `lastName` properties for matching users. All other traits are added or updated on a first-come basis. `firstName` and `lastName` tags are stored as `first_name` and `last_name`.
94
+
* Send User properties to OneSignal with blank or `null` values to remove the corresponding Data Tag from the OneSignal user record.
0 commit comments