# Reporting and Data Quality Assurance

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**.

### 1. Where to Find Reports

1. Go to [Meta Business Manager](https://business.facebook.com/) → **Events Manager**.
2. Select the **Pixel ID** that you configured.
3. Open the **Overview** and **Diagnostics** tabs to review:
   * Total event counts per event type
   * Errors and warnings
   * Event match quality scores

### 2. Understanding Event Counts

* **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.

### 3. Event Match Quality

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.

{% hint style="success" %}
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.
  {% endhint %}

### 4. Debugging with Test Events

* 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.

### 5. Error Messages & Troubleshooting

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.

{% hint style="success" %}
With reporting and diagnostics in place, you can ensure your Meta CAPI integration is sending **complete, valid, and high-quality data**.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.jentis.com/data-activation/connectors/meta/reporting-and-data-quality-assurance.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.