Skip to content

Commit 1557932

Browse files
author
markzegarelli
authored
Merge branch 'master' into evanSegment-clarify-object-throughput
2 parents de72b5e + e1e885b commit 1557932

File tree

9 files changed

+99
-14
lines changed

9 files changed

+99
-14
lines changed

.vscode/yml.code-snippets

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
{
2+
// Place your segment-docs workspace snippets here. Each snippet is defined under a snippet name and has a scope, prefix, body and
3+
// description. Add comma separated ids of the languages where the snippet is applicable in the scope field. If scope
4+
// is left empty or omitted, the snippet gets applied to all languages. The prefix is what is
5+
// used to trigger the snippet and the body will be expanded and inserted. Possible variables are:
6+
// $1, $2 for tab stops, $0 for the final cursor position, and ${1:label}, ${2:another} for placeholders.
7+
// Placeholders with the same ids are connected.
8+
// Example:
9+
// "Print to console": {
10+
// "scope": "javascript,typescript",
11+
// "prefix": "log",
12+
// "body": [
13+
// "console.log('$1');",
14+
// "$2"
15+
// ],
16+
// "description": "Log output to console"
17+
// }
18+
19+
"yml": {
20+
"prefix": ["- name"],
21+
"body":["- name: ${1:name}\r\tdescription: ${2:description}\r\tdefault: ${3}"],
22+
"description": "Yaml settings"
23+
}
24+
}

src/connections/destinations/catalog/ab-smartly/index.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,4 @@
11
---
2-
rewrite: true
32
title: AB Smartly Destination
43
---
54

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

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -15,11 +15,10 @@ This destination is maintained by OneSignal. For any issues with the destination
1515

1616
{% include content/connection-modes.md %}
1717

