Goals

Goal signal quality

Product

Goals

Updated

2026-08-09

Signal quality describes what Optimly actually observed. It prevents an interaction from being reported as a stronger outcome than the evidence supports.

Confirmed outcome

Optimly observed an explicit success signal, such as a customer-defined event emitted only after success or a supported provider completion. This is the strongest quality.

Destination reached

Optimly observed the browser arrive at the configured hostname and path. This is stronger than an outbound click because it proves the destination loaded, but it does not prove an action inside that destination completed.

Engagement

Optimly observed intent, such as a link click, native form submit event, or outbound scheduling click. Browser form submission does not prove the server accepted the form, and an iframe may not expose a cross-origin provider's completion state.

Choose the strongest honest signal

Prefer signals in this order when they are available and correctly implemented:

1. confirmed success event or provider completion;
2. confirmation destination reached;
3. destination reached;
4. form submission or link click.

Do not emit a confirmed success event on button click, form validation start, or an API request that can still fail.