Quick Verification
The fastest way to verify tracking is working:- Visit your website or open your app
- Navigate to a few pages or screens
- Go to your DATALYR dashboard
- Click Events in the sidebar
- You should see
page_vieworapp_openevents within 10 seconds
Check Event Stream
The Event Stream shows all events in real-time as they come in.Access Event Stream
- Go to Dashboard → [Your Workspace] → Events
- You should see a live stream of events
- Each event shows:
- Event name (e.g.,
page_view,button_clicked) - Timestamp
- Visitor ID
- Properties (click to expand)
- Event name (e.g.,
What to Look For
Page views should include:- Page URL or path
- Referrer
- UTM parameters (if coming from an ad)
- Device and browser info
- Visitor ID
- Event name
- Any properties you passed
- Timestamp
- Visitor ID
Test UTM Parameters
Test that UTM parameters are being captured correctly:Web Tracking
-
Create a test URL with UTM parameters:
- Visit this URL in a new incognito/private browser window
- Go to your DATALYR dashboard → Events
-
Find the
page_viewevent and expand it -
Verify these parameters are captured:
utm_source: facebookutm_medium: socialutm_campaign: test_campaign
Mobile Tracking
For mobile apps, test deep links with UTM parameters:Test Click IDs
Test that platform click IDs are being captured:Facebook Click ID (fbclid)
Visit your site with a test fbclid:fbclid appears in the event properties.
Google Click ID (gclid)
Visit your site with a test gclid:gclid appears in the event properties.
TikTok Click ID (ttclid)
Visit your site with a test ttclid:ttclid appears in the event properties.
Test Custom Events
If you’ve added custom event tracking, test those events:Web Custom Events
- Trigger the action (click button, submit form, etc.)
- Go to Events in your dashboard
- Find your custom event by name
- Verify all properties are correct
test_button_click.
Mobile Custom Events
Trigger the event in your app and check the dashboard: iOS:Test User Identification
Test that user identification is working:Web
Mobile
iOS:$identify event with the user ID and properties.
Test Purchase Tracking
Test purchase or conversion tracking:Web
Mobile
iOS:purchase event appears with correct revenue amount.
Check Browser Console
For web tracking, check the browser console for debug information:Enable Debug Mode
Script Tag:Look for Console Logs
Open browser console (F12) and look for:[DATALYR] Initialized[DATALYR] Event tracked: page_view[DATALYR] Event sent successfully
Check Mobile Logs
For mobile apps, check logs during development:iOS Debug Logs
Enable debug mode:[DATALYR] SDK initialized[DATALYR] Event tracked: app_open[DATALYR] Event sent successfully
React Native Debug Logs
Enable debug mode:Check Network Requests
Verify events are being sent to DATALYR servers:Web
- Open browser DevTools (F12)
- Go to Network tab
- Filter for
datalyrortrack.datalyr.com - Trigger an event (page view, button click, etc.)
- You should see a POST request to
https://ingest.datalyr.com/events - Check the request payload to see event data
Mobile
Use network debugging tools like Charles Proxy or Proxyman to inspect requests tohttps://api.datalyr.com.
Verify Visitor ID Persistence
Test that visitor IDs persist across sessions:- Visit your site and note the visitor ID in an event
- Close the browser
- Open a new browser window and revisit your site
- Check that the visitor ID is the same
Common Issues
No events appearing
Check:- Workspace ID or API key is correct
- Script is loaded (check Network tab)
- Ad blockers are disabled
- You’re viewing the correct workspace
- Events may take up to 10 seconds to appear
- Script is in the
<head>section deferattribute is present
- SDK is initialized before tracking events
- Network connectivity is available
- API key starts with
dk_
Events appear but missing properties
Check:- Properties are passed correctly to tracking calls
- Property names match what you expect
- Console for any errors or warnings
Duplicate events
Web:- Make sure tracking script is only loaded once
- Check that you’re not tracking the same event multiple times
- Ensure SDK is initialized only once
- Check for duplicate tracking calls
Wrong visitor ID
Check:- Cookies are enabled (web)
- Local storage is available (mobile)
- Not testing in incognito mode (visitor IDs don’t persist)
Test Before Going Live
Before connecting ad accounts or launching campaigns:- Page views are tracked on all pages
- UTM parameters are captured correctly
- Click IDs (fbclid, gclid, ttclid) are captured
- Custom events fire correctly
- Purchase/conversion events have correct revenue
- User identification works
- Visitor IDs persist across sessions
- Events appear in dashboard within 10 seconds
- No errors in browser console or mobile logs
Next Steps
Once tracking is verified:Connect Ad Accounts
Link Meta, Google, TikTok Ads
Set Up Conversions
Define conversion events
View Dashboard
See your tracking data
Troubleshooting
Fix common issues
Need Help?
Still having issues with tracking? Check our troubleshooting guide or contact support with:- Your workspace ID
- Browser/device you’re testing on
- Any error messages from console
- Screenshot of Event Stream (if applicable)