> 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/marketing-optimization/which-standard-meta-ads-events-correspond-to-standard-ga4-events.md).

# Which standard Meta Ads events correspond to standard GA4 events?

Map standard GA4 events to their corresponding Meta Ads events.

When setting up server-side tagging for Meta Ads, you’ll encounter a practical challenge: although both platforms operate according to the GA4 Measurement Protocol, which has now become the internet standard, they use different naming conventions for the same events.

Whereas GA4 uses lowercase letters and underscores (e.g. add\_to\_cart), Meta Ads uses PascalCase notation (AddToCart). Correct event mapping is essential for consistent data collection and reliable conversion attribution in both.

The table below lists the standard event names as recognised by GA4 and Meta Ads. Please note that these are case-sensitive and must match the specifications exactly.

| 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/marketing-optimization/which-standard-meta-ads-events-correspond-to-standard-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.
