Choosing how to host a form
Before you share a form, decide where respondents will reach it. There are three options, and they work together rather than compete: one org can use all three, and a single form can be reachable more than one way.
Compare the three
Section titled “Compare the three”| Sliick Edge | Experience Cloud | Custom site | |
|---|---|---|---|
| What it is | We host your public forms at an address of your own, such as https://acme.sliick.net | The Sliick Experience Form component placed on a page of your own Experience site | A form placed anywhere else, whose address only you know |
| Needs an Experience site | No | Yes | Depends where you put it |
| Can serve forms behind login | No, it does not authenticate anyone | Yes | Depends where you put it |
| Setup | Connect the org once, then tick each form | Publish a site, place the component, and set up guest access for public forms | Nothing org-wide: paste the form’s own Share URL |
| Bot protection | The hidden-field trap plus an automatic Cloudflare Turnstile check | The hidden-field trap | The hidden-field trap |
| Traffic controls in front of your org | Rate limiting and bot filtering, because the hosting sees the visitor’s address | None: Salesforce serves the page directly | Depends where you put it |
| Embedding on your own site | Yes, with a ready-made <iframe> snippet | Not offered here | Not offered here |
| View and start tracking for the funnel | Yes | Not generally available | Not generally available |
Placement is a security decision on a form that attracts abuse. Salesforce’s own protections against flooding are org-wide rather than form-shaped, so a flood against a form served directly by Experience Cloud consumes your org’s capacity, not just that form’s. A form served from Sliick Edge is filtered before it reaches Salesforce. Nothing in the package rate-limits anything, and a response cap is a data backstop rather than an abuse control: a spammer who exhausts it closes the form to genuine respondents.
Rules of thumb:
- A public form, and you would rather not build an Experience site: use Sliick Edge.
- A form behind portal login: it has to be Experience Cloud, because Sliick Edge does not authenticate anyone.
- A public form on a page you have already built, or a form embedded somewhere unusual: use the form’s own Share URL and treat it as a custom site.
Set the org-wide addresses
Section titled “Set the org-wide addresses”Both org-wide addresses live in the Delivery panel on the Admin Dashboard, one tab each. Each tab carries its own status dot, so you can see what is set up without opening it.
Sliick Edge. Optional. Click Connect, choose an integration user, and take the address the box already suggests, drawn from your Salesforce My Domain name. Connecting the org does not publish anything by itself: each form still needs Allow on your public Sliick Edge address ticked under its own Availability settings before it is served there. This tab also shows Edge cache refresh, telling you whether your last publish actually reached your public forms.
Experience Cloud. The address of the page that serves your forms, entered as a template. Click Set address and put {form} where a form’s external ID belongs, so one setting serves every form, for example https://acme.my.site.com/s/forms?form={form}. As you type, the panel previews the link one of your own forms would actually get, resolved by the same logic that produces real share links, so if the preview is empty your forms would get nothing too. A value with no {form} placeholder simply has /<external id> appended to it, and a single trailing slash is trimmed when the value is saved.
This writes the same setting as Setup, Custom Settings, Forms Settings. Note the two spellings: the dashboard says Experience Cloud, the custom setting field is labelled Public Site Address.
Custom site. For a form that lives on its own page, or anywhere the address does not follow a pattern. There is nothing org-wide to set here: open the form and fill in its own Share URL on the Share tab.
When more than one applies to the same form
Section titled “When more than one applies to the same form”The share link is resolved in a fixed order, stopping at the first hit: the form’s own Share URL, then Sliick Edge for a form allowed on it, then the Experience Cloud template. See Sharing a form.