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
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -67,8 +67,8 @@ When you call [`Identify`](/docs/connections/spec/identify/) in Device-mode, Seg
67
67
68
68
There are additional steps you must take to send `.identify()` calls in Device-mode.
69
69
70
-
1. Create an empty form in Marketo. This form will always be hidden and can remain empty as long as the traits you need downstream are mapped in the **Marketo Custom Fields** setting.
71
-
2. Input the associated **Marketo Form ID** and **Marketo Form URL** in your Marketo V2 destination settings. This information can be found in Form Actions > Embed Code in the Marketo Design Studio:
70
+
1. Create an empty form in Marketo. This form will always be hidden and can remain empty as long as the traits you need downstream are mapped in the **Marketo Custom Fields**Destination setting.
71
+
2. Input the associated **Marketo Form ID** and **Marketo Form URL** in your Marketo V2 Destination settings. This information can be found in Form Actions > Embed Code in the Marketo Design Studio:
72
72

73
73
74
74
### Traits
@@ -109,7 +109,7 @@ analytics.identify('1234', {
109
109
});
110
110
```
111
111
112
-
If you'd like any other traits from your `.identify()` call to update a field in Marketo, you must create custom fields in Marketo and map them in the **Marketo Custom Fields**destination setting.
112
+
If you'd like any other traits from your `.identify()` call to update a field in Marketo, you must create custom fields in Marketo and map them in the **Marketo Custom Fields**Destination setting.
0 commit comments