The setup checklist
Optimeleon walks you through installation as a checklist that verifies itself against real traffic. Here is what each step proves before it turns green.
Installation lives at /setup in the app, and it is a checklist rather than a page of instructions. Each step turns green only when Optimeleon has seen the thing actually happen in your live traffic, not when you tick a box.
The five steps
| Step | What it proves | Guide |
|---|---|---|
| 1 · Tracking domains | Your project has at least one allowlisted domain, so events from your site are accepted at all. | Tracking domains |
| 2 · Remove Optimeleon 1.0 | The old snippet is gone from your pages. Only appears if we detect it. | Migrating from 1.0 |
| 3 · Script | The snippet is live: a real pageview from your site has reached the collector. | Installing the script |
| 4 · Consent | Your consent banner is wired: a consent call (grant, decline or withdrawal) has reached Optimeleon. | Consent & cookies |
| 5 · Conversion events | At least one of your conversion events has fired for real. | Conversion events |
How the checklist behaves
It blocks where blocking is honest
Steps 1 and 2 are hard gates. Without an allowlisted domain nothing can ever verify, and with the 1.0 snippet still on the page the 2.0 install would be racing it. The later steps stay locked until those clear.
Everything else is a warning, not a block. A snippet pasted lower in the <head> than it should be raises an amber marker and lets you carry on. It is worth fixing, but it does not stop you installing.
It is resumable, and it never goes backwards
Progress is derived from your traffic each time you open the page, so you can leave mid-install and come back to find your cleared steps still cleared. A step that has gone green stays green.
It stays after you finish
Once every step verifies, the progress chip comes off the sidebar but the Setup entry stays. Come back any time to re-check the script, copy the snippet again, or review your consent wiring.
If a step will not go green
- Script step stuck. The snippet is probably being rewritten or delayed by a speed plugin, or blocked by a Content Security Policy. Both are covered in Installing the script.
- Consent step stuck. Your CMP is not calling Optimeleon. Note that a decline counts too, because any consent decision proves the wiring works.
- Conversion step stuck. The event exists in Optimeleon but its snippet is not on the code path that runs when the conversion happens.