Funnels are published on the hosted route /u/{slug}. The slug is the public identifier you share in ads, email campaigns, QR codes, and social posts. It stays separate from the underlying form URL so a funnel can run its own screens, visitor session, variant assignment, and conversion tracking while still creating a normal form submission at the end.
Choosing a slug
Use a slug that matches the campaign or offer rather than the internal form name:
summer-demopartner-intakepricing-checkupwebinar-signup
Keep slugs short, lowercase, and easy to read aloud. Avoid dates unless the funnel is tied to a specific event, because changing a published URL later can break ads and saved links.
Where links should point
Share the funnel URL when you want the visitor to move through multiple screens before submitting. Share the underlying form URL only when you want the classic one-page form experience.
| Destination | Use it for |
|---|---|
/u/{slug} |
Paid campaigns, quizzes, qualification flows, multi-step lead capture |
/f/{public_id} |
Direct form embeds, support intake, simple one-page collection |
When a visitor submits a form_collect screen, the resulting submission includes the funnel identifiers, so downstream automations, webhooks, notifications, and exports can still separate funnel traffic from direct form traffic.
Custom domains
Run a funnel on your own address, for example quote.yourcompany.com. Open the funnel, go to Settings > Custom domain, enter the hostname and follow the steps:
- Add the ownership record. At your DNS provider, create the TXT record shown on the page (name
_formspring.<your hostname>, valueformspring-verify=...). It is the same record Formspring uses to verify a branded short-link domain, so a hostname you already verified there is accepted without a second record. - Verify ownership. Select Verify ownership. We look up the record; if it is not published yet, the page tells you what we found. DNS changes can take a while to spread, so try again in a few minutes.
- Point the hostname at Formspring. Create the CNAME record shown on the page. Once it resolves, we issue the certificate automatically and the status changes to Live.
Use a subdomain you control. Add a path (for example /quote) to host several funnels on one domain.
The same steps are available through the API (GET /funnels/{id}/custom-domain and POST /funnels/{id}/custom-domain/verify), the MCP tools get_funnel_custom_domain and verify_funnel_custom_domain, and the PHP and JavaScript SDKs.
Domains that already serve traffic keep working. If you roll out a funnel from a client bundle, the domain you choose must be one that was verified first; a bundle cannot go live while one of its funnels carries an unverified domain.
Avoid proxying the funnel through another domain unless you also preserve cookies, request headers, and HTTPS behavior. Funnel sessions depend on a sticky visitor cookie, and broken proxy configuration can split analytics for the same visitor.
If you prefer not to connect a domain, you can still put the hosted /u/{slug} URL behind a redirect on your own site:
- Create a short path on your marketing site, such as
/go/demo. - Redirect that path to the hosted funnel URL.
- Keep UTM parameters on the redirect target so ad attribution is preserved.
Changing a live URL
Before changing a slug that has already been shared, check where it is used:
- Active ads and campaign tracking templates.
- Email sequences and autoresponders.
- QR codes on printed material.
- Partner links and internal sales playbooks.
- Webhooks or automations that filter by funnel URL.
If traffic is still active, create a branded redirect from the old URL to the new one first. Then update the source campaign links and monitor funnel analytics for unexpected drops.
