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
* Add three marketo items to Adobe menu, since it's part of the adobe fam
* well that didn't work
* combine headings.
* doc-138 react native deps
* add table for now
* cleanup capitalization
Co-authored-by: sanscontext <>
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/marketo-v2/index.md
+13-11Lines changed: 13 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,13 @@
1
1
---
2
2
title: Marketo V2 Destination
3
+
strat: adobe
3
4
---
4
5
5
6
## Getting Started
6
7
7
8
To start sending data to Marketo, there are two things you must do. **Both of these steps require that you to log in with the Admin Marketo Account.**
8
9
9
-
### 1. Enter your Marketo Credentials into your Destination settings.
10
+
### Enter your Marketo Credentials into your Destination settings
10
11
We'll need your Munchkin Account ID, Client Secret, and Client ID.
11
12
12
13
To get your Munchkin Account ID [login to your Marketo account](https://login.marketo.com/), click Admin in the top right corner, then click Munchkin on the left side bar.
@@ -15,12 +16,13 @@ To get your Munchkin Account ID [login to your Marketo account](https://login.ma
15
16
16
17
17
18
To get your Client Secret and Client ID, you must create a role that has full API access, an API only user, and then create a Service in Marketo.
19
+
18
20
To create a role with full API access:
19
21
20
-
1. Click Admin in the top right corner.
21
-
2. Click Users & Roles on the left side bar.
22
-
3. Click on the Roles tab.
23
-
4. Click New Role. Name your role and check the API Access box to assign the user full API access. Click Create.
22
+
1. Click **Admin** in the top right corner.
23
+
2. Click **Users & Roles** on the left side bar.
24
+
3. Click on the **Roles** tab.
25
+
4. Click **New Role**. Name your role and check the API Access box to assign the user full API access. Click Create.
24
26
25
27
26
28
@@ -44,7 +46,7 @@ Next, create a Service and get Client Secret and Client ID from that Service.
44
46
45
47
46
48
47
-
### **2. You must create a User ID and an Anonymous ID field in Marketo.**
49
+
### Create a User ID and an Anonymous ID field in Marketo
48
50
49
51
1. Click Admin in the top right corner.
50
52
2. Click Field Management on the left side bar.
@@ -79,7 +81,7 @@ Here is a sample Javascript `.identify()` call with the all the standard traits
79
81
analytics.identify('1234', {
80
82
firstName:'Robyn Rihanna',
81
83
lastName:'Fenty',
82
-
email:'rihanna@badgalriri.com',
84
+
email:'rihanna@example.com',
83
85
gender:'woman',
84
86
phone:'555-555-5555',
85
87
company:'Segment.com',
@@ -223,7 +225,7 @@ To upload a list to Marketo, when you are in Lead Database, click All Leads. The
223
225
224
226
### Migrating from Marketo to Marketo V2
225
227
226
-
There are a few necessary steps that have to be taken to Migrate from Marketo to Marketo V2.
228
+
There are a few necessary steps that have to be taken to migrate from Segment's legacy Marketo v1 destinations, to Marketo V2.
227
229
228
230
**Important: Make sure you disable Marketo once you are done getting set up with Marketo V2. If you leave both enabled, there will likely be duplicate data in your Marketo account.**
229
231
@@ -233,11 +235,11 @@ There are a few necessary steps that have to be taken to Migrate from Marketo to
233
235
3.`Track` calls must be mapped in your Destination settings. Our Marketo Destination sent `track` calls as a Munchkin Visit WebPage event in Marketo. In Marketo V2, we'll send your track calls to your Marketo Custom Activities. Detailed instructions [here](/docs/connections/destinations/catalog/marketo-v2/#track).
234
236
4. If there are any custom Lead fields that you'd like sent to Marketo in your `Identify` calls, you must add them in your Destination settings. Detailed instructions [here](/docs/connections/destinations/catalog/marketo-v2/#identify).
235
237
5. Update anything in Marketo that rely on the way V1 sends `.track()` events to be triggered by your custom activities. For example, our V1 Marketo destination sent track events as a "Visit Web Page" event with `/event/<your_event_name>`. So if you a workflow that is triggered by a "Visit Web Page" event where the web page contains `/event/<your_event_name>`, you'll have to swap out the "Visit Web Page" event trigger you have with your Custom Attribute Trigger. In the right side bar, click the "Custom" folder under "Triggers" and select the trigger that you set for your custom activity:
236
-
238
+
237
239
238
240
239
-
To figure out what the trigger name for that Custom Activity is, navigate to the admin section of Marketo > Marketo Custom Activities > Click on your activity from the side bar and you'll see the trigger name:
241
+
To figure out what the trigger name for that Custom Activity is, navigate to the admin section of Marketo > Marketo Custom Activities > Click on your activity from the side bar and you'll see the trigger name:
240
242
241
-
243
+
242
244
243
245
6. When enabling Marketo V2, because of the way Marketo's API works, there is potential to create duplicate leads, especially when the first enabling the destination. For ways to prevent this, check out the Preventing Duplicate Leads.
Copy file name to clipboardExpand all lines: src/connections/sources/catalog/libraries/mobile/react-native/index.md
+39-3Lines changed: 39 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,6 +48,10 @@ This is why even if you see events in the debugger, the Device-mode destination
48
48
> warning "React-Native version requirement"
49
49
> You must use React version 0.62 or later.
50
50
51
+
52
+
> info "Good to know - Device-mode destinations"
53
+
> Segment's React Native library serves as a wrapper around the two mobile libraries for iOs and Android. If you plan to [bundle device-mode destinations](#packaging-destinations-using-device-mode) you must add these dependencies.
54
+
51
55
### iOS configuration
52
56
53
57
You should use CocoaPods (**recommended**) to manage your installation and dependencies for iOS.
@@ -99,9 +103,9 @@ To install Analytics-React-native manually:
99
103
100
104
### Packaging Destinations using Device-mode
101
105
102
-
By default, Analytics-React-Native sends all of your data first to the Segment servers, which forward the data on to any tools you enabled from the Segment web app. It does not package any external destination SDKs by default. This is known as using "Cloud-mode", and it helps reduce the size of your project.
106
+
By default, Analytics-React-Native sends all of your data first to the Segment servers, which forward the data on to any tools you enabled from the Segment web app. It does not package any external destination SDKs by default. This is known as sending your data using "Cloud-mode", and it helps reduce the size of your project.
103
107
104
-
However, in order to function correctly some destinations require that you include code in your project that can be executed on the user's device. This is known as "device-mode". Other destinations offer a device-mode SDK, but still work (with reduced features) in cloud-mode.
108
+
However, some destinations require that you include code in your project that can be executed on the user's device so that these tools can function correctly. These destinations run code that sends data directly to the destination's API endpoints, as well as sending a copy to the Segment servers for archiving. This is known as sending data in "device-mode". Other destinations offer a device-mode SDK, but still work (with reduced features) in cloud-mode.
105
109
106
110
You can read [more about connection modes](/docs/connections/destinations/#connection-modes) in the Destination documentation.
107
111
@@ -110,7 +114,11 @@ You can read [more about connection modes](/docs/connections/destinations/#conne
110
114
111
115
To use a device-mode destination, you add the destination's SDK to the project. You can find information about these in the destination information pages in the Segment app. Any mobile destination with a Device-mode option includes information on how to bundle SDK.
112
116
113
-
These usually take the form of a dependency manager command, like the NPM example below.
117
+
Segment's React Native source library is a wrapper for the iOS and Android source libraries, and the React Native device mode SDKs you bundle are generated from the iOS and Android ones.
118
+
119
+
To use device-mode destinations with React Native, you must add the dependencies for iOS and Android. Once you set up the device mode dependencies for iOS and Android, you can then add the React Native dependency. See the [device mode documentation in the React Native readme](https://github.com/segmentio/analytics-react-native/#packaging-device-mode-destination-sdks) for more details.
120
+
121
+
To add the device-mode dependencies, install the pods for iOS builds, and add the dependencies to your `build.gradle` file in your Android project. You might also be able to use a dependency manager command, like the NPM example below.
0 commit comments