Skip to main content
Landing pages are generated in Creative → Landing Pages. Each page goes through the same lifecycle: generate, review, deploy, instrument, iterate.

​
Lifecycle at a glance

​
Before you begin

Have ready:
  • A clear campaign objective (lead capture, demo booking, free trial signup, etc.).
  • A primary CTA with one job (book a call, start trial, download X).
  • Offer details the page needs to communicate (price, what’s included, social proof).
  • A target audience description if it’s not already in Brand → Market Strategy.
If you’re capturing form submissions, decide which CRM lead list they should land in. If the list doesn’t exist yet, create it first.

​
Generate the page

1

Start in Agent Mode

Open Agent Mode and brief Emma. Include the objective, audience, offer, primary CTA, and any required sections (testimonials, FAQ, pricing, etc.).Example:“Generate a landing page for our Q2 founder webinar. Audience: B2B SaaS founders running marketing themselves. CTA: register for the webinar (one button, top and bottom). Sections: hero with headline + subhead, three bullet outcomes, host bio with photo placeholder, agenda, FAQ. Use our brand colors.”
2

Pick a template

Emma proposes a template from your available HTML templates (visible at Creative → Landing Pages → Templates). Accept the suggestion or pick a different one.
3

Review the draft

Emma generates the page and saves it as a draft in Creative → Landing Pages. Click into the page to preview it in your browser.
4

Iterate

Ask Emma for specific changes — tighten the headline, swap a section, change the color of the CTA, add a testimonial. Each iteration is saved with version history.For pixel-level edits, open the page in the Agent Mode artifact panel and switch from the Preview tab to the Code tab. Save commits your change to the page’s repo.

​
Deploy to a subdomain

1

Click Deploy

Find the page’s card in Creative → Landing Pages and click Deploy. Status moves to deploying.
2

AgentWeb assigns the subdomain

You are not asked to choose one. Deploy sends no subdomain at all, and after a successful build AgentWeb assigns an address off agentwebforms.com derived from the page name — a page named “Q2 Webinar” becomes q2-webinar.agentwebforms.com. If that address is already taken by another project, a short random suffix is added.The only place you can change the address is Site Config (top of Creative → Landing Pages) → Where Your Site Lives. There you can set the .agentwebforms.com prefix under Default Subdomain, or connect a custom domain with + Set Custom Domain. Both are site-wide: every page in the site shares that root address, so changing it changes the URL of every page at once.
3

Wait for the build

Deploys typically complete in under a minute. Status flips to deployed and a View Live Site link appears on the page’s card.
Re-deploys are incremental — clicking Deploy again after edits pushes the latest version to the same URL.

​
Capture leads

To pipe form submissions into your CRM:
  1. Find the page’s card in Creative → Landing Pages.
  2. Use the lead-list picker on the card to choose the CRM lead list submissions should land in.
There is no re-deploy step — AgentWeb pushes the capture wiring to the live site itself when you pick the list. If it cannot reach the site’s repo it tells you so (“Saved, but your live site was not updated”), and leads are not captured until that succeeds. Submissions appear in the chosen list with the form fields mapped to lead fields. Custom form fields land in CRM custom fields.

​
Install your Meta Pixel

If you connected a Meta ad account before generating the page, the Pixel and server-side conversion tracking are already on it — there’s nothing to install. Ask Emma to confirm rather than adding a second one, which would double-count every conversion. If the page was generated without them, paste your Pixel ID into the chat with Emma and ask her to add the tracking snippet: “Install Meta Pixel 123456789012345 on the webinar landing page.” Emma adds the Pixel snippet to the page’s <head>, gives you a preview URL to review, and publishes it once you confirm. The Pixel goes into the layout every page on the site shares, so it applies site-wide rather than to that page alone.
This adds the base Pixel only — page views, audiences and retargeting. It does not report conversions: a form fill won’t show up in Meta, because the conversion event and its server-side counterpart are wired separately. Ask your AgentWeb contact for the full setup, and see Analytics and tracking for what’s involved.
For the full ads-side setup (Business Account, Partner sharing, Pixel creation), see Integrations → Meta.

