> For the complete documentation index, see [llms.txt](https://docs.adpage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adpage.io/faq/faq-nl/marketingoptimalisatie/welke-standaard-meta-ads-events-komen-overeen-met-standaard-ga4-events.md).

# Welke standaard Meta Ads-events komen overeen met standaard GA4-events?

Koppel standaard GA4-events aan de bijbehorende Meta Ads-events.

Wanneer je server-side tagging voor Meta Ads instelt, kom je voor een praktische uitdaging te staan: hoewel beide platforms werken volgens het GA4 Measurement Protocol, dat inmiddels de internetstandaard is geworden, gebruiken ze verschillende naamgevingsconventies voor dezelfde gebeurtenissen.

Waar GA4 kleine letters en underscores gebruikt (bijv. add\_to\_cart), gebruikt Meta Ads PascalCase-notatie (AddToCart). Correcte eventmapping is essentieel voor consistente gegevensverzameling en betrouwbare attributie van conversies in beide systemen.

De onderstaande tabel bevat de standaard eventnamen zoals erkend door GA4 en Meta Ads. Houd er rekening mee dat deze hoofdlettergevoelig zijn en exact aan de specificaties moeten voldoen.

| page\_view          | PageView             |
| ------------------- | -------------------- |
| add\_payment\_info  | AddPaymentInfo       |
| add\_to\_cart       | AddToCart            |
| add\_to\_wishlist   | AddToWishlist        |
| sign\_up            | CompleteRegistration |
| contact             | Contact              |
| customize\_product  | CustomizeProduct     |
| donate              | Donate               |
| find\_location      | FindLocation         |
| begin\_checkout     | InitiateCheckout     |
| generate\_lead      | Lead                 |
| purchase            | Purchase             |
| schedule            | Schedule             |
| search              | Search               |
| start\_trial        | StartTrial           |
| submit\_application | SubmitApplication    |
| subscribe           | Subscribe            |
| view\_content       | ViewContent          |


---

# 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.adpage.io/faq/faq-nl/marketingoptimalisatie/welke-standaard-meta-ads-events-komen-overeen-met-standaard-ga4-events.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.
