Skip to content

Commit 22f027b

Browse files
authored
style guide clean up
Updated text for clarity and consistency, including links and formatting adjustments.
1 parent 0ade561 commit 22f027b

File tree

1 file changed

+20
-25
lines changed
  • src/connections/destinations/catalog/onesignal-new

1 file changed

+20
-25
lines changed

src/connections/destinations/catalog/onesignal-new/index.md

Lines changed: 20 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -6,32 +6,29 @@ redirect_from: '/connections/destinations/catalog/onesignal/'
66
id: 60b6a5b69fec493efbd3c64c
77
---
88
[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).
109

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"}.
1511

12+
> info ""
13+
> The OneSignal Destination is available to customers on OneSignal Growth, Professional, and Enterprise plans.
1614
15+
## Getting started
1716

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**.
2019
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.
2321

2422
> info ""
2523
> 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.
2624
27-
2825
## Supported methods
2926

3027
OneSignal supports the following methods, as specified in the [Segment Spec](/docs/connections/spec).
3128

3229
### Identify
3330

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:
3532

3633
```js
3734
analytics.identify('userId123', {
@@ -62,39 +59,37 @@ analytics.track('Add to Cart', {
6259
})
6360
```
6461

65-
OneSignal stores Track properties as Data Tags but drops the event name. In the above example, `Add to Cart` is dropped.
62+
OneSignal stores Track properties as Data Tags but drops the event name. In the example, `Add to Cart` is dropped.
6663

6764
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`.
6865

69-
![""](images/track-example.png)
66+
![Screenshot of the OneSignal dashboard showing a notification for an "eShoppe" campaign.](images/track-example.png)
7067

7168
## Engage
7269

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.
7471

7572
### Audiences
7673

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.
7875

79-
Track calls from Audiences create a OneSignal [segment](https://documentation.onesignal.com/docs/segmentation){:target="_blank"} with the Audience Name.
76+
Track calls from Audiences create a OneSignal [segment](https://documentation.onesignal.com/docs/segmentation){:target="_blank"} with the audience name.
8077

81-
Identify calls from Audiences create a OneSignal [segment](https://documentation.onesignal.com/docs/segmentation){:target="_blank"} with the Audience Name and add Data Tags on all the matching user records.
78+
Identify calls from Audiences create a OneSignal [segment](https://documentation.onesignal.com/docs/segmentation){:target="_blank"} with the audience name and add Data Tags on all the matching user records.
8279

83-
![""](images/audiences.jpg)
80+
![Screenshot of the OneSignal "eShoppe" dashboard](images/audiences.jpg)
8481

8582
Audiences sends Identify and Track calls to OneSignal when a user enters or exits the Audience.
8683

8784
### Computed Traits
8885

8986
OneSignal stores Track and Identify calls from Engage Computed Traits as [Data Tags](https://documentation.onesignal.com/docs/add-user-data-tags){:target="_blank"} for the OneSignal User/Player's records.
9087

91-
## OneSignal Destination FAQ
92-
### Managing Segment'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
9789

98-
* Send User properties to OneSignal with blank/null values to remove the corresponding Data Tag from the OneSignal user record.
90+
#### How do I manage Segment's Reserved and Custom Traits?
9991
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.
10095
* OneSignal doesn't store `email` and `phone` properties. To update `email` and `phone` properties in OneSignal, create a player record with the email address and/or a phone number and map those records with the External_User_ID. Additional properties from Segment map across all your matching records, including email and phone number records.

0 commit comments

Comments
 (0)