Skip to content
Start for free

Marketo Munchkin

Track known and anonymous leads with Marketo Munchkin once visitors allow marketing. Until then, Munchkin sets no cookie and stores nothing.

Inth keeps the consent record of each choice, with the visitor’s country and the policy that applied.

Start for free
pnpm add @c15t/integrations
Marketo MunchkinWaiting for consent
Before a choice

No loader request, window.Munchkin, _mkto_trk cookie or vendor storage appears.

Turn the switch on, then off, to see what loads.

Before you start

You need an Inth project that connects to your app and c15t in that app. You also need the Munchkin account ID from your Marketo installation snippet.

The account ID looks like AAA-BBB-CCC. If it is blank, c15t logs an error and never loads Munchkin.

Open the quickstart for your framework

How consent works with Munchkin

Before marketing has permission, the c15t marketoMunchkin helper requests nothing. It creates no Munchkin global, cookie or browser storage.

After consent, c15t downloads the SDK and calls Munchkin.init once with your account ID and initOptions. Changes to other categories do not start Munchkin again.

If the visitor withdraws while the SDK downloads, the helper skips the init call.

Munchkin has no API to stop tracking. So on withdrawal, c15t removes the loader and reloads the page. While consent stays off, the next page does not load Munchkin.

Installation

Munchkin has one load mode in c15t. The helper waits for marketing permission.

Wait for permission. No request goes to Marketo until the visitor accepts marketing. On withdrawal, c15t reloads the page.

marketoMunchkin({ munchkinId })

An opt-out policy or no policy gives optional categories permission before a choice. Then Munchkin loads on the first page. This guide uses an opt-in policy.

Setup steps

  1. Install the integration package

    Add the helpers next to c15t. An import alone does not start Munchkin.

    pnpm add @c15t/integrations

  2. Add your Munchkin account ID

    The helper trims whitespace from the ID. Pass Munchkin settings such as anonymizeIP or cookieLifeDays through initOptions.

    src/consent-scripts.ts
    import { marketoMunchkin } from '@c15t/integrations/marketo';

export const scripts = [marketoMunchkin({ munchkinId: 'AAA-BBB-CCC' })];

    cookieAnon: false stops cookies for new anonymous visitors, but it is not a consent switch. Visitors who already have a cookie are still tracked.

  3. Register it with your existing setup

    Add scripts to the c15t configuration that you have now. Keep your Inth endpoint, mode, policy, styles and consent UI.

    Add scripts to c15t.config.ts, next to next.config.ts. Keep the rest of your config, such as mode, in the same call. App Router, Pages Router and static export read the same file.

    c15t.config.ts
    import { defineConsentConfig } from 'c15t/next';
import { scripts } from './src/consent-scripts';

export default defineConsentConfig({ scripts });

    Pass scripts to the ConsentRoot in your root route. Import helpers in the route module, not in a server function: script configurations carry callbacks.

    src/routes/__root.tsx
    import { scripts } from '../consent-scripts';

<ConsentRoot state={consent} scripts={scripts}>

    Add scripts to the options of your ConsentProvider, next to mode. Keep the banner, dialog and preferences link inside the provider.

    src/consent.tsx
    import { scripts } from './consent-scripts';

<ConsentProvider options={{ mode, scripts }}>

    Register scripts under the c15t key in app.config.ts. Keep them out of nuxt.config.ts, which reaches the browser as JSON and drops the helper callbacks.

    app/app.config.ts
    import { scripts } from '../src/consent-scripts';

export default defineAppConfig({
  c15t: { scripts },
});

    Pass scripts to the c15tVue plugin call you have now. The plugin starts one script loader when the app mounts.

    src/main.ts
    import { c15tVue, manifest } from 'c15t/vue/vue-plugin';
import { scripts } from './consent-scripts';

app.use(c15tVue, {
  mode: manifest(),
  scripts,
});

    Add scripts to the client entrypoint, which the integration finds on its own. Keep helpers out of astro.config.mjs: its options are serialized into the page.

    src/c15t.client.ts
    import type { C15tClientOptionsExtension } from 'c15t/astro';
import { scripts } from './consent-scripts';

export default { scripts } satisfies C15tClientOptionsExtension;

    Pass scripts as a prop to the ConsentProvider you have now. The provider owns the loader and disposes it on unmount.

    src/App.svelte
    <script lang="ts">
  import { ConsentProvider, manifest } from 'c15t/svelte';
  import { scripts } from './consent-scripts';
</script>

<ConsentProvider mode={manifest()} {scripts}>
  <!-- Your app and consent UI -->
</ConsentProvider>

    Add scripts to the ConsentRoot in the root layout. Import helpers in the layout component, not in +layout.server.ts: a server load cannot send functions to the browser.

    src/routes/+layout.svelte
    <script lang="ts">
  import { ConsentRoot } from 'c15t/svelte';
  import { scripts } from '../consent-scripts';

  let { children, data } = $props();
</script>

<ConsentRoot state={data.consent} {scripts}>
  {@render children()}
</ConsentRoot>

    Paste the vendor’s snippet behind consent

    The helpers need a bundler. On a page with the c15t script tag, paste the vendor’s own snippet instead and keep it inert until visitors allow its category. Helper options, such as loadMode, do not apply.

    index.html
    <script type="text/plain" data-c15t-category="marketing">
  // The vendor's snippet, unchanged
</script>

    Pass scripts to init() from @c15t/browser, next to your mode. With createConsentRuntime, pass scripts to it instead.

    src/consent.ts
    import { init, manifest } from '@c15t/browser';
import { scripts } from './consent-scripts';

const consent = init({
  mode: manifest(),
  scripts,
});
All frameworks

Remove the Munchkin tag from your site, so that c15t controls when it loads. Keep reloadOnConsentRevoked on.

Verify your setup

Filter DevTools Network by munchkin.marketo.net. Then test the three states.

  • Before a choice

    No loader request, window.Munchkin, _mkto_trk cookie or vendor storage appears.

  • After you allow marketing

    The SDK loads and calls init with your account ID.

  • After you withdraw marketing

    c15t reloads the page. The new page makes no Munchkin request.

The reload does not remove _mkto_trk, which lasts two years by default. The helper does not set the Marketo opt out cookie, since that would block tracking after a later grant.

Open the full Munchkin guide