Skip to content

Commit e9a7aef

Browse files
committed
Changed terminology from nickname to name, added id and beta flag, clarified around null subject events
1 parent ca98bcd commit e9a7aef

File tree

1 file changed

+6
-6
lines changed
  • src/connections/sources/catalog/cloud-apps/white-label-loyalty

1 file changed

+6
-6
lines changed

src/connections/sources/catalog/cloud-apps/white-label-loyalty/index.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
---
22
title: White Label Loyalty Source
3+
id: xeZMgSrtAQ
4+
beta: true
35
---
46

57
[White Label Loyalty](https://whitelabel-loyalty.com/){:target="_blank”} is an event powered loyalty solution to drive customer retention.
@@ -12,9 +14,9 @@ This source is maintained by White Label Loyalty. For any issues with the source
1214

1315
1. From your workspace's [Sources catalog page](https://app.segment.com/goto-my-workspace/sources/catalog){:target="_blank”} click **Add Source**.
1416
2. Search for "White Label Loyalty" in the Sources Catalog, select White Label Loyalty, and click **Add Source**.
15-
3. On the next screen, give the Source a nickname configure any other settings.
17+
3. On the next screen, give the Source a name configure any other settings.
1618

17-
- The nickname is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. The nickname can be anything, but we recommend using something that reflects the source itself and distinguishes amongst your environments (eg. SourceName_Prod, SourceName_Staging, SourceName_Dev).
19+
- The name is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. The name can be anything, but we recommend using something that reflects the source itself and distinguishes amongst your environments (eg. WhiteLabel_Prod, WhiteLabel_Staging, WhiteLabel_Dev).
1820

1921
4. Click **Add Source** to save your settings.
2022
5. Copy the Write key from the Segment UI.
@@ -31,14 +33,12 @@ The default behavior is for White Label Loyalty to pass the authIdentifier assoc
3133

3234
## Events
3335

34-
White Label Loyalty will send all custom and intrinsic event types created in the White Label Loyalty Console, as per the schema provided when you set it up. White Label Loyalty will include the `userId` if available.
36+
White Label Loyalty will send all custom and intrinsic event types created in the White Label Loyalty Console, as per the schema provided when you set it up. White Label Loyalty will send all events reported against a user and include the `userId`.
3537

3638
## Adding Destinations
3739

3840
Now that your Source is set up, you can connect it with Destinations.
3941

4042
Log into your downstream tools and check to see that your events appear as expected, and that they contain all of the properties you expect. If your events and properties don’t appear, check the [Event Delivery](/docs/connections/event-delivery/) tool, and refer to the Destination docs for each tool for troubleshooting.
4143

42-
If there are any issues with how the events are arriving to Segment, [contact the White Label Loyalty support team](mailto:[email protected]).
43-
44-
---
44+
If there are any issues with how the events are arriving to Segment, [contact the White Label Loyalty support team](mailto:[email protected]).

0 commit comments

Comments
 (0)