> For the complete documentation index, see [llms.txt](https://docs.edgetag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgetag.io/mcp/tools/meta-emq.md).

# metaEMQ

Get the Facebook Event Match Quality (EMQ) score for a given Facebook channel over the last 24 hours. EMQ measures how well your event data matches Facebook user profiles, directly impacting ad optimization and targeting accuracy.

### Parameters

| Parameter   | Type          | Required | Description                                                                                                 |
| ----------- | ------------- | -------- | ----------------------------------------------------------------------------------------------------------- |
| `channelId` | string (UUID) | Yes      | The Facebook channel ID. Must be a channel with `providerId: "facebook"`. Get this from the `domains` tool. |
| `teamId`    | string (UUID) | Yes      | The team ID the domain belongs to.                                                                          |

### Output

Returns the EMQ score and related metrics for the last 24 hours.

### Example

> "What's our Facebook EMQ score?"

The AI assistant will find the Facebook channel from your domains and call `metaEMQ` to display the match quality score.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.edgetag.io/mcp/tools/meta-emq.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
