After installing and configuring the OneLence SDK, it is important to verify that events, attribution signals, and conversion data are being received correctly.
Systematic testing helps ensure that marketing insights and growth decisions are based on reliable data.
Verify SDK Initialization
Start by confirming that the SDK loads and initializes successfully.
Typical verification steps:
- open your website in a browser
- inspect the developer console
- confirm that no SDK initialization errors are present
- check that debug logs appear when
debug: trueis enabled
Initialization issues are often caused by:
- incorrect tracking key
- multiple SDK initializations
- script loading blocked by content security policies
Confirm Page View Tracking
Automatic page view tracking should emit events when:
- the page loads
- users navigate between routes in single-page applications
To validate:
- navigate across several pages
- observe console debug logs
- check whether page view signals appear in the OneLence dashboard within a few seconds
Delayed visibility can occur due to consent gating or network buffering.
Test Attribution Parameter Capture
Campaign attribution can be tested by visiting your site with tracking parameters.
Example test URL:
https://www.example.com/?utm_source=test&utm_campaign=integration_check
After visiting:
- trigger a few interactions
- confirm that attribution values appear in event records
- verify that consent configuration does not block parameter persistence
Validate Custom Event Emission
If manual events are implemented, confirm that they are triggered at the expected interaction points.
Typical test actions include:
- clicking primary call-to-action buttons
- completing signup flows
- initiating checkout sequences
Check both:
- browser console debug output
- OneLence dashboard event timeline
Troubleshoot Hybrid and Server Tracking
For server-validated conversions:
- confirm that visitor IDs are correctly passed from browser to backend
- verify that backend SDK calls return successful responses
- inspect webhook or queue processing logs
Mismatch between browser and server attribution often indicates:
- missing visitor identifier propagation
- incorrect site context configuration
- delayed backend event processing
When to Seek Integration Support
If tracking signals remain inconsistent after verification:
- capture console logs and SDK version details
- document reproduction steps
- confirm consent banner behaviour
- validate environment configuration (staging vs production)
Providing structured debugging context helps support teams resolve integration issues more efficiently.