Bonani DOSH, Dhaka - 1230, Bangladesh
Configuration
1 / 1How to Choose a BIG-FLYTX Tracking Mode
Understand Full Tracking, dataLayer Only, Server Only and Monitor Only before connecting pixels or APIs.
BIG-FLYTX offers several delivery modes so it can fit different WordPress tracking setups. Choose one deliberately; enabling overlapping browser tags in multiple tools can create duplicate conversions.
Full Tracking
Use Full Tracking when BIG-FLYTX should manage browser tracking and any server destinations you explicitly configure. Enable only the providers and event types you need.
dataLayer Only
Use dataLayer Only when Google Tag Manager (GTM) should load and control the final tags. BIG-FLYTX publishes normalized event data to the dataLayer; configure GTM separately to map those events to your tags and triggers. Do not also install duplicate browser pixels through BIG-FLYTX unless you intentionally want both paths.
Server Only
Use Server Only when browser pixels are already managed elsewhere but you want BIG-FLYTX to send configured server-side events. Global server tracking, the destination-specific server toggle and the required credentials must all be configured. Server delivery is not automatic just because this mode is selected.
Monitor Only
Use Monitor Only while checking event capture and plugin behavior without sending events to advertising platforms. This is a useful first step for testing a new installation or investigating unexpected conversions.
Changing modes
After changing a mode, save the settings and run a test journey: view a page, submit a supported lead form or complete a test WooCommerce flow. Check BIG-FLYTX activity/diagnostics and the destination’s test tools. Confirm that the same action is not also being sent by another plugin or GTM container.
Full Tracking
Use Full Tracking when BIG-FLYTX should manage browser tracking and any server destinations you explicitly configure. Enable only the providers and event types you need.
dataLayer Only
Use dataLayer Only when Google Tag Manager (GTM) should load and control the final tags. BIG-FLYTX publishes normalized event data to the dataLayer; configure GTM separately to map those events to your tags and triggers. Do not also install duplicate browser pixels through BIG-FLYTX unless you intentionally want both paths.
Server Only
Use Server Only when browser pixels are already managed elsewhere but you want BIG-FLYTX to send configured server-side events. Global server tracking, the destination-specific server toggle and the required credentials must all be configured. Server delivery is not automatic just because this mode is selected.
Monitor Only
Use Monitor Only while checking event capture and plugin behavior without sending events to advertising platforms. This is a useful first step for testing a new installation or investigating unexpected conversions.
Changing modes
After changing a mode, save the settings and run a test journey: view a page, submit a supported lead form or complete a test WooCommerce flow. Check BIG-FLYTX activity/diagnostics and the destination’s test tools. Confirm that the same action is not also being sent by another plugin or GTM container.
