Skip to content

Commit 3ea35a7

Browse files
pwsegpwseg
authored
Merge pull request #6678 from segmentio/sendgrid/marketing-campaigns
Add SendGrid Marketing Campaigns Source docs
2 parents 363cdd9 + ad56216 commit 3ea35a7

File tree

1 file changed

+75
-0
lines changed
  • src/connections/sources/catalog/cloud-apps/sendgrid-marketing-campaigns

1 file changed

+75
-0
lines changed

‎src/connections/sources/catalog/cloud-apps/sendgrid-marketing-campaigns/index.md

Lines changed: 75 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,75 @@
1+
---
2+
title: SendGrid Marketing Campaigns Source
3+
id: GCeG0vmcDW
4+
beta: true
5+
---
6+
7+
[SendGrid Marketing Campaigns](http://twilio.com/docs/sendgrid/ui/integrations/segment?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} lets you automatically stream your email events directly into Segment for use inside your warehouse or other downstream destinations.
8+
9+
This is an [Event Cloud Source](/docs/sources/#event-cloud-sources) that can not only export data into your Segment warehouse but also federate the exported data into your other enabled Segment destinations.
10+
11+
This source is maintained by SendGrid Marketing Campaigns. For any issues with the source, [contact their Support team](mailto:[email protected]).
12+
13+
## Getting started
14+
1. From your workspace's [Sources catalog page](https://app.segment.com/goto-my-workspace/sources/catalog){:target="_blank”} click **Add Source**.
15+
2. Search for "SendGrid Marketing Campaigns" in the Sources Catalog, select SendGrid Marketing Campaigns, and click **Add Source**.
16+
3. On the next screen, give the source a name configure any other settings.
17+
- The name is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. The name can be anything, but Segment recommends using something that reflects the source itself and distinguishes amongst your environments (for example, `Sendgrid_Prod`, `Sendgrid_Staging`, `Sendgrid_Dev`).
18+
4. Click **Add Source** to save your settings.
19+
5. Copy the Write key from the Segment UI.
20+
6. Log in to your SendGrid Marketing Campaigns account - navigate to **Integrations > Segment -> Connect** and paste the key. Select the matching region and any email events you want to receive.
21+
22+
## Stream
23+
24+
SendGrid Marketing Campaigns uses Segment's 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.
25+
26+
SendGrid Marketing Campaigns passes a SHA256 hash of the recipient's email address as `anonymousId`. The raw email address is passed in `context.traits.email`.
27+
28+
## Events
29+
30+
The following table lists events that SendGrid Marketing Campaigns sends to Segment. These events appear as tables in your warehouse, and as regular events in other Destinations.
31+
32+
| Event Name | Description |
33+
|-------------------------|-----------------------------------------------------------------------------------------------------------------------------|
34+
| Email Processed | Email was sent successfully |
35+
| Email Delivered | Email delivered successfully |
36+
| Email Opened | Recipient opened the email |
37+
| Email Machine Opened | Email was [opened anonymously](https://www.twilio.com/docs/sendgrid/for-developers/tracking-events/understanding-apple-mail-privacy-protection-and-open-events){:target="_blank”} |
38+
| Email Link Clicked | Recipient clicked the [tracking link](https://www.twilio.com/docs/sendgrid/ui/account-and-settings/tracking#click-tracking){:target="_blank”} |
39+
| Email Dropped | Email was [dropped by Sendgrid](https://www.twilio.com/docs/sendgrid/glossary/drops){:target="_blank”} |
40+
| Email Bounced | Email servers [rejected the email](https://www.twilio.com/docs/sendgrid/ui/sending-email/bounces){:target="_blank”} |
41+
| Unsubscribed | Recipient [unsubscribed globally](https://www.twilio.com/docs/sendgrid/ui/sending-email/global-unsubscribes){:target="_blank”} |
42+
| Unsubscribed From Group | Recipient [unsubscribed from a group](https://www.twilio.com/docs/sendgrid/ui/sending-email/group-unsubscribes){:target="_blank”} |
43+
| Resubscribed To Group | Recipient resubscribed to a group |
44+
| Email Marked as Spam | Recipient [reported the email as spam](https://www.twilio.com/docs/sendgrid/ui/analytics-and-reporting/spam-reports){:target="_blank”} |
45+
46+
## Event Properties
47+
The table below list the properties included in the events listed above. Some properties are only available for Single Sends or Automations.
48+
49+
| Property Name | Description |
50+
|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------|
51+
| `event` | Email event type |
52+
| `anonymousId` | SHA256 hash of the recipient email |
53+
| `email_type` | "Singlesend" or "Automation" |
54+
| `template_id` | Email template ID |
55+
| `email_subject` | Subject line of the email, when available |
56+
| `test_phase` | `true` if the Single Send is an [A/B Test](https://www.twilio.com/docs/sendgrid/ui/sending-email/a-b-testing){:target="_blank”} in the test phase |
57+
| `unsubscribe_group_id` | ID of the unsubscribe group, when available |
58+
| `link_url` | URL of the link clicked |
59+
| `categories` | [Categories](https://www.twilio.com/docs/sendgrid/for-developers/sending-email/categories){:target="_blank”} associated to the email |
60+
| `campaign_name` | Name of the Single Send |
61+
| `campaign_id` | ID of the Single Send |
62+
| `automation_name` | Name of the Automation |
63+
| `automation_id` | ID of the Automation |
64+
| `automation_step_id` | ID of the Automation step |
65+
| `context.traits.email` | The recipient's raw (unhashed) email address |
66+
| `context.traits.ip` | The opening computer's public IP address |
67+
| `context.traits.user_agent` | The opening browser's user agent |
68+
69+
## Adding Destinations
70+
71+
Now that your source is set up, you can connect it with destinations.
72+
73+
Log into your downstream tools and check to see that your events appear as expected and that they contain all of the properties you expect. If your events and properties don’t appear, check the [Event Delivery](/docs/connections/event-delivery/) tool and refer to the Destination docs for each tool for troubleshooting.
74+
75+
If there are any issues with how the events are arriving to Segment, [contact the SendGrid Marketing Campaigns support team](mailto:[email protected]).

0 commit comments

Comments
 (0)