Adobe Marketo Engage
How to configure Adobe Marketo Engage at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Support marketing analytics, Receive personalised marketing offers
Overview
This guide explains how to implement different privacy configurations for Marketo Engage (Munchkin tracking) and how to reflect them in the Consenter Manager.
- Configure the third-party service.
- Map the selected configuration in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.
At a glance
Scope. The Munchkin JavaScript tracking code and Marketo Forms 2.0. Adobe Inc. is a US company.
What the service does in this scope. Munchkin sets the _mkto_trk cookie, specific to each second-level domain, with a default lifespan of 2 years (730 days). On a visitor's first visit, an anonymous lead record is created whose primary key is the Munchkin cookie. Munchkin.init accepts configuration settings: cookieAnon controls whether a cookie is created for all leads upon visiting, and cookieLifeDays sets the expiry of newly created cookies. Visitors can opt out with marketo_opt_out=true, which sets mkto_opt_out. Forms 2.0 can be embedded without Munchkin, and thus without a new cookie.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Lower risk | Forms 2.0 only, no Munchkin; form data processed on submission. |
| Configuration B — Medium risk | Munchkin after consent; cookieAnon: false; 180-day cookie. |
| Configuration C — Higher risk (default configuration) | Munchkin after consent; anonymous and known leads tracked; 2-year cookie; email link identification. |
Configuration without prior consent (A). Without Munchkin no tracking cookie is set; form data is processed on the legal basis of the form's purpose (Art. 6 GDPR). Whether the Forms library itself accesses device storage should be verified in the browser.
Step 1 — Configure Marketo Engage
| # | Configuration area | Where to configure it | Configuration A — Lower risk | Configuration B — Medium risk | Configuration C — Higher risk (default configuration) |
|---|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | — (form only) | Support marketing analytics | Support marketing analytics; Receive personalised marketing offers |
| 2 | Munchkin | Website code | Not loaded | Munchkin.init after consent | Munchkin.init after consent |
| 3 | cookieAnon | Munchkin.init config | — | false | true (default) |
| 4 | cookieLifeDays | Munchkin.init config | — | 180 | 730 (default) |
| 5 | Email link tracking (mkt_tok) | Email settings | — | Off | On |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Adobe is a US enterprise subject to the US CLOUD Act; list the United States in all configurations with an entry.
| Consenter Manager field | Configuration A — Lower risk | Configuration B — Medium risk | Configuration C — Higher risk (default configuration) |
|---|---|---|---|
| Entry needed | Optional (form processing only) | Yes | Yes |
| Processing purposes | — | Support marketing analytics | Support marketing analytics, Receive personalised marketing offers |
| Tracking method | No tracking | First party tracking (cross-session) | First party tracking (cross-session) |
| Identifier | Direct identifier (on submission) | Device identifiers, Direct identifier | Device identifiers, Direct identifier |
| Data categories | User-provided data, direct identifier | Browsing and interaction data, Device identifiers, IP address, User-provided data, direct identifier | As B, plus Users' profiles |
| Legal role of data recipient | Processor | Processor | Processor |
| Personalisation model | No personalisation | Group based (behaviour) | Profile based |
| Maximum storage duration | Per lead retention | 180 days (cookie) | 2 years (cookie) |
| Processing location | Contract region; United States | Contract region; United States | Contract region; United States |
How is this guide?
Shape Consenter Together
Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.
Need Help?
Last updated on