Skip to content

Commit 2263190

Browse files
authored
More edits
1 parent cd494ea commit 2263190

File tree

1 file changed

+5
-3
lines changed
  • src/connections/destinations/catalog/marketo-v2

1 file changed

+5
-3
lines changed

src/connections/destinations/catalog/marketo-v2/index.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -260,13 +260,15 @@ There are a few necessary steps that have to be taken to migrate from Segment's
260260
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.
261261

262262
## Send a single source's data to multiple Marketo V2 workspaces
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.
263+
264+
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 instructions 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.
264265
To create a Repeater destination, new source, and second Marketo V2 destination:
266+
265267
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.
266268
2. Click **Add destination**, name the destination, and select Fill in settings manually.
267269
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+
- 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.
271+
5. Navigate back to your Repeater destination and paste in the source's `writeKey` into the write key setting.
270272
6. Add a Marketo V2 destination to your new source with the desired configuration settings.
271273
7. Enable the Repeater destination, new source, new Marketo V2 destination.
272274
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

Comments
 (0)