Skip to content

Commit a4c4001

Browse files
authored
Merge pull request #7336 from segmentio/spencerattick-patch-5
Custom Activity behavior
2 parents e8e033a + b5f84bb commit a4c4001

File tree

1 file changed

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

1 file changed

+3
-0
lines changed

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -162,6 +162,9 @@ Analytics.track(
162162
- **Primary Field**. When creating a Custom Activity in Marketo, you have to set a Primary Field. If you are unsure which field was set as the primary field, when you are looking at the list of fields for your Custom Activity in Marketo, there will be a red star next to your Primary Field.
163163
![A screenshot of the Fields tab inside of the Marketo Custom Activities page.](images/cZuvsHeaepX+.png)
164164

165+
> info ""
166+
> You can't map fields nested in objects as Marketo Custom Activity property names. You must flatten any objects you may need to access data from either before you send it to Segment, or while using an [Insert Function](/docs/connections/functions/insert-functions/).
167+
165168
## Page
166169

167170
When you call [`Page`](/docs/connections/spec/page/), Segment uses [Marketo's Munchkin.js `visitWebPage` method](http://developers.marketo.com/javascript-api/lead-tracking/api-reference/#munchkin_visitwebpage){:target="_blank"}. The URL is built from your `.page()` event and properties object into the form Marketo expects, so no need to worry about doing that yourself.

0 commit comments

Comments
 (0)