Skip to content

Commit 198f1fc

Browse files
author
markzegarelli
committed
Merge branch 'develop' of github.com:segmentio/segment-docs into develop
2 parents 9dbb0ba + e915ff5 commit 198f1fc

File tree

2 files changed

+45
-40
lines changed
  • src/connections
    • destinations/catalog/actions-upollo
    • sources/catalog/cloud-apps/voucherify

2 files changed

+45
-40
lines changed

‎src/connections/destinations/catalog/actions-upollo/index.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -5,24 +5,24 @@ id: 640267d74c13708d74062dcd
55

66
{% include content/plan-grid.md name="actions" %}
77

8-
[Upollo](https://upollo.ai?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} finds and converts repeat trialers, account sharers and more.
8+
[Upollo](https://upollo.ai?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} gives unique and actionable insights that lead to conversion, retention and expansion.
99

10-
11% of users signing up for free trials have [already had a free trial](https://upollo.ai/blog/turn-repeated-trials-into-growth?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"}, and up to 45% of users [share their logins](https://upollo.ai/blog/grow-by-understanding-account-sharing?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} with others.
11-
Inviting these users to a paid account is the top underutilized growth channel for SaaS businesses.
10+
Understand who your users truly are, if they are ready to convert, churn or expand and why they are ready. Upollo provices unique insights from users who are ready to convert because they have [already had a free trial](https://upollo.ai/blog/turn-repeated-trials-into-growth?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"}, a company ripe for a team wide roll out because they [share logins](https://upollo.ai/blog/grow-by-understanding-account-sharing?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} or finding high intent companies [hidden behind public emails](https://upollo.ai/blog/hidden-goldmine-public-emails).
11+
12+
Upollo also enriches your identify data with firmopgrahic data so you can understand your users in Upollo or in your data warehouse. See company name, size and industry for your users as soon as they sign in, for free at unlimited scale.
1213

1314
Upollo maintains this destination. For any questions or issues with the destination, please [contact the Upollo team](https://upollo.ai/contact?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"}.
1415

1516
## Benefits of Upollo (Actions)
1617

1718
Upollo (Actions) provides the following benefits:
1819

19-
- **Find hidden growth opportunities**. Quickly see how many users are repeating free trials or sharing their account.
20+
- **Find hidden growth opportunities**. Quickly see opportunities to convert, retain and expand.
2021
- **More happy paying customers**. Upgrade these users onto a paying plan and get more happy paying users.
2122

2223
## Getting Started
2324

24-
25-
1. From the Segment web app, navigate to **Connections > Catalog**, and select the **Destinations** tab.
25+
1. From the Segment web app, navigate to **Connections > Catalog**, and select the **Destinations** tab.
2626
2. Select **Destinations Actions** under **Categories** in the left navigation.
2727
3. Search for **Upollo (Actions)** and click **Configure Upollo**.
2828
4. Select an existing Source to connect to Upollo (Actions).
@@ -31,15 +31,15 @@ Upollo (Actions) provides the following benefits:
3131

3232
## Identify
3333

34-
Upollo uses the `identify` call to analyze users on your platform. If the same person is using multiple accounts or if different people are sharing an account, they are flagged and shown in the Upollo dashboard.
35-
34+
Upollo uses the `identify` call to analyze users on your platform. Our unique insights shown in the Upollo dashboard and optionally enriched data is added to identify events.
3635

3736
The `identify` call provides any available information about the user.
37+
3838
```js
39-
analytics.identify('userId123', {
40-
email: '[email protected]',
41-
name: 'John Doe',
42-
phone: '+123456789'
39+
analytics.identify("userId123", {
40+
email: "[email protected]",
41+
name: "John Doe",
42+
phone: "+123456789",
4343
});
4444
```
4545

‎src/connections/sources/catalog/cloud-apps/voucherify/index.md

Lines changed: 33 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -25,54 +25,59 @@ This source is maintained by Voucherify. For any issues with the source, [contac
2525

2626
Voucherify uses the stream Source component to send Segment event data. It uses a server-side `track` method to send data to Segment. These events are then available in any destination that accepts server-side events, and available in a schema in your data warehouse, so you can query using SQL. These events are also assigned to user accounts in the Segment Profiles (Unify).
2727

28-
The default behavior is for Voucherify to pass the `userId` associated with the customer. There are cases in which Voucherify does not have an associated `userId`, and then the customer will be associated with an `anonymousId`. 
28+
By default, Voucherify passes a customer's associated `userId` to Segment. Because Voucherify sends customer-triggered events only, `anonymousId` is not used. The Voucherify source doesn't send anonymous events to Segment. As a result, events that aren't assigned to or called by a customer are ignored. For mapping, `source_id` on Voucherify events becomes the `user_id` in Segment.
2929

3030
## Events
3131
Integrating by adding Voucherify as a Source to Segment supports the following events to be sent out of the box:
3232
- Redemption events (successful, failed, rolled back).
3333
- Validation events (only if connected with a customer).
34+
- Publication events.
3435
- Customer reward events.
3536

3637
Below are the events that Voucherify sends to Segment. These events appear as tables in your warehouse and as regular events in other Destinations. Voucherify includes the `userId` if available.
3738

3839
### Redemption events
39-
| Event | Description |
40-
| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
41-
| Redemption succeeded | Triggered when a redemption is successfully completed by a customer (successful use of a voucher to receive a discount or other reward). |
42-
| Redemption failed | Triggered when a redemption attempt fails due to an issue with the voucher or customer. |
43-
| Redemption rollback succeeded | Triggered when a redemption is successfully rolled back, which means removal of the voucher and reversal of any associated discount or reward. |
44-
| Redemption rollback failed | Triggered when an attempt to rollback the redemption fails. |
40+
| Event | Description | Fields |
41+
|----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|
42+
| Customer Redemption Succeeded | Triggered when a redemption is successfully completed by a customer (successful use of a voucher to receive a discount or other reward). | order (object), promotion_tier (object), redemption (object), voucher (object), holder (object) |
43+
| Customer Redemption Failed | Triggered when a redemption attempt fails due to an issue with the voucher or customer. | order (object), promotion_tier (object), redemption (object), voucher (object), holder (object) |
44+
| Customer Redemption Rollback Succeeded | Triggered when a redemption is successfully rolled back, which means removal of the voucher and reversal of any associated discount or reward. | order (object), promotion_tier (object), redemption (object), redemption_rollback (object), voucher (object), holder (object) |
45+
| Customer Redemption Rollback Failed | Triggered when an attempt to roll back the redemption fails. | order (object), promotion_tier (object), redemption (object), redemption_rollback (object), voucher (object), holder (object) |
4546

4647
### Customer rewarded events
47-
48-
| Event | Description |
49-
| -------------------------------------------- | ------------------------------------------------------------------------------------------- |
50-
| Customer creates a reward redemption request | Triggered when a customer redeems a reward in Voucherify account. |
51-
| Customer reward redemption completed | Triggered when a customer's redemption request is completed (customer received the reward). |
52-
| Reward redemption created | Triggered when a reward redemption is created. |
53-
| Reward redemption completed | Triggered when a reward redemption is successfully completed. |
54-
| Customer rewarded | Triggered when a customer is rewarded with a main reward. |
55-
| Customer rewarded with loyalty points | Triggered when a customer is rewarded with loyalty points. |
56-
57-
48+
| Event | Description | Fields |
49+
|---------------------------------------|---------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|
50+
| Customer Reward Redemptions Created | Triggered when a customer redeems a reward in Voucherify account. | reward (object), reward_assignment (object), reward_redemption (object), voucher (object), source (object), holder (object), balance |
51+
| Customer Reward Redemptions Completed | Triggered when a customer's redemption request is completed (customer received the reward). | reward (object), reward_assignment (object), reward_redemption (object), voucher (object), source (object), holder (object), balance |
52+
| Customer Rewarded | Triggered when a customer is rewarded with a main reward. | redemption (object), referral_tier (object), reward (object), voucher (object), holder (object), balance |
53+
| Customer Rewarded Loyalty Points | Triggered when a customer is rewarded with loyalty points. | earning_rule (object), loyalty_tier (object), order (object), voucher (object), holder (object), balance |
5854

5955
### Validation events
56+
| Event | Description | Fields |
57+
|-------------------------------|------------------------------------------------------------------------------------|---------------------|
58+
| Customer Validation Succeeded | Triggered when a customer's validation is completed (customer entered valid code). | validation (object) |
59+
| Customer Validation Failed | Triggered when a customer's validation fails. | validation (object) |
6060

61-
| Event | Description |
62-
| -------------------- | ---------------------------------------------------------------------------------- |
63-
| Validation succeeded | Triggered when a customer's validation is completed (customer entered valid code). |
64-
| Validation failed | Triggered when a customer's validation fails. |
65-
66-
Publication events:
61+
### Publication events
62+
| Event | Description | Fields |
63+
|--------------------------------|--------------------------------------------------------------------------------------|----------------------|
64+
| Customer Publication Succeeded | Triggered when a publication (assigning a code to particular customer) is completed. | publication (object) |
65+
| Customer Publication Failed | Triggered when a publication (assigning a code to particular customer) fails. | publication (object) |
6766

6867

6968
## Event Properties
7069

71-
The table below lists the properties included in the events listed above.
70+
The table below shows common properties for each event.
71+
72+
| Event | Description |
73+
|-----------|-------------------------------------------------------------------------------------------------------------------|
74+
| userId | The id used to identify the customer in Voucherify. It's the same id as the source_id in Voucherify. |
75+
| email | Customer's email. |
76+
| event | Event name. |
77+
| timestamp | Date and time the event occurred |
78+
| customer | Customer object. Contains fields such as: id, email, source_id and name. |
79+
| campaign | Campaign object. Contains fields such as: id, name, created_at, type, active. It may include voucher information. |
7280

73-
| Event | Description |
74-
| --------------- | ---------------------------------------------------- |
75-
| voucherifyEvent | The entire event object that occurred in Voucherify. |
7681
## Adding Destinations
7782

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

0 commit comments

Comments
 (0)