How it works
You don’t need to know any of this to use Conversion Toolkit — but if you’re the curious type (or you’re vetting it before putting it on your pages), here’s exactly what happens under the hood.
Your page stays simple
When you drop a Conversion Toolkit widget onto a funnel or website page, the page itself stores almost nothing — just which widget to show (an id) and a small placeholder. It does not bake in the widget’s design, content, or logic.
That one detail is what makes everything below possible.
Edits go live everywhere — instantly
Because your page only references the widget, the actual widget is served by us at view time. So when you change a calculator’s formula, swap a theme, or fix a typo in the app:
- the change appears on every page that widget is on,
- with no page edits and no re-publishing,
- and nothing in your funnel needs to be touched.
Build once, update centrally. The same is true for improvements we ship — widgets get better without you lifting a finger.
It’s fast
The widget loads through a tiny first-party loader (a few KB) and pulls its configuration from a cache served at the edge, close to your visitor. Responses are cached for a short window and refreshed in the background, so widgets render quickly without hammering anything. When you save a change in the app, the cache for that widget is cleared immediately so visitors see the new version right away.
What you preview is what ships
The live preview inside the editor renders through the same code path as the published widget — not a lookalike mock-up. If it looks right in the preview, it looks right on your page.
It’s secure
- The admin app is a hosted, SSO-verified page inside the platform — only the logged-in user for that sub-account can manage your widgets.
- Lead writes happen on the server. When a visitor submits, the contact, tags, note, and saved results are written server-side using your sub-account’s own authorization — the browser is never trusted to write to your CRM directly.
- Everything is scoped to your location (sub-account). One business’s widgets and leads are never visible to another.
For exactly which permissions the app uses and why, see Permissions & data.
In one sentence
Your page holds a reference; we serve the widget from a fast first-party loader; your edits go live everywhere instantly; and every lead is written securely into your CRM under your own permissions.