Bonani DOSH, Dhaka - 1230, Bangladesh
Integrations
1 / 1Configure Meta Pixel and Conversions API
Connect Meta browser and server events and use event IDs to help Meta deduplicate matching conversions.
Before configuring Meta
Have the correct Meta Pixel ID and, if using server-side delivery, the required Conversions API credentials ready. These values are supplied by the site owner and must be kept private.
Browser Pixel setup
1. Open BIG-FLYTX → Settings and find the Meta/Facebook integration.
2. Enable the Meta Pixel destination and enter the Pixel ID.
3. Save, then test a page view and a supported conversion event using Meta’s test tools.
Optional Conversions API setup
1. Enable global server tracking and the Meta server destination.
2. Enter the required server-side credentials in the protected settings fields.
3. If both browser and server delivery are enabled, keep shared event IDs enabled/configured so Meta can match and deduplicate the same event.
4. Send a test event and confirm the browser and server copies are recognized as one event where applicable.
Troubleshooting
If browser events arrive but server events do not, verify the server destination toggle, global server tracking, credentials and server response/diagnostics. If counts are doubled, check whether another plugin or GTM also sends the same Pixel event. Do not solve duplicates by removing event identifiers without first checking the platform’s deduplication requirements.
Meta may receive event names, event IDs, timestamps, page/referrer information, advertising click IDs, commerce values and configured hashed identifiers. Review Meta’s terms and privacy information and disclose the integration to visitors.
Have the correct Meta Pixel ID and, if using server-side delivery, the required Conversions API credentials ready. These values are supplied by the site owner and must be kept private.
Browser Pixel setup
1. Open BIG-FLYTX → Settings and find the Meta/Facebook integration.
2. Enable the Meta Pixel destination and enter the Pixel ID.
3. Save, then test a page view and a supported conversion event using Meta’s test tools.
Optional Conversions API setup
1. Enable global server tracking and the Meta server destination.
2. Enter the required server-side credentials in the protected settings fields.
3. If both browser and server delivery are enabled, keep shared event IDs enabled/configured so Meta can match and deduplicate the same event.
4. Send a test event and confirm the browser and server copies are recognized as one event where applicable.
Troubleshooting
If browser events arrive but server events do not, verify the server destination toggle, global server tracking, credentials and server response/diagnostics. If counts are doubled, check whether another plugin or GTM also sends the same Pixel event. Do not solve duplicates by removing event identifiers without first checking the platform’s deduplication requirements.
Meta may receive event names, event IDs, timestamps, page/referrer information, advertising click IDs, commerce values and configured hashed identifiers. Review Meta’s terms and privacy information and disclose the integration to visitors.
