Skip to main content
If you have configured Munchkin and Forms 2.0, most Web Edge settings will feel familiar once you know where each piece landed. This article is for the person who owns the DNS records and the settings. Your web developer has a separate article on scripts, forms, and events: Coming from Marketo: Web Edge for developers.

​
Where each Marketo setting landed

​
What is different, not just renamed

One subdomain replaces three. Marketo split landing pages, Munchkin tracking, and branded email links across separate CNAME setups. One connected subdomain does all three jobs, with one pair of DNS records. You still set up an email domain, and it is separate. In Marketo, a branded link domain and your sending domain were both part of “the email setup.” In allGood, the Web Edge subdomain serves the links inside your emails, including the unsubscribe link. Your sending domain is a different subdomain with its own SPF, DKIM, and DMARC records. Plan on two subdomains: one for Web Edge and one for email. See Web Edge domain vs. email domain and Set up an email domain. The tracking key is not a secret, and you can replace it. A Munchkin ID never changes. A tracking key can be rotated with a grace period or revoked. See Set up Web Tracking. The origin list is stricter. Marketo’s whitelist is forgiving. Allowed origins match exactly: the scheme counts, there are no wildcards, and https://brand.com and https://www.brand.com are different origins. Budget an hour for this on your first rollout. Consent is read, not rendered. allGood has no cookie banner to configure. It reads the choice from the consent platform you already run.

​
Your part of a migration

Do these three steps before your developer starts. The developer steps follow in the developer article.
1

Connect a new subdomain

Do not reuse the subdomain that Munchkin, your Marketo landing pages, or your Marketo email links use until you are ready to cut over. See Connect a subdomain.
2

Port your domain whitelist

Turn every entry in Marketo’s form domain whitelist into an exact origin with its scheme. See Set your allowed origins.
3

Connect your consent platform

If Munchkin is already gated behind a consent platform such as OneTrust, point allGood at the same one. See Connect your consent platform.
You finish with an active subdomain, an origin list that mirrors your whitelist, and a consent platform connected. Send your developer the items in the hand-over list.