Add lead forms to a Seedly Sites page by embedding your CRM's form, with automatic UTM capture and a built-in thank-you page.
Loading the guide...
Did this answer your question?
Help us make the guides more useful.
0 helpful · 0 not helpful
Add lead forms to a Seedly Sites page by embedding your CRM's form, with automatic UTM capture and a built-in thank-you page.
Loading the guide...
Help us make the guides more useful.
0 helpful · 0 not helpful
Seedly Sites does not include a native form builder. That is a deliberate choice: your leads should land in your CRM, not in a website database you then have to sync. The workflow is to embed the form your CRM already provides, and the platform makes that embed first-class - campaign attribution flows through automatically, and every site ships a confirmation page.
Any provider that gives you an embed code works: GoHighLevel / LeadConnector, HubSpot, Typeform, JotForm, your own CRM's forms, or anything else that hands you an iframe or script snippet.
The embed block renders server-side in the published output, so iframes load and embed scripts execute on the live site. See Local Business Blocks for the block itself.
A few embed tips:
title attribute (accessibility) and loading="lazy" if the form sits below the fold.Each Location can carry its own Contact form embed and Careers form embed, set on the Location's edit page by the agency operator. Paste the form's full link, including https://, or its complete iframe code. Then put {{location.contactForm}} (or {{location.careersForm}}) in an HTML / Embed Code block, and every location that page is bound to shows its own form. The contact pages in the template packs already carry the contact-form token, and a location left empty shows no form. See Merge Tokens.
When UTM persistence is on in the site's Settings, the published site remembers the campaign a visitor arrived with for the rest of the visit. To pass it to your CRM, also turn on CRM embed attribution, as below, so a submission from a deep page still tells your CRM which ad or post brought the lead in.
How it behaves:
utm_source, utm_medium, utm_campaign, and click IDs like gclid or fbclid) is stored for the visit and persists as the visitor navigates between pages./admin, open the site's Site Settings, tick Enable Crm Embed Attribution, and list the hostnames in Crm Embed Hosts), the stored campaign parameters are appended to the address of form embeds whose hostnames you list, so providers that read UTMs from their form URL receive them. Nothing fills hidden form fields, and embeds you have not listed receive nothing.Turn on UTM persistence in Settings (and CRM embed attribution in /admin, if you use it), then redeploy the site so the script ships (Deploying).
Every published site includes a built-in /thank-you/ confirmation page, styled with the site's chrome. Point your form's post-submit redirect at it:
https://your-client-domain.com/thank-you/.Prefer a fully custom confirmation page? Build a normal page in the builder and point the form's redirect there instead. A dedicated confirmation URL also gives you a clean conversion signal for anything that tracks page views.
The built-in page, and any page you build with the slug thank-you, also sends a ws_conversion event to the page's data layer, so your own Google Analytics or Tag Manager setup can count each form submission as a key event. Nothing about the submission is stored in Seedly Sites.
To keep this honest:
| Piece | How |
|---|---|
| The form itself | Your CRM's embed code in an HTML / Embed Code block |
| Attribution | UTM persistence in Settings; opt-in CRM embed attribution adds the campaign to allow-listed form iframes |
| Confirmation | Built-in /thank-you/ page, or any page you build |
| Submissions | Live in your CRM, not in Seedly Sites |