This document provides a list of common reasons why events might not be tracking properly and suggests solutions for each issue. By understanding these common problems, you can take the necessary steps to resolve them and ensure accurate event tracking.
1. Cookies are Blocked
Issue:
If cookies are blocked by the browser, events cannot be sent to Facebook or other tracking platforms.
Cause:
Ad blockers, GDPR plugins, or cookie consent tools may block the necessary cookies for event tracking.
Solution:
- Ensure cookies are enabled in the browser.
- Avoid using ad-blocking tools or configure them to allow essential cookies for tracking.
2. Incorrect Pixel ID or Tracking Setup
Issue:
The pixel ID, conversion ID, or label (Google Ads) might be incorrect.
Cause:
If the pixel ID is missing or the wrong one is added to the FunnelKit tracking settings, the event won't be triggered.
Solution:
- Double-check the pixel ID, conversion ID, and label to ensure they are correctly configured in FunnelKit settings.
3. Purchase Event Not Tracking on Thank You/Upsell offer Page
Issue:
If the purchase event is not tracked on the Thank You/One-click upsell offer page, the issue may be related to the page not loading correctly.
Cause:
- There may be some browser console error on the thank you/offer page or showing blank.
- The Thank You page may be a custom page that is not using standard WooCommerce thank you page hooks.
- There may be a redirect to a 404 error page or another incorrect page.
Solution:
- Ensure that the user reaches the FunnelKit Thank You page or the standard WooCommerce Thank You page.
- Make sure the page is not redirecting to an error page or a custom version that prevents event firing.
4. Plugin Conflicts
Issue:
Other plugins or themes may interfere with event tracking.
Cause:
Plugins related to caching, optimization, security, or tracking might conflict with FunnelKit’s event tracking.
Solution:
- Deactivate plugins one by one to identify any conflicts.
- Use the Health Check plugin to find and isolate any conflicting plugins.
- Ensure that the tracking code is not being overridden by other plugins.
5. Tracking Disabled for Specific User Roles
Issue:
Purchase event tracking may be disabled for certain user roles.
Cause:
Custom code may be blocking event tracking for specific user roles.
Solution:
- Review any custom code added to disable event tracking for specific user roles.
- Ensure that the purchase event is not unintentionally disabled for specific roles.
- Use Incognito mode to test if events are tracking correctly for all user roles.
6. JavaScript Errors
Issue:
JavaScript errors on the page can prevent events from firing.
Cause:
JavaScript errors or conflicts with other scripts may block the execution of the event tracking code.
Solution:
- Inspect the browser’s developer console for JavaScript errors.
- Resolve any conflicts or issues with the script causing the error.
Conclusion
By addressing these common reasons, you can resolve most issues related to event tracking.
