Skip to main content
This guide covers website measurement for published FloKit pages. Use your mobile measurement provider for native-app attribution. Keep access tokens out of chat and support messages.

​
Connect the selected Dataset

  1. In Meta Events Manager, select the intended website Dataset or Pixel. Reuse the established asset when appropriate instead of creating a duplicate.
  2. In Meta Business Settings, confirm that the Dataset is connected to the intended ad account.
  3. Follow the partner-sharing instructions displayed in FloKit. Share only the selected assets and review the requested permissions.
  4. In FloKit, select the same Dataset and confirm the exact website origin. Complete the account verification steps.
  5. Enter a temporary Meta test-event code only in the designated setup field when requested. Never copy it or an access token into chat, screenshots, or support messages.
Check advertising-account access and browser Pixel and Conversions API event delivery separately.

​
Check the event plan

For events delivered through both Pixel and Conversions API, the two copies must use the same logical event ID so Meta can deduplicate them. Do not send quiz answers, free text, health information, financial details, credentials, or other sensitive fields. Send personal data only when permitted by your consent and privacy requirements and the provider’s rules.

​
Verify your events

Use Meta Test Events to check the intended browser and server events. Confirm the selected Dataset and website origin, consent behavior, event names, and deduplication. Check that no unapproved fields are included. Test purchase measurement only with the intended payment mode and an explicitly approved transaction. Review the test results in Meta and the signal status shown in FloKit for the selected Dataset. For provider-side instructions, see Meta’s Pixel setup guide and Conversions API overview. For a missing asset or failed check, confirm account permissions and contact FloKit with the safe error reference, not a credential-bearing payload.