Once your events and parameters are implemented in JENTIS and sent to Meta (Pixel + Conversion API), it is important to validate the data flow and monitor quality.
Go to Meta Business Manager → Events Manager.
Select the Pixel ID that you configured.
Open the Overview and Diagnostics tabs to review:
Total event counts per event type
Errors and warnings
Event match quality scores
Frontend Pixel Events
Reported as a raw count.
Shows all events directly captured in the browser.
CAPI Events (server-side)
Reported as a filtered and processed value.
May not match frontend event counts, even for the same event type (PageView, Purchase).
👉 A difference between frontend and CAPI counts is expected and normal.
Meta provides a match quality score for each event. This rating indicates how well Meta can match your event data with its user database.
High match quality: You send enough hashed PII (email, phone, external_id, etc.).
Low match quality: Some identifiers are missing or not hashed correctly.
To improve match quality:
Always include fbc, fbp, and external_id when possible.
Add hashed values of email and phone.
Ensure hashing follows Meta's CAPI hashing requirements.
Navigate to Test Events in your Pixel settings.
Use the Test Event Code (generated earlier) in your JENTIS setup.
Verify events arrive in real time while browsing in preview mode.
In the Diagnostics tab you may see:
Missing parameters → Ensure all mandatory fields are provided in JENTIS tags.
Unhashed PII → Double-check that sensitive values are hashed before submission.
Event deduplication issues → Avoid sending the same event via multiple sources without configuring deduplication.
With reporting and diagnostics in place, you can ensure your Meta CAPI integration is sending complete, valid, and high-quality data.
Last updated
Was this helpful?
Was this helpful?
