Skip to main content
No. You describe the page to Mary, and she builds it. If you want to change the code yourself, use Edit Source. See Editing a landing page’s code.
Yes. Scripts you add to a page run as written. Keep in mind that allGood’s consent settings cover allGood’s own tracking, not tags you paste in. If your privacy policy needs those tags to wait for consent, set that up in the tag itself or in your consent platform.
Yes. A page allGood hosts is tracked by the allGood tag on the page, the same tag your website uses. With your consent settings on, the tag holds the visit until the visitor agrees, and allGood’s visitor cookie isn’t set before then. If they decline, the visit isn’t recorded. See Connect your consent platform.Mary puts the tag on every page she builds. If a page doesn’t load it, publishing warns you, and visits to that page aren’t tracked at all.One exception: a page that shows different versions sets a cookie that remembers which version the visitor saw. It holds only that, not who they are, and it ends when the browser closes.A form submission is never held back for consent, on any page. What the form keeps is the consent statement the visitor saw. See What protects a form.
Yes. A form is its own asset, and any number of pages can point at it. Editing the form changes it on every page that uses it. See Finding where a form is used.
Yes. Copy can live in its own document that both a page and an email use, so a campaign says one thing in both places. See Copy and variants.
A page is built once, when you publish it, before anyone visits. At that point there’s no visitor, so a name would be empty for everyone. To use someone’s name, put it in an email, or collect it with a form.
No. The search engine setting applies to your whole site. See Landing page settings.
No. A page goes live when you publish it.
Yes. Publish two versions and use a router to split visitors. See Showing different versions of a page.
The page is kept. Publish it again to put it back. See Publishing a landing page.