Plugin settings
Every plugin — built-in or uploaded — has a settings surface: where it renders, how it behaves, and whether it is on. This guide is the control room.
The settings you will touch
| Setting | Meaning |
|---|---|
| Enabled (per site) | The master toggle — off means the plugin never renders |
| Slot | Where on the page it injects (plugins declare their slots) |
| Options | Per-plugin behavior: thresholds, colors, labels, limits |
| Scope | Site-wide or specific page types, where the plugin supports it |
Options are validated on save — a nonsense value bounces with a message instead of silently doing nothing.
The cache, honestly
Plugins are cached for speed (they render on every page view). In normal use this is invisible; while ITERATING on an uploaded plugin the short dev cache means a re-upload is live in seconds — refresh and look. If a change ever seems stuck, hard-refresh once before suspecting the cosmos.
Disabling vs deleting
- Disable — the plugin stops rendering instantly. Settings remain; re-enabling is one toggle. This is the right move for seasonal plugins (a greeting banner in December) and experiments.
- Delete (uploaded only) — the plugin is gone for good. Export/keep the source folder first; see Deleting content.
Built-in plugins cannot be deleted — they are platform features; you merely toggle them off.
When two plugins disagree
Plugins share a page. Two that fight for the same eyeball space (a greeting banner plus a cookie banner plus a newsletter popup on load) read as clutter no matter how nice each is alone. The etiquette:
- One plugin per page region.
- One popup campaign at a time (see Popups).
- Preview at phone width after every enable — the phone is where crowding shows first.
Tip
The quarterly plugin audit: open the list, and for each enabled plugin ask "when did a visitor last benefit from this?". Disable the ones with no answer. A site sheds weight; the ones that remain earn their place.
Settings and the publish loop
Plugin setting changes follow the site's publish flow like any appearance change — preview first, publish once (see Live preview, Editing pages). A toggle is cheap; a page that surprises visitors is not.
Where the limits are
Plugins render on YOUR public pages — they cannot reach the dashboard, other users' sites or platform internals. Plan gates apply to some built-ins (the toggle is honest about it — see Plans compared). Anything the format cannot express is an integration request away (see Contacting support).
Note
Plugin renders appear in your analytics as part of the page, not as separate events — the honest measurement of a plugin is visitor behavior before and after enabling it, which the first-party analytics make easy to compare.