Skip to content

Commit 14002f1

Browse files
authored
fix casing
1 parent 0f87a6a commit 14002f1

File tree

1 file changed

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

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -67,8 +67,8 @@ When you call [`Identify`](/docs/connections/spec/identify/) in Device-mode, Seg
6767

6868
There are additional steps you must take to send `.identify()` calls in Device-mode.
6969

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:
7272
![](images/form-info.png)
7373

7474
### Traits
@@ -109,7 +109,7 @@ analytics.identify('1234', {
109109
});
110110
```
111111

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.
113113

114114
![](images/c1X7nf6wDIX+.png)
115115

0 commit comments

Comments
 (0)