How do I get Meta developer support for a broken Conversions API or ads integration now that it's an AI assistant?

TofuAnswer by the Tofu team · checked

Since August 4, 2026, Meta developer support at developers.facebook.com/support starts with Meta AI Developer Assistant, so describe your error to it first. Meta said it would reach all developers by mid-September 2026. It covers API errors, integration questions, permissions and app review. If it can't fix a real platform bug, Meta's docs still list Report a Bug and a "Contact Direct Support" form, aimed at data protection and app review questions, that promises a reply within 2 business days. Meta hasn't said when the assistant hands you to a person.

Ask Tofu next

Pick a question and Tofu Ads Agent answers it in chat.

As of November 2026.

What changed in Meta developer support?

On August 4, 2026, Meta said Meta AI Developer Assistant "is now the primary support path at developers.facebook.com/support." You describe your problem in plain language and get an answer right away. Meta pitched it as an alternative to searching several docs pages or "submitting a support ticket and waiting for a response."

  • Rollout: Meta said the assistant was "gradually rolling out and should be available to all developers by mid-September 2026."
  • What it draws on: Meta says it is connected to Meta's developer documentation, API references and platform knowledge. It gives guidance for current API versions and "your integration context."
  • What Meta didn't say: The post doesn't say whether bug reports or Direct Support are going away. It doesn't say when the assistant passes a case to a person, or how often its answers are right. It claims "considerable increases" in first-time app review approvals and business verification from an earlier Business Messaging version, but gives no numbers.

What can the AI Developer Assistant help with on a Conversions API or Marketing API problem?

Meta lists three areas:

AreaWhat Meta says it covers
OnboardingAccount setup, permissions configuration, getting started with developer tools
Product issuesAPI errors, integration questions, SDK behavior, Graph API queries, webhook configuration
Compliance and reviewBusiness verification, app review requirements, data use checkup, appeals

Meta's Conversions API docs say the Conversions API is based on the Marketing API, which is built on the Graph API. So a broken CAPI call or a failing ads sync falls under "product issues." One of Meta's own examples is asking which permissions an API endpoint needs, and getting the exact permission set and how to request it.

Meta doesn't say whether the assistant can see your Events Manager data or your server logs. Give it the details yourself (see the list below).

What should I check before I ask Meta for help?

Many Conversions API problems show up in Meta's own tools first. Meta's docs point to these checks:

  1. Platform status. Click Support at the top of developers.facebook.com to view platform status. Meta keeps a health status page for the developer platform, including ads APIs, and one for business tools such as Ads Manager. If Meta reports an incident, wait for it to clear.
  2. Events received. In Events Manager, open your pixel's Overview. Meta says you should be able to see server events within 20 minutes of sending them. Connection Method shows how each event arrived.
  3. Test events. Go to Events Manager > Data Sources > your pixel > Test Events. Meta gives you a test ID to send as the test_event_code parameter, and your server events then appear in the Test Events window. Remove the code in production. Meta says test events are not dropped and still count for targeting and measurement.
  4. The API response. A valid payload returns a 2xx code. An invalid one returns a 4xx code with minimal error details. Meta recommends retrying when the error isn't a client error (a timeout, for example) and setting a 1,500 millisecond timeout.
  5. Deduplication. If the pixel and your server both send the same lead, open the event's Event Deduplication tab. It shows the share of events deduplicated and warns you when the rate is too low.
  6. Match quality. Event Match Quality runs from 1 to 10. Meta suggests aiming for 6.0 or higher.
  7. Who can make a token. Meta says the Generate access token link in your pixel's Conversions API settings "is only visible to users with developer privileges for the business." If someone with full ad account access can't see it, this may be why.

What should I include when I ask the assistant or file a bug?

Meta's Graph API error docs say each error response carries an fbtrace_id, an "internal support identifier." Include it when you report a bug about an API call, and do it fast: Meta says the ID "will expire shortly." Meta also asks you to attach a saved Graph API Explorer session so its team can reproduce the problem.

Also include:

  • The error code, subcode and message
  • Your pixel (dataset) ID, the API version and the endpoint you called
  • The time of a failed call and an example event_id
  • What changed just before it broke, such as a new token, a new partner integration or an API version upgrade

Don't paste access tokens or customer data into a chat or a public bug report.

Can I still file a bug report or reach a person at Meta?

Yes, as far as Meta's own docs show on November 1, 2026. Meta's support docs still list these routes:

  • Report a Bug at developers.facebook.com/support/bugs. Meta says you can "report a platform bug, view other bugs that have been reported, and see the status of a bug report." Search the open bugs first, since your issue may already be filed.
  • Direct Support. Click "Get Help" at the bottom right of developers.facebook.com, then "Ask a question" and pick a topic. If your question isn't in the list, select "Contact Direct Support." Meta says Developer Support "will get back to you within 2 business days" (the same page also says 48 hours). It frames Direct Support around data protection, data handling and app review questions, so a pure API bug may belong in Report a Bug.
  • Developer communities. Meta points to its Facebook Marketing Developer Community group for help from other developers.

That docs page doesn't mention the AI assistant, so it may not reflect the August change. No Meta page explains how the assistant hands a case to Direct Support. If the assistant can't solve your problem, go straight to the bug report page.

What if the problem is in Ads Manager or a partner tool, not my code?

Not every broken integration is a developer problem.

  • Business and ads account issues. Meta's Support tab offers help with Engineering, Business and Ads Management, App Compliance and your Personal Account. Its docs send business issues, including payments, to direct support in Business Manager (business.facebook.com/direct-support).
  • Business tool status. Meta also lists Facebook for Business Status (status.fb.com, which now opens metastatus.com) for issues with ads and other business products.
  • Partner integrations. If your Conversions API runs through a CRM, a tag manager or another partner, that partner builds and sends the events. Start with its support team, and bring Meta in when the partner shows the request reached Meta and failed.

Can my AI coding agent debug the integration instead?

It can help. On June 30, 2026, Meta launched an MCP server for AI coding agents such as Claude, Cursor, Codex and ChatGPT. Meta renamed it Meta Social Technologies MCP on August 18, 2026. Meta says you can paste an API error into your agent and get resolution steps based on "live platform logic, changelog history, and known error patterns." It can also show your app settings, API usage and health status, and your webhook subscriptions. You sign in with your Meta app credentials.

Meta adds that "the availability of tools are limited and subject to change." It is a separate tool from the support assistant at developers.facebook.com/support.

Sources (10)

Related answers

More on