Adobe Marketo Engage

Overview

Adobe Marketo Engage is a B2B marketing automation platform widely used on corporate websites to track prospect behavior, score leads, and trigger nurturing campaigns. Its presence on a site typically indicates the organization is capturing visitor activity to feed into sales and marketing workflows. The platform's primary client-side component is the Munchkin JavaScript tracker, which loads on every page to log visitor interactions.

What This Script Does

Marketo Engage deploys the munchkin.js tracker, which loads asynchronously on each page of the website. The script monitors page views, link clicks, form submissions, and time-on-page metrics, associating all activity with a visitor record.

Key cookies set:

• _mkto_trk — the primary Munchkin tracking cookie, a first-party cookie with a 2-year expiry. Contains a unique visitor ID that ties anonymous browsing activity to a lead record once the visitor identifies themselves (e.g., by submitting a form). This cookie persists across sessions and enables Marketo to build a complete activity history for each prospect.
• _mkto_referrer — stores the original referrer URL for attribution purposes. Session-scoped.
• BIGipServer* — load balancer cookies for Marketo's infrastructure. Session-scoped.

The Munchkin script contacts Marketo's tracking endpoints (typically *.mktoresp.com or *.marketo.net) to transmit visitor events in near-real-time. Data collected includes: page URLs visited, referrer information, UTM parameters, form field values (when Marketo forms are used), IP address, browser metadata, and timestamps.

When a visitor submits a form or clicks a tracked email link, the anonymous Munchkin cookie ID is merged with the known lead record in Marketo's database. From that point forward, all historical and future browsing activity is attributed to the identified contact. This data feeds into lead scoring models, triggering automated email sequences, sales alerts, and CRM sync operations with platforms like Salesforce.

Marketo Forms 2.0 (forms2.js) may also load on pages with embedded forms, adding form-specific tracking and validation scripts.

Consent & Compliance

Adobe Marketo Engage spans both marketing and analytics categories. It collects analytics-grade behavioral data (page views, click paths), but its primary purpose is marketing automation — lead scoring, email nurturing, and sales pipeline acceleration.

Under the GDPR, Marketo processes personal data including pseudonymous visitor IDs, IP addresses, and — once a form is submitted — directly identifiable information linked to the complete browsing history. The merging of anonymous tracking data with identified contact records is a significant data processing operation requiring explicit consent.

The ePrivacy Directive requires consent for the _mkto_trk cookie. Its 2-year expiry and use for marketing automation purposes (lead scoring, nurturing campaigns) place it firmly outside the "strictly necessary" exemption.

Under CCPA/CPRA, Marketo collects personal information and uses it for B2B marketing purposes. The cross-session behavioral tracking and lead identification constitute processing of personal information. If Marketo data syncs to a CRM and is used to target individuals with marketing communications, this may implicate the CPRA's profiling provisions.

Should You Block This Without Consent?

Yes. Marketo Engage's Munchkin tracker sets a persistent 2-year identification cookie, collects detailed behavioral data, and feeds it into marketing automation workflows. It is not essential for website functionality and requires consent before loading under EU privacy regulations.