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
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/userlist/index.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,9 +2,9 @@
2
2
rewrite: true
3
3
title: Userlist Destination
4
4
---
5
-
[Userlist.io](https://userlist.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) allows you to send behavior-based messages to your SaaS users. It's great for onboarding users as well as nurturing them throughout their journey.
5
+
[Userlist](https://userlist.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) allows you to send behavior-based messages to your SaaS users. It's great for onboarding users as well as nurturing them throughout their journey.
6
6
7
-
This destination is maintained by Userlist.io. For any issues with the destination, [contact the Userlist Support team](mailto:support@userlist.io).
7
+
This destination is maintained by Userlist. For any issues with the destination, [contact the Userlist Support team](mailto:support@userlist.com).
8
8
9
9
{% include content/beta-note.md %}
10
10
@@ -15,9 +15,9 @@ This destination is maintained by Userlist.io. For any issues with the destinati
15
15
16
16
1. From the Segment web app, click **Catalog**.
17
17
2. Search for "Userlist" in the Catalog, select it, and choose which of your sources to connect the destination to.
18
-
3. Enter the "Push API Key" into your Segment Settings UI which you can find from your [Userlist.io Push API settings](https://app.userlist.io/settings/push).
18
+
3. Enter the "Push API Key" into your Segment Settings UI which you can find from your [Userlist Push API settings](https://app.userlist.com/settings/push).
19
19
20
-
_**NOTE:** The Userlist.io Destination does not support tracking of anonymous users, so make sure to call `identify` before calling `track`. If you do call `track` on unidentified users, you will receive a 400 error which you can disregard if it was intentional._
20
+
_**NOTE:** The Userlist Destination does not support tracking of anonymous users, so make sure to call `identify` before calling `track`. If you do call `track` on unidentified users, you will receive a 400 error which you can disregard if it was intentional._
21
21
22
22
## Identify
23
23
@@ -30,7 +30,7 @@ If you're not familiar with the Segment Specs, take a look to understand what th
30
30
createdAt: '2019-03-21T12:12:54.735+01:00'
31
31
});
32
32
33
-
Identify calls will be sent to Userlist.io as user records. If the `userId` is already known, it'll update the user record, otherwise it'll create a new one.
33
+
Identify calls will be sent to Userlist as user records. If the `userId` is already known, it'll update the user record, otherwise it'll create a new one.
34
34
35
35
Here's how Segment fields map to Userlist users:
36
36
@@ -50,4 +50,4 @@ If you're not familiar with the Segment Specs, take a look to understand what th
50
50
projectName: 'Party Planning'
51
51
});
52
52
53
-
Track calls will be sent to Userlist.io as a new event. You may send additional properties to describe the event in more detail. Both the event name and additional properties will be stored with the event and normalized to snake case (`project_created` and `project_name`) automatically within Userlist.io.
53
+
Track calls will be sent to Userlist as a new event. You may send additional properties to describe the event in more detail. Both the event name and additional properties will be stored with the event and normalized to snake case (`project_created` and `project_name`) automatically within Userlist.
0 commit comments