You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Customer.io](https://customer.io/) is an automated email tool. It lets you set up rules to automatically send emails to your users after they perform actions, making drip email campaigns really easy.
7
+
{% include content/source-region-unsupported.md %}
8
+
9
+
[Customer.io](https://customer.io/){:target="_blank”} is an automated email tool. It lets you set up rules to automatically send emails to your users after they perform actions, making drip email campaigns really easy.
8
10
9
11
Take your company's email analysis to the next level by **adding Customer.io as a Source to Segment.** Segment automatically collects email events like `Email Delivered` and `Email Opened`, forward them to your destinations, and load them into your data warehouse.
10
12
11
-
In your favorite BI or analytics tool, you'll be able to analyze your email campaigns in SQL or through drag-and-drop reports. And, you'll be able to join your Customer.io data with the event data you're already sending through Segment to analyze the down-funnel effects of your emails. [Learn more about how you can use Customer.io with Segment.](https://segment.com/sources/customerio/)
13
+
In your favorite BI or analytics tool, you'll be able to analyze your email campaigns in SQL or through drag-and-drop reports. And, you'll be able to join your Customer.io data with the event data you're already sending through Segment to analyze the down-funnel effects of your emails. [Learn more about how you can use Customer.io with Segment.](https://segment.com/sources/customerio/){:target="_blank”}
12
14
13
15
> success ""
14
-
> **Good to know**: This page is about the Customer.io Segment source, which sends data _into_ Segment. There's also a page about the [Customer.io Segment destination](/docs/connections/destinations/catalog/customer-io/), which receives data from Segment!
16
+
> **Good to know**: This page is about the Customer.io Segment source, which sends data _into_ Segment. There's also a page about the [Customer.io Segment destination](/docs/connections/destinations/catalog/customer-io/), which receives data from Segment.
15
17
16
18
## Getting Started
17
19
18
-
If you previously sent email events using the Customer.io destination during our beta (using a project write key), you do not need to create new Customer.io source. Your email data will continue to flow as normal.
20
+
If you previously sent email events using the Customer.io destination during the beta (using a project write key), you do not need to create new Customer.io source. Your email data will continue to flow as normal.
19
21
20
22
1. Go to **Connections > Sources** and click **Add Source** in the Segment app.
21
23
22
24
2. Search for **Customer.io** in the Sources Catalog and click **Add Source**.
23
25
24
-
3. Give the Source a name and add any labels to help you organize and filter your sources. You can give the source any name, but Segment recommends a name that reflects the source itself, as this name autopopulates the schema name. For example, the source name `Customer.io` creates the schema `customerio`.
26
+
3. Give the Source a name and add any labels to help you organize and filter your sources. You can give the source any name, but Segment recommends a name that reflects the source itself, as this name auto-populates the schema name. For example, the source name `Customer.io` creates the schema `customerio`.
25
27
26
28
4. The next page ("Overview") displays your **Segment write key for Customer.io.** Copy this write key.
27
29
@@ -33,57 +35,29 @@ If you previously sent email events using the Customer.io destination during our
33
35
34
36
7. In Segment, click **Add Destinations** in your Customer.io source to add destinations for your Customer.io data.
35
37
36
-
That's it! As you send emails, events will now be sent to your destinations and automatically loaded into any warehouses you have enabled.
38
+
As you send emails, events will now be sent to your destinations and automatically loaded into any warehouses you have enabled.
37
39
38
40
## Components
39
41
40
42
**Stream**
41
43
42
-
Customer.io uses our stream Source component to send Segment email events. 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.
44
+
Customer.io uses Segment's stream Source component to send Segment email events. 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.
43
45
44
46
The default behavior is for Customer.io to pass the `userId` associated with the email recipient as the `userId`. There are cases in which Customer.io does not have an associated `userId`, in which case the email address will be passed in as the `anonymousId`.
45
47
46
48
## Collections
47
49
48
-
Collections are the groupings of data we pull from your Source. In your warehouse, each collection gets its own table, as well as a `tracks` table that aggregates all the events into a single table.
50
+
Collections are the groupings of data Segment pulls from your Source. In your warehouse, each collection gets its own table, as well as a `tracks` table that aggregates all the events into a single table.
49
51
50
-
<table>
51
-
<tr>
52
-
<td>**Collection**</td>
53
-
<td>**Type**</td>
54
-
<td>**Description**</td>
55
-
</tr>
56
-
<tr>
57
-
<td>Email Delivered</td>
58
-
<td>Event</td>
59
-
<td>Message has been successfully delivered to the receiving server</td>
60
-
</tr>
61
-
<tr>
62
-
<td>Email Opened</td>
63
-
<td>Event</td>
64
-
<td>Recipient has opened the HTML message. You need to enable Open Tracking for getting this type of event</td>
65
-
</tr>
66
-
<tr>
67
-
<td>Email Link Clicked</td>
68
-
<td>Event</td>
69
-
<td>Recipient clicked on a link within the message. You need to enable Click Tracking for getting this type of event</td>
70
-
</tr>
71
-
<tr>
72
-
<td>Email Unsubscribed</td>
73
-
<td>Event</td>
74
-
<td>Recipient clicked on message's subscription management link</td>
75
-
</tr>
76
-
<tr>
77
-
<td>Email Bounced</td>
78
-
<td>Event</td>
79
-
<td>Receiving server could not or would not accept message</td>
| Email Delivered | Event | Message has been successfully delivered to the receiving server |
56
+
| Email Opened | Event | Recipient has opened the HTML message. You need to enable Open Tracking for this kind of event |
57
+
| Email Link Clicked | Event | Recipient clicked on a link within the message. You need to enable Click Tracking for this kind of event |
58
+
| Email Unsubscribed | Event | Recipient clicked on message's subscription management link |
59
+
| Email Bounced | Event | Receiving server could not or would not accept message |
60
+
| Email Marked as Spam | Event | Recipient marked message as spam |
87
61
88
62
<!-- Example: To query the Email Delivered table, you'd write a query like this:
89
63
@@ -101,4 +75,4 @@ from customerio.email_delivered
101
75
102
76
## Send data to Customer.io
103
77
104
-
The Customer.io Source works better when you also connect Customer.io as a destination. With the Customer.io **Destination**, you can use Segment to send Cusotmer.io user and event data from which you trigger email campaigns. Want to start sending website or mobile data **_TO_** Customer.io? Head on over to our[Customer.io destination docs](https://segment.com/docs/connections/destinations/catalog/customer.io/).
78
+
The Customer.io Source works better when you also connect Customer.io as a destination. With the Customer.io **Destination**, you can use Segment to send Cusotmer.io user and event data from which you trigger email campaigns. Want to start sending website or mobile data **_TO_** Customer.io? Head on over to the[Customer.io destination docs](/docs/connections/destinations/catalog/customer.io/).
0 commit comments