Bonani DOSH, Dhaka - 1230, Bangladesh
Testing & Troubleshooting
1 / 1Troubleshooting Missing or Duplicate Events
A systematic checklist for events that are not recorded, not delivered or counted more than once.
If no events appear
1. Confirm BIG-FLYTX is explicitly authorized and enabled; activation alone leaves it paused.
2. Check the selected tracking mode. Monitor Only records for inspection but does not send to ad platforms.
3. In Strict visitor gate mode, confirm the visitor’s consent signal is set correctly. In Site-owner managed mode, confirm the site’s consent tool is not blocking the integration unintentionally.
4. Confirm the event source is supported and the relevant integration is enabled.
5. Recheck Pixel/Measurement IDs, API credentials and destination-specific server switches.
6. Use the plugin’s Diagnostics or Health Check and the provider’s test/debug tool. Check the WordPress/PHP error log for server failures.
If events are duplicated
1. Check whether the same pixel or tag is installed by the theme, GTM, another plugin and BIG-FLYTX at the same time.
2. If GTM controls tags, consider dataLayer Only and disable duplicate direct browser tags.
3. If using browser and server delivery together, verify that matching events share event IDs and that the destination accepts/deduplicates them.
4. Make one change at a time and repeat a single controlled test.
If browser works but server delivery fails
Confirm global server tracking and the destination’s server toggle are both enabled, the credentials are valid, outbound requests are allowed by the hosting provider, and the event is allowed by consent settings. Use delivery logs/diagnostics and the provider’s test view to locate the failing stage.
When asking for support, include the plugin version, WordPress/PHP/WooCommerce versions, tracking mode, affected event and a sanitized diagnostic message. Never send API tokens, customer personal data or full payment/order details.
1. Confirm BIG-FLYTX is explicitly authorized and enabled; activation alone leaves it paused.
2. Check the selected tracking mode. Monitor Only records for inspection but does not send to ad platforms.
3. In Strict visitor gate mode, confirm the visitor’s consent signal is set correctly. In Site-owner managed mode, confirm the site’s consent tool is not blocking the integration unintentionally.
4. Confirm the event source is supported and the relevant integration is enabled.
5. Recheck Pixel/Measurement IDs, API credentials and destination-specific server switches.
6. Use the plugin’s Diagnostics or Health Check and the provider’s test/debug tool. Check the WordPress/PHP error log for server failures.
If events are duplicated
1. Check whether the same pixel or tag is installed by the theme, GTM, another plugin and BIG-FLYTX at the same time.
2. If GTM controls tags, consider dataLayer Only and disable duplicate direct browser tags.
3. If using browser and server delivery together, verify that matching events share event IDs and that the destination accepts/deduplicates them.
4. Make one change at a time and repeat a single controlled test.
If browser works but server delivery fails
Confirm global server tracking and the destination’s server toggle are both enabled, the credentials are valid, outbound requests are allowed by the hosting provider, and the event is allowed by consent settings. Use delivery logs/diagnostics and the provider’s test view to locate the failing stage.
When asking for support, include the plugin version, WordPress/PHP/WooCommerce versions, tracking mode, affected event and a sanitized diagnostic message. Never send API tokens, customer personal data or full payment/order details.
