Goals
Goals
Turn observed website signals into tested, named business outcomes.
A goal is a named business outcome recognized from one or more observed website signals. Optimly keeps the business outcome separate from the technical rule used to recognize it.
Supported rule types
| Rule | Matches | Quality |
|---|---|---|
| Destination reached | Authorized hostname and optional exact or prefix path | Destination reached |
| Link clicked | Safe target hostname/path and optional stable element key | Engagement |
| Form submitted | Safe form key or normalized form action | Engagement |
| Custom event | Validated customer-defined event emitted after success | Confirmed outcome |
| Provider completed | A supported provider completion adapter | Confirmed outcome when the adapter observes success |
Configure a goal
- Open Goals for the connected website.
- Tell Ask Optimly the meaningful action you want to measure.
- Review the signals Optimly has actually observed for the site.
- Choose whether the goal is primary or secondary.
- Review the proposed rule and its signal-quality label.
- Start a bounded test window.
- Perform the action once on the authorized website.
- Review the matched observation.
- Confirm exactly what will count and activate the displayed draft.
A site can have one active primary goal and multiple secondary goals. A single browser session that matches several rules for the same goal counts once as a goal-reaching session.
Goal lifecycle
Goals move through draft, active, paused, and archived states. A draft must be tested or activated with an explicit unverified override. Changing a draft invalidates a previous confirmation so an older approval cannot activate different rules.
Pausing a goal stops future matching without deleting historical results. Archiving is for goals that should no longer return to active use.