Verifying Tracking & Understanding Signal Timing

After installing the tracking snippet or configuring integrations, the next step is to confirm that signals are reaching OneLence.

This page helps you verify that installation is working correctly and explains why some insights may appear with a short delay.

Checking Initial Event Reception

To confirm that basic tracking is operational:

1. Open your website in a fresh private or incognito browser window.
2. Ensure no ad blockers or privacy extensions are active in this testing session.
3. Accept the cookie or consent banner if your site shows one.
4. Navigate across several pages.
5. Perform at least one meaningful action such as:
   • clicking a primary CTA
   • starting signup
   • submitting a form
   • entering checkout

Then check the OneLence dashboard.

You should observe:

• integration status changing from waiting → active
• recent activity indicators beginning to appear
• initial visitor or session signals becoming visible

Seeing even one visitor signal confirms that installation is functioning.

If no signals appear, allow a short processing interval before continuing debugging.

Understanding Signal Processing Timing

Tracking data does not always appear instantly as insights.

Signals move through several processing steps before becoming visible in dashboards.

In practical terms:

• page visits and simple events may appear within seconds
• attribution insights may take slightly longer
• conversion intelligence may require multiple user signals

This behaviour is normal and does not indicate a failed integration.

Common “False Alarm” Situations

Tracking can appear inactive even when working correctly.

Typical causes include:

• consent not yet granted (visitor identity unavailable)
• testing without triggering meaningful actions
• attribution parameters missing from the test session
• conversion tracking not yet configured
• testing on localhost, preview, or staging environments not registered in OneLence
• using an incorrect tracking key

Before assuming an error, confirm that:

• the SDK loads without browser console errors
• at least one real interaction has been triggered
• testing is performed on the live tracked domain

Recommended Verification Test Flow

Use this simple validation sequence:

1. Open the site in a private browser window.
2. Disable ad blockers or tracking-blocking extensions.
3. Accept consent banner if shown.
4. Visit multiple pages.
5. Trigger one tracked action such as signup or CTA click.
6. Wait briefly and refresh the OneLence dashboard.

Successful completion of this flow confirms that basic signal transmission is working correctly.

You should complete this verification before configuring advanced tracking logic or launching campaigns.