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/destinations/catalog/marketo-v2/index.md
+9-9Lines changed: 9 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -260,13 +260,13 @@ There are a few necessary steps that have to be taken to migrate from Segment's
260
260
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.
261
261
262
262
## Segment Sources Cannot Have Multiple Instances of Marketo V2 Destination
263
-
Multiple instances of Marketo V2 are not allowed for any source in Segment, in either Device-Mode or Cloud-Mode. If you need a single source's data sent to multiple Marketo V2 workspaces, then follow the steps listed below on configuring a [Repeater destination]([url](https://segment.com/docs/connections/destinations/catalog/repeater/)) to route your source's data through the Repeater destination into a new source and new Marketo V2 destination instance.
264
-
**Steps to Create a Repeater Destination, New Source, and second Marketo V2 destination**
265
-
1. Create and Connect a new Repeater destination to your source : [link to Repeater destination in catalog]([url](https://app.segment.com/goto-my-workspace/destinations/catalog/repeater)) and select the intended source.
266
-
2. Click Add destination, name the destination, and select Fill in settings manually.
267
-
3. On the Repeater destination's Settings page, under Connection Settings is a setting called Write Keys. This is where your second source's writeKey will go, from Step 4.
268
-
4. Create a new source (any type of source). Once created, navigate to its Settings tab / API Keys / and copy the value under Write Key.
269
-
5. Navigate back to your Repeater destination and paste in the source's writeKey into that Write Key setting.
263
+
Segment doesn't support multiple instances of Marketo V2 for any source in Segment (for both Device-Mode and Cloud-Mode). If you need a single source's data sent to multiple Marketo V2 workspaces, follow the steps listed below on configuring a [Repeater destination](/docs/connections/destinations/catalog/repeater/) to route your source's data through the Repeater destination into a new source and new Marketo V2 destination instance.
264
+
To create a Repeater destination, new source, and second Marketo V2 destination:
265
+
1. Create and connect a new [Repeater destination](https://app.segment.com/goto-my-workspace/destinations/catalog/repeater) to your source and select the intended source.
266
+
2. Click **Add destination**, name the destination, and select Fill in settings manually.
267
+
4. Create a new source, then navigate to **Settings > API Keys** and copy the **Write Key** value.
268
+
- From the Repeater destination's **Settings** page, you'll find **Write Keys** in the **Connection Settings**. This is where your second source's Write Key from step 4 will go.
269
+
5. Navigate back to your Repeater destination and paste in the source's `writeKey` into the Write Key setting.
270
270
6. Add a Marketo V2 destination to your new source with the desired configuration settings.
271
-
7. Enable all three : Repeater Destination, new Source, new Marketo V2 Destination.
272
-
8. You will begin seeing data transmitted from your originating source → to the Repeater Destination (Event Delivery) → to the new source (Debugger) → to Marketo V2 destination (Event Delivery)
271
+
7. Enable the Repeater destination, new source, new Marketo V2 destination.
272
+
8. You'll begin seeing data transmitted from your originating source to the Repeater Destination (Event Delivery), then to the new source (Debugger), and finally to the Marketo V2 destination (Event Delivery).
0 commit comments