​
Add Google Tag Manager (or other tags)

For Google Tag Manager, GA4, LinkedIn Insight Tag, or any custom script, open Site Config at the top of Creative → Landing Pages and use Analytics & Tracking → Add GTM. It accepts a GTM container ID in the form GTM-XXXXX — not a full script tag — and it applies to the whole site, not to a single page. AgentWeb commits the change and the site redeploys itself. Add GA4, the LinkedIn Insight Tag, and anything else as tags inside that GTM container.

​
Performance and iteration

Once a page is live and running paid traffic to it, conversion data flows back into Performance → Campaign Performance. Iterate on the page based on what the data shows:
  • Low CTR from the ad to the page → ad creative / messaging mismatch, not a page problem.
  • Low time-on-page → headline and first section aren’t matching intent.
  • Form-start but no form-complete → form is too long or asking for the wrong fields.
  • High CTR but low form-fill → CTA, offer, or proof points aren’t credible enough.
Ask Emma to propose changes based on the metrics: “Look at the last 7 days of analytics on the webinar landing page. What three things would you change first?”

​
Custom code edits

For changes beyond what Emma will do conversationally — custom JS, third-party widgets, A/B test setups — open the page in the Agent Mode artifact panel and use the Code tab. All edits are committed to the page’s repo. There is no commit browser in the product, so you cannot roll back to an arbitrary earlier commit. The one rollback available to you is Revert last publish on the page’s card in Creative → Landing Pages. It undoes only the most recent publish, it works only once, and it is refused if anything newer has been published since.

​
Duplicate a page

There is no Duplicate button. Ask Emma: “Duplicate the webinar landing page and call it ‘Webinar — founder angle’.”
Duplicating does not copy the page. It re-runs a full generation from the original page’s original prompt plus your current brand guidelines, and it deploys the result live automatically. You do not get a draft to review first — the new page finishes as deployed or failed, and a deployed one is publicly reachable at its own address. Delete it from Creative → Landing Pages if you did not want a second live page.
Because it regenerates rather than copies, the duplicate will not match the original’s current code — hand edits and Emma iterations made since the original was generated are not carried over. If you don’t give Emma a new name, the page is saved under the original name followed by (copy). The original’s CRM lead list carries over; if it had none, your default list is used. Duplicating is refused with an error if no brand logo is saved in Brand Guidelines — landing pages are never generated with an invented or approximate logo. Upload your logo first, then duplicate.

​
Troubleshooting

A failed page shows its error message directly on its card in Creative → Landing Pages, and the same text appears in the warning-triangle tooltip next to the status badge. The most common cause is a template syntax error introduced during a manual edit. Click Retry on the card, or ask Emma for the build details: “Show me the deployment status and build errors for the webinar landing page.”
Confirm the page’s card in Creative → Landing Pages shows the correct lead list in its lead-list picker. If the mapping looks right, submit a test entry from the deployed page and check CRM → [list] within a minute.
Open the deployed page in Chrome with the Meta Pixel Helper extension installed. If the Pixel doesn’t appear, ask Emma to verify the installation: “Confirm the Meta Pixel is installed on this page and show me where it was added.”
Custom domains need DNS records configured at your domain registrar. Open Site Config → Where Your Site Lives, connect the domain, then click Show DNS records — it lists the exact records to add, with copy buttons: a CNAME for a subdomain (or an A record for an apex domain), a wildcard CNAME so page subdomains work without extra records, and any TXT verification records. Click Check Again once you’ve added them. DNS can take up to 48 hours to propagate.
Most templates are responsive by default. If a custom edit broke mobile, preview in mobile viewport (Chrome DevTools → device mode) and ask Emma to fix it: “The landing page is broken on mobile under 400px. Fix the hero section so the headline doesn’t overflow.”

​
Next steps

Last modified on August 13, 2026