Web Edge setup checklist

Your account

#	Check	Done when
1	A subdomain is registered. See Connect a subdomain.	The row exists on Web Edge Sessions.
2	The routing record resolves.	A green tick on that row in the DNS drawer.
3	The certificate record resolves.	A green tick on the delegation record, or on every TXT record.
4	The subdomain is active.	A green active chip, with three of four steps done.
5	Sync has run since the subdomain went active. See Bot protection.	The fourth step, Bot protection ready, is done.
6	One subdomain is the default.	A default badge on a row.
7	Every website that will send data is listed. See Allowed origins.	Each origin is listed exactly, with its scheme.
8	The consent signal matches what your platform writes. See Consent provider.	The path is correct for your site.
9	A consent text version exists, if you need consent evidence.	A row in the versions table.
10	A tracking key is issued. See Web Tracking.	A key is shown, not Issue key.
11	Send events to allGood is on.	The switch is on.
12	Form processing defaults are reviewed. See Form processing.	Usually nothing changed.
13	Every status chip reads Live at the edge. See Saved vs live.	Green, not amber.

Each form

#	Check	Done when
14	The form exists and declares its fields.	The fields show on the form’s Settings tab.
15	The form is published.	It reads published on the form’s Overview.
16	The form is registered.	It reads “Accepting submissions: Registered”.
17	If it requires a bot check, the widget covers the hostname it sits on.	A green bot check covered chip on that origin.

Check 16 is the one people forget. An unregistered form refuses every submission, and the page shows the visitor a generic message instead of the reason.

Before the real website

#	Check	Where
18	Open the hosted test page in tracking mode and confirm events are accepted.	Test your setup
19	Open it in form mode for one real form and submit it.	The form’s Test tab
20	Deny consent, then grant it, and watch events hold and then send.	The test page’s consent simulator

If a check fails, start with the Web Edge FAQ. Your developer can use Troubleshooting to read the browser.

What to hand over

Whoever installs the tag needs four things:

The connected subdomain, for example mk.yourbrand.com.

The tracking key, which begins agsk_.

The short ID of each form they will wire up. It must be registered, not just created.

The name of the JavaScript value your consent platform writes to.

Marketing Kernel

Platform

Enterprise

Settings

Web Edge setup checklist

Your account

Each form

Before the real website

What to hand over

​Your account

​Each form

​Before the real website

​What to hand over

​Related articles

Your account

Each form

Before the real website

What to hand over

Related articles