> For the complete documentation index, see [llms.txt](https://developers.make.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.make.com/white-label-documentation/release-notes/facebook-conversions-api-connection-update-by-may-9-2026.md).

# Facebook Conversions API connection update by May 9, 2026

**Action required:** **Reauthorize Facebook Conversions API connections**

Meta is updating its security requirements for Facebook Conversions API connections. To keep your scenarios running without interruption, you must reauthorize affected connections after this update is released and before **May 9, 2026**.

### What’s changing

Meta’s updated security requirements affect existing connections for the **Facebook Conversions API** and **Facebook Conversions API for CRM** apps.

After the update is released, these connections must be reauthorized to continue working. Your existing scenarios will continue to run until **May 9, 2026**. After this date, scenarios using connections that haven’t been reauthorized might fail.

### What you need to do

Reauthorize your affected Facebook Conversions API connections before **May 9, 2026**.

1. Go to the **Connections** page in your Make account.
2. Find your existing connection for **Facebook Conversions API** or **Facebook Conversions API for CRM**.
3. Click **Re-authorize**.
4. Follow the prompts to sign in to your Facebook account again.

### Resources

* [Facebook Conversions API app documentation](https://apps.make.com/facebook-conversions-api)
* [Meta for Developers: Secure Graph API Requests](https://developers.facebook.com/docs/graph-api/guides/secure-requests/)


---

# 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://developers.make.com/white-label-documentation/release-notes/facebook-conversions-api-connection-update-by-may-9-2026.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.