Skip to main content
This article is for the developer who has run Munchkin and Forms 2.0 and now has to do the same jobs here. DNS records, the allowed origins list, and consent settings belong to your admin, who has a separate article: Coming from Marketo: Web Edge for admins.

​
Concept map

​
Three things that are different, not renamed

​
1. allGood doesn’t render your form

Marketo’s model is that the vendor renders, styles and captures the form, and teams then either rebuild their design inside that renderer or spend their time overriding its markup. allGood assumes the page and the form are built in the tools you already use. What the platform owns is what a page can’t credibly do for itself: secure capture, abuse control, and defensible consent evidence. So there’s no embed code that draws a form, no form theme, and no CSS to override. You add one attribute to a form you already have. See Capture a form.

​
2. Tracking is identify and track, not just visits and clicks

Munchkin was designed when a page visit and a link click described most online behaviour. Anything else had to become a form submission or a REST call. allGood gives you two general-purpose calls, so anything a page can describe becomes an activity:
No activity type to define first, no fixed catalogue. See Identify and track.

​
3. Your page writes the consent signal

allGood has no banner to configure. Your page writes the visitor’s choice to a JavaScript global, and the tag holds events until it reads a yes. Form submissions are never gated on it. See What consent gates.

​
A migration sequence

Your admin does the first three steps: connect a new subdomain, port the domain whitelist, and connect the consent platform. See Your part of a migration. Then you do these.
1

Install the tag alongside Munchkin

They don’t conflict. Run both while you compare. See Install the tag.
2

Recreate one form

Build its field model in allGood, then publish it to register it. See Create a form.
3

Point one page's existing markup at it

Add data-ag-form to the markup you already have, keeping the Marketo form beside it while you compare.
4

Compare for a week

Check submission counts and field completeness, then remove the Marketo form from that page and repeat.
You finish with one page submitting to both systems and matching counts. Repeat per form until Marketo has none left.

​
What’s better, so you use it

  • Your markup stays yours. No renderer to fight.
  • A real response contract. Every submission comes back with exactly one machine-readable outcome, so your page can branch on it. See Reason codes.
  • Consent evidence you can defend. The statement version is stamped by allGood, not supplied by the page, so it can’t be forged from the browser.
  • Nothing is dropped on the way in. Every key you send is stored, including UTM values and your own hidden fields. Adding a field to a form needs no migration.
  • A rotatable, revocable key. Munchkin IDs are forever.
  • A real test surface. A hosted page on a genuinely separate domain, running the production script against your production settings.
  • Honest status. “Live at the edge” means a read-back confirmed it, not that a write was attempted.