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
Copy file name to clipboardExpand all lines: src/connections/sources/catalog/cloud-apps/marketo/index.md
+15-18Lines changed: 15 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,19 +3,16 @@ title: Marketo Source
3
3
rewrite: true
4
4
source-type: object
5
5
strat: adobe
6
-
beta: true
7
6
id: VOXa199Bdm
8
7
---
9
8
<!-- Marketo is listed as an object source, but doesn't appear in our configapi source catalog, so leave the "source-type" set here -->
10
9
11
10
12
-
[Marketo](https://www.marketo.com/) is a leader in marketing automation. Use the Marketo source to load your campaigns, emails, leads and other collections into your data warehouse.
11
+
[Marketo](https://www.marketo.com/){:target="_blank"} is a leader in marketing automation. Use the Marketo source to load your campaigns, emails, leads, and other collections into your data warehouse.
13
12
14
-
This will allow you to write SQL to analyze your analyze your email marketing campaigns ROI, or join your email data to other data sources like web and mobile events, Salesforce, and Zendesk to tie nurture emails to re-activation rates in your app.
13
+
This will allow you to write SQL to analyze your email marketing campaigns ROI, or join your email data to other data sources like web and mobile events, Salesforce, and Zendesk to tie nurture emails to re-activation rates in your app.
15
14
16
-
{% include content/beta-note.md %}
17
-
18
-
## Getting Started
15
+
## Getting started
19
16
20
17
### Permissions
21
18
@@ -33,18 +30,18 @@ You will need Admin permissions to your Marketo account.
33
30
> In Marketo's settings, the Lead Activity Type IDs field is labeled as optional, but is required to see the `lead_activities` table. Segment recommends that you complete this field to see all available data.
34
31
35
32
36
-
### Configure your Marketo Source
33
+
### Configure your Marketo source
37
34
38
-
1. Open Marketo
39
-
2. Go to Admin > Munchkin to find your Munchkin Account ID
35
+
1. Open Marketo.
36
+
2. Go to **Admin > Munchkin** to find your Munchkin Account ID.
40
37
41
38
3. Go to Admin > LaunchPoint
42
39
a. If you don't already have a REST service setup, follow [these steps](http://developers.marketo.com/rest-api/custom-services/).
43
40
b. Then, copy the "Client ID" and "Client Secret" parameters.
44
41
45
42
c. Paste the "Client ID" and "Client Secret" into the Segment Marketo source settings.
46
43
47
-
Data should start flowing into your Warehouse in the next few hours.
44
+
Data should start flowing into your warehouse in the next few hours.
48
45
49
46
50
47
## Components
@@ -56,7 +53,7 @@ The Marketo source is built with a sync component, which means Segment makes req
56
53
57
54
The sync component uses an upsert API, so the data in your warehouse loaded using sync will reflect the latest state of the corresponding resource in Marketo. For example, if `first_name` goes from `Jess` to `Jessica` between syncs, on its next sync that field will be `Jessica`.
58
55
59
-
The source syncs and warehouse syncs are independent processes. Source runs pull your data into the Segment Hub, and warehouse runs flush that data to your warehouse. Sources will sync with Segment every 3 hours. Depending on your Warehouses plan, Segment pushes the Source data to your warehouse on the interval associated with your billing plan.
56
+
The source syncs and warehouse syncs are independent processes. Source runs pull your data into the Segment Hub, and warehouse runs flush that data to your warehouse. Sources will sync with Segment every three hours. Depending on your Warehouses plan, Segment pushes the Source data to your warehouse on the interval associated with your billing plan.
60
57
61
58
## Collections
62
59
@@ -78,7 +75,7 @@ Collections are the groupings of resources Segment pulls from your source. In yo
78
75
|`segments`| object | Segments inside a given segmentation. |
79
76
80
77
81
-
## Collection Properties
78
+
## Collection properties
82
79
83
80
### Leads
84
81
@@ -133,7 +130,7 @@ Collections are the groupings of resources Segment pulls from your source. In yo
Copy file name to clipboardExpand all lines: src/connections/sources/catalog/cloud-apps/salesforce-marketing-cloud/index.md
+20-33Lines changed: 20 additions & 33 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,33 +1,26 @@
1
1
---
2
2
title: Salesforce Marketing Cloud Source
3
-
beta: true
4
3
source-type: object
5
4
strat: salesforce
6
5
id: oQ5dZPW0Ii
7
6
---
8
7
<!-- SFMC is listed as an object source, but doesn't appear in our configapi source catalog, so leave the "source-type" set here-->
9
8
10
9
11
-
12
-
[Salesforce Marketing Cloud](https://www.salesforce.com/ca/products/marketing-cloud/overview/), formerly known as
13
-
ExactTarget, is a marketing automation suite with the ability to build complete customer journeys as well as creating,
14
-
targeting, tracking, and managing email and digital media campaigns.
10
+
[Salesforce Marketing Cloud](https://www.salesforce.com/ca/products/marketing-cloud/overview/){:target="_blank"}, formerly known as ExactTarget, is a marketing automation suite with the ability to build complete customer journeys as well as creating, targeting, tracking, and managing email and digital media campaigns.
15
11
16
12
With the Segment Salesforce Marketing Cloud Source, you can extract data from Marketing Cloud and send them
17
13
to a data warehouse such as Redshift or Big Query with ease, avoiding having to build your own expensive custom solutions.
18
14
19
15
If you are trying to set up Salesforce Marketing Cloud as a destination to receive data from Segment, check out
> *NOTE:* The Salesforce Marketing Cloud Source is currently in beta. This means that component names and functionality may change. For all feedback, [send us a note](https://segment.com/help/contact).
> **Good to know**: This page is about the Salesforce Marketing Cloud Segment source, which sends data _into_ Segment. There's also a page about the [Salesforce Marketing Cloud Segment destination](/docs/connections/destinations/catalog/salesforce-marketing-cloud/), which receives data from Segment!
19
+
> **Good to know**: This page is about the Salesforce Marketing Cloud Segment source, which sends data _into_ Segment. There's also a page about the [Salesforce Marketing Cloud Segment destination](/docs/connections/destinations/catalog/salesforce-marketing-cloud/), which receives data from Segment.
27
20
28
-
## Getting Started
21
+
## Getting started
29
22
30
-
### API Access
23
+
### API access
31
24
32
25
To access the Salesforce Marketing Cloud data on your behalf, Segment requires the client ID, client secret and
33
26
subdomain from your Salesforce Marketing Cloud integration. The integration must also have the following permissions:
@@ -46,19 +39,18 @@ client secret and subdomain set up for the destination. To enable the permission
46
39
2. Click your name in the top-right corner of the screen and select "Administration".
47
40
3. Navigate to the existing package with the the Segment destination API Integration.
48
41
4. Adjust the scope according to the permission table above.
49
-
5. Click "Save".
42
+
5. Click **Save**.
50
43
51
44
**If you do not have a Salesforce Marketing Cloud Segment Destination**, follow the steps below to acquire the client ID
52
45
and client secret:
53
46
54
47
1. Log in to your Salesforce Marketing Cloud account.
55
48
2. Click your name in the top-right corner of the screen and select "Administration".
56
49
3. Click the "Account" menu at the top-left corner of the page and select "Installed Packages".
57
-
4. If you want to use an existing package, click on that one or click "New" to create a new one. We recommend giving it
58
-
a name like "Segment".
50
+
4. If you want to use an existing package, click on that one or click "New" to create a new one. Segment recommends giving it a name like "Segment".
59
51
5. Click "Add Component".
60
52
6. Select "API Integration" and click "Next".
61
-
7. Select Server-to-Server
53
+
7. Select Server-to-Server.
62
54
8. Enable the permissions as specified in the table above.
63
55
9. Click "Save".
64
56
@@ -67,7 +59,7 @@ You should now see a Summary page with a Components section. This section lists
67
59
### Set up your subdomain
68
60
Segment will use your unique Salesforce subdomain to make API calls to SFMC. Your subdomain is represented by a 28-character string starting with the letters "mc" in any of your base URIs. For example, in the base URI `mc563885gzs27c5t9-63k636ttgm.rest.marketingcloudapis.com`, the subdomain is `mc563885gzs27c5t9-63k636ttgm`.
69
61
70
-
### Enable the Salesforce Marketing Cloud Source
62
+
### Enable the Salesforce Marketing Cloud source
71
63
72
64
1. From your Segment workspace's `/Sources` page, click `Add Source`.
73
65
2. Under the Email Marketing category, choose Salesforce Marketing Cloud and click `Connect`.
@@ -81,34 +73,29 @@ Segment will use your unique Salesforce subdomain to make API calls to SFMC. You
81
73
82
74
### Sync
83
75
84
-
The Salesforce Marketing Cloud source is built with a sync component, which means we'll make requests to their API on
85
-
your behalf on a 3 hour interval to pull the latest data into Segment. In the initial sync, we'll grab all the
86
-
Salesforce objects (and their corresponding properties) according to the Collections Table below. The objects will be
87
-
written into a separate schema, corresponding to the source instance's schema name you designated upon creation.
88
-
For example, if you went with `sfmc_prod`, the `campaigns` collection will be accessible at `sfmc_prod.campaigns` in SQL.
76
+
The Salesforce Marketing Cloud source is built with a sync component, which means Segment makes requests to their API on your behalf on a three-hour interval to pull the latest data into Segment. In the initial sync, Segment grabs all the Salesforce objects (and their corresponding properties) according to the Collections Table below.
77
+
78
+
The objects will be written into a separate schema, corresponding to the source instance's schema name you designated upon creation. For example, if you went with `sfmc_prod`, the `campaigns` collection will be accessible at `sfmc_prod.campaigns` in SQL.
89
79
90
80
Each sync will only sync the data that has been modified since the previous sync.
91
81
92
82
The source syncs and warehouse syncs are independent processes. Source runs pull your data into the Segment Hub,
93
-
and warehouse runs flush that data to your warehouse. Sources will sync with Segment every 3 hours. Depending on your
94
-
Warehouses plan, we will push the Source data to your warehouse on the interval associated with your billing plan.
83
+
and warehouse runs flush that data to your warehouse. Sources will sync with Segment every three hours. Depending on your Warehouses plan, Segment will push the source data to your warehouse on the interval associated with your billing plan.
95
84
96
85
## Collections
97
86
98
-
Collections are the groupings of resources we pull from your source. In your warehouse, each collection gets its own table.
87
+
Collections are the groupings of resources Segment pulls from your source. In your warehouse, each collection gets its own table.
| campaigns | Object | A campaign in your account. Corresponds to [Campaigns](https://developer.salesforce.com/docs/atlas.en-us.noversion.mc-apis.meta/mc-apis/getCampaignCollection.htm)|
104
-
| campaign_assets | Object | The assets associated with each campaign. Corresponds to [campaign_assets](https://developer.salesforce.com/docs/atlas.en-us.noversion.mc-apis.meta/mc-apis/getCampaignAssetCollection.htm)|
105
-
| lists | Object | A mailing list. Corresponds to [Lists](https://developer.salesforce.com/docs/atlas.en-us.noversion.mc-apis.meta/mc-apis/list.htm)|
| campaigns | Object | A campaign in your account. Corresponds to [Campaigns](https://developer.salesforce.com/docs/atlas.en-us.noversion.mc-apis.meta/mc-apis/getCampaignCollection.htm){:target="_blank"}|
93
+
| campaign_assets | Object | The assets associated with each campaign. Corresponds to [campaign_assets](https://developer.salesforce.com/docs/atlas.en-us.noversion.mc-apis.meta/mc-apis/getCampaignAssetCollection.htm){:target="_blank"}|
94
+
| lists | Object | A mailing list. Corresponds to [Lists](https://developer.salesforce.com/docs/atlas.en-us.noversion.mc-apis.meta/mc-apis/list.htm){:target="_blank"}|
106
95
107
96
## Collection Properties
108
97
109
-
Segment performs a one-to-one mapping of all publicly available fields from Salesforce Marketing Cloud. Below are tables
110
-
outlining the properties included in the collections listed above. To see the full description of each property,
111
-
refer to the Salesforce Marketing Cloud documentation linked in each [collection](#collections) above.
98
+
Segment performs a one-to-one mapping of all publicly available fields from Salesforce Marketing Cloud. The tables in this section outline the properties included in the collections listed above. To see the full description of each property,refer to the Salesforce Marketing Cloud documentation linked in each [collection](#collections) above.
0 commit comments