Optimly Developer Documentation

Optimly Connect

Verify an installation

In short

Prove that the collector accepted an event for the configured key and exact origin.

Product
Optimly Connect
Updated

Verification proves that Optimly accepted data for the configured site key and origin. Finding a script element in the page is useful diagnostic evidence, but is not proof that collection works.

Verify in Connect

  1. Open the exact configured website origin in a fresh tab.
  2. Reload after the published snippet is live.
  3. Open Optimly Connect and select Verify installation.
  4. Wait for Receiving data.
  5. Open Site Insights and confirm the latest accepted-event time and beacon version.

Verify in browser developer tools

  1. Open Developer Tools and select Network.
  2. Enable Preserve log.
  3. Filter for site-insights.
  4. Reload the page.
  5. Confirm the beacon request succeeds.
  6. Confirm the configuration request succeeds for the current origin.
  7. Confirm the event request returns HTTP 202 with accepted: true.

In test mode, the request must also identify the event as test traffic.

What success means

Receiving data means the collector accepted at least one event for:

  • the site key generated for this Site Insights site;
  • the exact allowed origin;
  • a site whose collection state permits the event;
  • a valid, bounded event payload.

It does not mean that a goal has been configured or reached. Configure and test Goals separately.

Common failure states

SymptomWhat to check
Beacon not foundPublished revision, shared layout placement, duplicate staging/production environments
Origin mismatchExact scheme, hostname, and port; preview domains are separate origins
Configuration blockedCSP connect-src, privacy extensions, proxy or firewall rules
Script blockedCSP script-src, incorrect asset origin, HTML sanitizer
Invalid site keyCopy the entire server-generated snippet again
Duplicate page viewsRemove the second snippet from page embeds, tag managers, or another shared layout
Events accepted but no goal resultTest the active goal's exact rule; an event receipt is not automatically a goal match

Collection failures are designed to fail open for the host website: Optimly should not interrupt the page's normal behavior.