Skip to content

Commit ad56216

Browse files
authored
Minor cleanup
1 parent 57ee034 commit ad56216

File tree

1 file changed

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

1 file changed

+11
-11
lines changed

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

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -4,30 +4,30 @@ id: GCeG0vmcDW
44
beta: true
55
---
66

7-
[SendGrid Marketing Campaigns](http://twilio.com/docs/sendgrid/ui/integrations/segment?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} enables you to automatically stream your email events directly into Segment to be used inside your warehouse or other downstream destinations.
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.
88

9-
This is an [Event Cloud Source](/docs/sources/#event-cloud-sources) which can not only export data into your Segment warehouse, but can also federate the exported data into your other enabled Segment Destinations.
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.
1010

1111
This source is maintained by SendGrid Marketing Campaigns. For any issues with the source, [contact their Support team](mailto:[email protected]).
1212

1313
## Getting started
1414
1. From your workspace's [Sources catalog page](https://app.segment.com/goto-my-workspace/sources/catalog){:target="_blank”} click **Add Source**.
1515
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 we recommend using something that reflects the source itself and distinguishes amongst your environments (eg. Sendgrid_Prod, Sendgrid_Staging, Sendgrid_Dev).
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`).
1818
4. Click **Add Source** to save your settings.
1919
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.
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.
2121

2222
## Stream
2323

24-
SendGrid Marketing Campaigns uses our 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.
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.
2525

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`.
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`.
2727

2828
## Events
2929

30-
The table below lists events that SendGrid Marketing Campaigns sends to Segment. These events appear as tables in your warehouse, and as regular events in other Destinations.
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.
3131

3232
| Event Name | Description |
3333
|-------------------------|-----------------------------------------------------------------------------------------------------------------------------|
@@ -49,7 +49,7 @@ The table below list the properties included in the events listed above. Some pr
4949
| Property Name | Description |
5050
|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------|
5151
| `event` | Email event type |
52-
| `anonymousId` | sha256 hash of the recipient email |
52+
| `anonymousId` | SHA256 hash of the recipient email |
5353
| `email_type` | "Singlesend" or "Automation" |
5454
| `template_id` | Email template ID |
5555
| `email_subject` | Subject line of the email, when available |
@@ -68,8 +68,8 @@ The table below list the properties included in the events listed above. Some pr
6868

6969
## Adding Destinations
7070

71-
Now that your Source is set up, you can connect it with Destinations.
71+
Now that your source is set up, you can connect it with destinations.
7272

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.
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.
7474

7575
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)