Bonani DOSH, Dhaka - 1230, Bangladesh
Integrations
1 / 1Available Advertising Platforms and Custom Relays
Overview of supported advertising destinations and the credentials or endpoint configuration each may need.
BIG-FLYTX can route enabled events to supported browser tags, dataLayer or optional server endpoints. Available destinations include Meta, Google Analytics 4, Google Ads, Google Tag Manager dataLayer, Microsoft Ads UET, TikTok, LinkedIn, Pinterest, Snapchat, X, Reddit, Quora, Telegram and custom relays.
Configure only what you use
1. Open BIG-FLYTX → Settings and review the available integration sections.
2. Enable a destination only when your site has an account and a valid reason to send it events.
3. Add its Pixel ID, Measurement ID, API credential or endpoint where required.
4. Select a compatible tracking mode and save.
5. Send a test event and verify it in the provider’s test/debug tools.
Some integrations are browser-only; others can also support optional server delivery. Server events require global server tracking, the destination’s server switch and valid credentials. Check the specific provider settings and diagnostics; do not assume every destination sends server events by default.
Custom endpoints
For a custom relay, the site administrator chooses and configures the URL. Confirm who operates that endpoint, what information it receives, its security requirements and its privacy terms before enabling it. BIG-FLYTX does not guarantee or endorse an administrator-entered endpoint.
External-service disclosure
Depending on the enabled destinations, event names, event IDs, timestamps, URLs, referrers, UTM values, advertising click IDs, product/order details and configured identifiers may be sent to providers. Keep your privacy notice accurate as integrations change.
Configure only what you use
1. Open BIG-FLYTX → Settings and review the available integration sections.
2. Enable a destination only when your site has an account and a valid reason to send it events.
3. Add its Pixel ID, Measurement ID, API credential or endpoint where required.
4. Select a compatible tracking mode and save.
5. Send a test event and verify it in the provider’s test/debug tools.
Some integrations are browser-only; others can also support optional server delivery. Server events require global server tracking, the destination’s server switch and valid credentials. Check the specific provider settings and diagnostics; do not assume every destination sends server events by default.
Custom endpoints
For a custom relay, the site administrator chooses and configures the URL. Confirm who operates that endpoint, what information it receives, its security requirements and its privacy terms before enabling it. BIG-FLYTX does not guarantee or endorse an administrator-entered endpoint.
External-service disclosure
Depending on the enabled destinations, event names, event IDs, timestamps, URLs, referrers, UTM values, advertising click IDs, product/order details and configured identifiers may be sent to providers. Keep your privacy notice accurate as integrations change.
