Skip to content

Commit 8a77fd0

Browse files
authored
Merge pull request #177 from segmentio/repo-sync
repo sync
2 parents 8b71b70 + a8c7ebb commit 8a77fd0

File tree

5 files changed

+17
-65
lines changed

5 files changed

+17
-65
lines changed

src/connections/destinations/catalog/actions-sprig-web/index.md

Lines changed: 2 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Sprig maintains this destination. For any issues with the destination, consult [
1818
<!-- In the section below, add your destination name where indicated. If you have a classic version of the destination, ensure that its documentation is linked as well. If you don't have a classic version of the destination, remove the second and third sentences. -->
1919

2020
> success ""
21-
> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Sprig Segment destination. There's also a page about the [non-Actions Sprig (formerly UserLeap) destination](/docs/connections/destinations/catalog/userleap/). Both of these destinations receive data from Segment.
21+
> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Sprig Segment destination. There's also a page about the [non-Actions Sprig Cloud (formerly UserLeap) destination](/docs/connections/destinations/catalog/userleap/). Both of these destinations receive data from Segment.
2222
2323
<!-- In the section below, explain the value of this actions-based destination over the classic version, if applicable. If you don't have a classic version of the destination, remove this section. -->
2424

@@ -42,8 +42,6 @@ Sprig (Actions) provides the following benefits over the classic Sprig destinati
4242

4343
<!-- The line below renders a table of connection settings (if applicable), Pre-built Mappings, and available actions. -->
4444

45-
{% include components/actions-fields.html name="sprig-web" connection="true" %}
46-
4745
## Pre-built subscriptions
4846

4947
By default, a new Sprig (Actions) destination comes with the following subscriptions.
@@ -66,14 +64,10 @@ Combine the supported [triggers](/docs/connections/destinations/actions/#compone
6664
- [Track Event](#track-event)
6765
- [Update User ID](#update-user-id)
6866

69-
{% include components/actions-fields.html name="sprig-web" %}
70-
7167
<!-- If applicable, add information regarding the migration from a classic destination to an Actions-based version below -->
7268

7369
## Migration from the classic Sprig destination
7470

75-
To prevent duplicate events from being tracked, please disable your existing Sprig destination when you enable Sprig (Actions).
71+
To prevent duplicate events being created in Sprig, ensure that for each Segment source, this destination and the Sprig Cloud destination are not both enabled at the same time.
7672

77-
Follow the table below to map your existing Sprig destination configuration to Sprig (Actions).
7873

79-
{% include components/actions-map-table.html name="sprig" %}
Lines changed: 9 additions & 52 deletions
Original file line numberDiff line numberDiff line change
@@ -1,63 +1,20 @@
11
---
2-
title: UserLeap
2+
title: Sprig Cloud Destination
33
rewrite: true
44
---
55

6-
[UserLeap](https://userleap.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) is a microsurvey platform that continuously identifies opportunities to build better experiences. Gain clarity into customer needs and grow faster.
6+
[Sprig (formerly UserLeap)](https://sprig.com/?&utm_source=segment_2021-10-20&utm_medium=int&utm_campaign=integration) is an in-context user research platform that makes it fast and effortless for product teams to learn from their actual customers in real time, through microsurveys, concept tests, and video questions.
77

8-
This destination is maintained by UserLeap. For any issues with the destination, contact [the UserLeap support team](mailto:support@userleap.com).
8+
Sprig maintains this destination. For any issues with the destination, consult [Sprig's documentation](https://docs.sprig.com/docs/segment) or contact [[email protected]](mailto:support@sprig.com).
99

10+
> success ""
11+
> **Good to know**: This page is about the [non-Actions Sprig (formerly UserLeap) destination](/docs/connections/destinations/catalog/userleap/). There's also a page about the [Actions-framework](/docs/connections/destinations/actions/) Sprig Segment destination. Both of these destinations receive data from Segment.
1012
## Getting Started
1113

1214
{% include content/connection-modes.md %}
1315

1416
1. From the Destinations catalog page in the Segment App, click **Add Destination**.
15-
2. Search for "UserLeap" in the Destinations Catalog, and select the UserLeap destination.
16-
3. Choose which Source should send data to the UserLeap destination.
17-
4. Go to the [UserLeap dashboard](https://app.userleap.com/settings/installation), find and copy the **API key**.
18-
5. Enter the UserLeap API Key that you copied in the UserLeap destination settings in Segment.
19-
20-
**Note**: UserLeap's Segment integration does not support In-Product Surveys
21-
22-
## Identify
23-
If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like:
24-
25-
```js
26-
analytics.identify('userId123', {
27-
firstName: 'Laura',
28-
lastName: 'Gibbon'
29-
})
30-
```
31-
32-
Use Segment's Identify method to identify your users in UserLeap. Segment `traits` map to UserLeap `attributes`.
33-
34-
**Important:** Only Identify calls can create new users in UserLeap.
35-
36-
## Track
37-
If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like:
38-
39-
```js
40-
analytics.track('Button Clicked');
41-
```
42-
43-
Use Track calls to track events and use them as filtering criteria for your Surveys.
44-
45-
Create Triggered Events in your UserLeap [Events dashboard](https://app.userleap.com/events) and map them to your Segment Track event names before you start sending Segment data to UserLeap.
46-
47-
## Page
48-
If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](/docs/connections/spec/page/) to learn about what it does. An example call would look like:
49-
50-
```js
51-
analytics.page()
52-
```
53-
54-
Segment sends Page calls to UserLeap as a `pageview` which you can use as filtering criteria for your surveys.
55-
56-
Add Page URLs in your UserLeap [Events dashboard](https://app.userleap.com/events) and map them to your Segment Page call's `properties.url` field before you start sending Segment data to UserLeap.
57-
58-
## Alias
59-
If you aren't familiar with the Segment Spec, take a look at the [Alias method documentation](/docs/connections/spec/alias/) to learn about what it does. An example call would look like:
60-
61-
```js
62-
analytics.alias('newUserId');
63-
```
17+
2. Search for "Sprig Cloud" in the Destinations Catalog, and select the Sprig Cloud destination.
18+
3. Choose which Source should send data to the Sprig Cloud destination.
19+
4. Go to the [Sprig Connect page](https://app.sprig.com/connect), and find and copy the Segment **API key**. Use the Development key for a testing environment, and the Production key for your live environment.
20+
5. Enter the API Key that you copied in the Sprig Cloud destination settings in Segment.

src/connections/sources/catalog/libraries/website/shopify-littledata/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,7 @@ Below is a table of events that **Shopify by Littledata** sends to Segment from
9696
| Order Completed | A prospect has completed an order |
9797
| Order Refunded | An order has been refunded |
9898
| POS Order Placed (v2) | A user has placed an order through Shopify POS |
99-
| Payment Failure (v2) | A user completed checkout step 3 but the payment method failed (for example, the card details were valid but the [charge did not succeed(https://stripe.com/docs/testing#cards-responses)]) |
99+
| Payment Failure (v2) | A user completed checkout step 3 but the payment method failed (for example, the card details were valid but the [charge did not succeed](https://stripe.com/docs/testing#cards-responses)) |
100100
| Payment Info Entered | A user has entered payment info |
101101
| Product Added | A user has added a product to the cart, and left it in the cart for more than 10 seconds |
102102
| Product Removed | A user has removed a product from the cart |

src/personas/sql-traits.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -152,9 +152,10 @@ If you are sending data from [object cloud sources](/docs/connections/sources/#c
152152

153153
When you're building your query, keep the following requirements in mind for the data your query returns.
154154

155-
- The query must return a column with a `user_id`, `email`, or `anonymous_id` (or `group_id` for account traits, if you have Personas for B2B enabled).
156-
- It must return at least one additional trait in addition to `user_id`/`group_id`, and no more than 25 total columns.
157-
- The query must not return any `user_id`s with a `null` value, or any duplicate `user_id`s.
155+
- The query must return a column with a `user_id`, `email`, or `anonymous_id` (or `group_id` for account traits, if you have Personas for B2B enabled). The query _cannot_ include values for both `user_id` and `anonymous_id`.
156+
- The query must return at least one trait in addition to `user_id`/`anonymous_id`/`email`/`group_id`, and no more than 25 total columns.
157+
- The query must not return any `user_id`s, `anonymous_id`s, or `group_id`s with a `null` value.
158+
- The query must not return any records with duplicate `user_id`s.
158159
- The query must not return more than 25 million rows.
159160
- Each record must be less than 16kb in size to adhere to [Segment's maximum request size](/docs/connections/sources/catalog/libraries/server/http-api/#max-request-size).
160161

src/personas/using-personas-data.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,7 @@ List destinations can only receive Audiences, and cannot receive computed traits
8888

8989
When syncing to a list destination Personas uploads lists of users directly to the destination. When you first create an audience, Segment uploads the entire list of audience users to the destination. Later syncs only upload the users that have been added or removed since the last sync.
9090

91-
User-list destinations can have individual limits on how often Segment can sync with them. For example, an AdWords audience is updated once every 6 hours or more, because that is what AdWords recommends.
91+
User-list destinations can have individual limits on how often Segment can sync with them. For example, an AdWords audience is updated once every six hours or more, because that is what AdWords recommends.
9292

9393

9494
## What do the payloads look like for Personas data?

0 commit comments

Comments
 (0)