18-
1. From the Destinations catalog page in the Segment App, click **Add Destination**.
19-
1. Search for OneSignal in the Destinations Catalog, and select the OneSignal destination.
20-
1. Choose which Source should send data to the OneSignal destination.
21-
1. Go to the [OneSignal dashboard](https://app.onesignal.com/apps/){:target="_blank"}, select the Segment App, and go to the **Settings > Keys & IDs**. Copy the **App ID** and the **API key**.
22-
1. Enter the OneSignal **App ID** and the **API key** in the OneSignal destination settings in Segment.
18+
1. Log in to the [OneSignal Dashboard](https://app.onesignal.com/){:target="_new"}
19+
2. Navigate to **Segment App** -> **Settings** -> **Analytics** -> **Segment.com** and click **Activate**.
20+
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.
2322

2423

2524
> info ""

src/connections/destinations/catalog/optimizely-full-stack/index.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -164,7 +164,8 @@ Notification listeners are not available for Segment `track` events when impleme
164164

165165
Follow these instructions on how to set up Personas and Optimizely:
166166

167-
* [Using Segment Personas and Optimizely Full Stack for Omnichannel Experiments](https://www.optimizely.com/insights/blog/segment-personas-optimizely-full-stack-omnichannel-experiments/)
167+
* [Using Segment Personas and Optimizely Full Stack for Omnichannel Experiments](https://www.optimizely.com/insights/blog/segment-personas-optimizely-full-stack-omnichannel-experiments/){:target="_blank"}
168+
168169

169170
## GDPR Support
170171
Segment supports deleting/suppressing users in Optimizely using the [Segment app](/docs/privacy/user-deletion-and-suppression/). In order to do this however, you will need to create a [Personal Access Token](https://developers.optimizely.com/x/authentication/personal-token/) in Optimizely and provide it as the value of the Access Token setting.
Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
---
2+
title: ProsperStack Destination
3+
rewrite: true
4+
beta: true
5+
---
6+
7+
[ProsperStack](https://prosperstack.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) is the hosted cancellation flow for subscription businesses that automatically prevents churn. Retain customers with targeted offers and interventions designed to prevent cancellations and increase customer lifetime value.
8+
9+
ProsperStack maintains this destination. For any issues with the ProsperStack Destination, [contact the ProsperStack Support team](mailto:[email protected]).
10+
11+
> The ProsperStack Destination is currently in beta, and is actively developing. To join the beta program, or if you have any feedback to help improve the ProsperStack Destination and its documentation, [contact the ProsperStack support team](mailto:[email protected]).
12+
13+
## Getting Started
14+
15+
{% include content/connection-modes.md %}
16+
17+
### Automated setup
18+
19+
1. Log in to the [ProsperStack dashboard](https://app.prosperstack.com){:target="\_blank"}.
20+
2. Navigate to **Settings** > **Manage integrations**.
21+
3. Click **Configure** in the Segment integration section.
22+
4. Click **Connect Segment**.
23+
5. Select a Segment workspace and source to send to the ProsperStack Destination.
24+
25+
To add additional sources, click **Connect a source**.
26+
27+
### Manual setup
28+
29+
1. In the Segment app, go to **Connections** and click **Add Destination**.
30+
2. Search for "ProsperStack" in the Destinations Catalog, and select the **ProsperStack** destination.
31+
3. Click **Configure ProsperStack** and choose the source you want to connect the destination to.
32+
4. Create a new API key from the [ProsperStack API keys settings screen](https://app.prosperstack.com/settings/api-keys){:target="\_blank"}.
33+
5. Enter the **API Key** in the ProsperStack destination **Settings** tab in Segment.
34+
35+
## Supported methods
36+
37+
ProsperStack supports the following methods, as specified in the [Segment Spec](/docs/connections/spec).
38+
39+
### Identify
40+
41+
Send [Identify](/docs/connections/spec/identify) calls to ProsperStack to update subscriber custom properties in ProsperStack. For example:
42+
43+
```js
44+
analytics.identify("userId123", {
45+
46+
traits: {
47+
"Number of contacts": 5800,
48+
"Is professional": true,
49+
"Last contacted": "2021-05-04",
50+
"Preferred name": "Johnny",
51+
},
52+
});
53+
```
54+
55+
Segment sends Identify calls to ProsperStack as an `identify` event.
56+
57+
Custom traits specified in an Identify call update [custom properties](https://prosperstack.com/docs/custom-properties/){:target="\_blank"} for a corresponding subscriber in ProsperStack. You must specify an `email` in an Identify call in order for a ProsperStack subscriber to match with the Identify call.
58+
59+
Custom properties in ProsperStack that match the exact key of a trait update automatically. You can configure additional trait mappings in the [ProsperStack configuration dashboard](https://app.prosperstack.com/settings/integrations/segment){:target="\_blank"}.

src/connections/sources/catalog/libraries/mobile/android/index.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,9 @@
22
title: 'Analytics for Android'
33
strat: android
44
repo: analytics-android
5-
redirect_from: '/connections/sources/catalog/cloud-apps/kotlin-android/'
6-
redirect_from: '/connections/sources/catalog/cloud-apps/kotlin/'
5+
redirect_from:
6+
- '/connections/sources/catalog/cloud-apps/kotlin-android/'
7+
- '/connections/sources/catalog/cloud-apps/kotlin/'
78
---
89

910

src/connections/sources/catalog/libraries/website/javascript/upgrade-to-ajs2.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ Once a source moves to Analytics.js 2.0, you can follow the steps above in [Manu
3535

3636
## Cases that require additional intervention
3737

38-
There are two cases where upgrading to Analytics.js 2.0 requires manual effort beyond enabling the Analytics.js 2.0 toggle.
38+
In some cases, upgrading to Analytics.js 2.0 requires manual effort beyond enabling the Analytics.js 2.0 toggle.
3939

4040
### When using in-domain instrumentation CDN aliasing
4141

src/connections/sources/sources-compare.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ Cloud-App Sources allow you to pull in data from third-party tools so you can us
4343
<th width="30%"> Categories </th>
4444
<th> Data Type </th>
4545
</tr>
46-
{% assign integrations = site.data.catalog.sources.items %}
46+
{% assign integrations = site.data.catalog.sources_capi.items %}
4747
{% for integration in integrations %}
4848
{% unless integration.categories contains promoted_categories[0] or integration.categories contains promoted_categories[1] or integration.categories contains promoted_categories[2] or integration.categories contains promoted_categories[3]%}
4949
{% unless integration.display_name == "Project"%}

src/connections/storage/catalog/db2/index.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -66,11 +66,13 @@ Search for and select "Db2":
6666

6767
Add your credentials as follows:
6868

69-
- User (This is the "User ID" that you created above)
70-
- Password
7169
- Host (Found in Settings → Connection Info → Connection Information)
72-
- Port (50000 by default)
70+
- Port (50001 is Db2 Default)
7371
- Database name
72+
- User (This is the "User ID" that you created above)
73+
- Password
74+
- Security (Enter "SSL" in this field if applicable - optional)
75+
7476

7577
<img src="./images/settings.png" style="max-width: 540px">
7678

0 commit comments

Comments
 (0)