Skip to content

Commit 10fb13a

Browse files
markzegarelliBarak Gilarchinn1
authored
Sprig actions (#2271)
* sprig action destination documentation * apply new template, hide until released * Minor edits * Apply suggestions from review * hide for now Co-authored-by: Barak Gila <[email protected]> Co-authored-by: rchinn-segment <[email protected]>
1 parent 64ebffe commit 10fb13a

File tree

1 file changed

+55
-0
lines changed
  • src/connections/destinations/catalog/actions-sprig-web

1 file changed

+55
-0
lines changed
Lines changed: 55 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
---
2+
# The end name should be similar to `Slack (Actions) Destination`
3+
title: Sprig (Actions) Destination
4+
hide-boilerplate: true
5+
hide-dossier: true
6+
hidden: true
7+
---
8+
9+
<!-- In the section above, edit the `title` field. For example, Slack (Actions) Destination -->
10+
11+
{% include content/plan-grid.md name="actions" %}
12+
13+
[Sprig (formerly UserLeap)](https://sprig.com/?&utm_source=segmentio&utm_medium=docs_actions&utm_campaign=integration){:target="_blank"} 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.
14+
15+
This destination is maintained by Sprig. For any issues with the destination, contact [[email protected]](mailto:[email protected]).
16+
17+
18+
<!-- 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. -->
19+
20+
> 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.
22+
23+
<!-- 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. -->
24+
25+
## Benefits of Sprig (Actions) vs Sprig Classic
26+
27+
Sprig (Actions) provides the following benefits over the classic Sprig destination:
28+
29+
- **Trigger microsurveys**. Because Sprig (Actions) hooks into your browser-based, JavaScript Segment source, it can be used to trigger Sprig microsurveys.
30+
- **Code-free Sprig installation**. The Sprig (Actions) destination can install the Sprig SDK onto your website, without you having to update any code.
31+
32+
<!-- The section below explains how to enable and configure the destination. Include any configuration steps not captured below. For example, obtaining an API key from your platform and any configuration steps required to connect to the destination. -->
33+
34+
## Getting started
35+
36+
1. From the Segment web app, click **Catalog**, then click **Destinations**.
37+
2. Use the navigation on the left to locate and select Sprig (Actions).
38+
3. Click **Configure Sprig (Actions)**.
39+
4. Select an existing JavaScript website source to connect to Sprig (Actions).
40+
5. Find your Environment ID on [Sprig Dashboard > Connect > JavaScript](https://app.sprig.com/connect){:target="_blank"}. Use the Development Environment ID for a testing environment, and the Production Environment ID for your live website environment. When you configure the destination, input the appropriate Environment ID.
41+
6. Select **Quick Setup** to start with pre-populated subscriptions, or **Customized Setup** to configure each action from scratch. Click **Configure Actions** to complete setup.
42+
43+
<!-- The line below renders a table of connection settings (if applicable), Pre-built Mappings, and available actions. -->
44+
45+
{% include components/actions-fields.html %}
46+
47+
<!-- If applicable, add information regarding the migration from a classic destination to an Actions-based version below -->
48+
49+
## Migration from the classic Sprig destination
50+
51+
<!-- Include any pertinent information here. -->
52+
53+
To prevent duplicate events being tracked, please disable your existing Sprig destination when you enable Sprig (Actions).
54+
55+
Follow the table below to map your existing Sprig destination configuration to Sprig (Actions).

0 commit comments

Comments
 (0)