Skip to content
ChatterfyHelp Center
HomeGeneralCRMAI ManagerTrackerPlatformsFAQUpdate log
FAQ
Tracker Errors
Tracker Errors
Error: fbclid is empty in source logs
Error: Post graph.facebook.com in source logs
Telegram Errors
FAQs
  1. FAQ
  2. Tracker Errors
  3. Error: Post graph.facebook.com in source logs

Error: Post graph.facebook.com in source logs

This error appears in next to the Facebook source. The message Post graph.facebook.com with an error label means that Chatterfy could not send the event to the Facebook Conversions API . The request t

Updated August 30, 20263 min
This error appears in Logs — event logs next to the Facebook source. The message Post graph.facebook.com with an error label means that Chatterfy could not send the event to the Facebook Conversions API. The request to graph.facebook.com either timed out, returned an error, or never got through.


Why this happens

Facebook restricts access to the Conversions API from certain regions and networks. To allow Chatterfy to send events (Subscribe, Contact, Registration, FD) back to the ad account reliably, there is a proxy between our servers and graph.facebook.com.
If the proxy performs poorly, responds with a delay of more than 10 seconds, or is completely unavailable, every send attempt returns Post graph.facebook.com error. Without working event delivery, Facebook does not receive optimization data, and the algorithms stop finding the target audience.


What to do

  1. 1

    Check the current proxy

    Open the Proxy — proxy for S2S section and make sure a proxy is specified, the status is Active, and there are no red labels. If the health indicator is red, Tracker periodically checks the connection itself and signals the problem.
  2. 2

    Replace the proxy

    If the proxy is inactive, add a new one. Any stable residential or datacenter proxy that allows requests to graph.facebook.com will work. The lower the latency, the fewer missed events. After replacement, errors usually disappear within 5–15 minutes.
  3. 3

    Check the source logs

    After replacement, open Logs — event logs and make sure new Subscribe / Contact events are sent without errors. Changes will not affect previous entries in the log — they record the moment of the failure.
The proxy is not connected at all
If Proxy — proxy for S2S is empty, the Conversions API does not work for any Facebook campaigns in this company. Connect a proxy before launching FB campaigns. Without a proxy, events cannot be sent to graph.facebook.com — they will not arrive.
To prevent this from happening again
Do not use free “trial” proxies for live traffic — they often go down after a few hours. Once a week, go to Tracker → Proxy and check the status. If you work with a large volume of FB traffic, keep a backup proxy in case the main one fails.


Frequently asked questions

All events that should have gone to graph.facebook.com during this period — Subscribe, Contact, Registration, FD for Facebook campaigns. Inside Chatterfy, events are saved (visible in Messenger), but Facebook will not know about them, and ad optimization for this window will not take them into account. They cannot be restored retroactively through the proxy — Facebook accepts only fresh events (up to 24 hours from the time they occurred).

Most often, the proxy has gone down. Less often, Facebook has changed API requirements (for example, the old access token has expired). First, check the proxy in Proxy — proxy for S2S, then the integration token in Integration Types. If both are fine but the error does not go away, message @chatterfy_support.

Yes. graph.facebook.com is Facebook Conversions API. Google, Telegram, and Custom sources use other protocols and do not depend on this proxy. If both FB and Google are down at the same time, those are different issues.

Chatterfy does not provide the proxy — it is an external service. Any residential or datacenter proxy provider will work. The main thing is that it consistently provides low latency (< 1 sec to graph.facebook.com) and is not blocked by Facebook itself. If your team does not have its own provider, @chatterfy_support can recommend trusted ones.


Related

Error: fbclid is empty in source logs
This error appears in next to Facebook source events. The message fbclid is empty means that Tracker detected a link click, but the fbclid parameter was missing from the URL or was empty . Without fbc
Proxy — proxy for S2S
The Tracker → Proxy section is a directory of HTTP/HTTPS proxy servers through which Tracker sends outgoing S2S requests to advertising platforms (Facebook Conversions API, Google, etc.). Without a pr
Facebook — Source with Meta Pixel
A Source with Provider = Facebook is needed when you drive traffic from Meta Ads (Facebook, Instagram). Tracker links your campaign events to the Facebook pixel and sends conversions back through the
Logs — event logs
Open Tracker → Logs. In the upper part of the page, four logs are available: postback sends, source events, S2S requests, and the Tracker object change history. To search for a single chain, use the s

Was this article helpful?

BackError: fbclid is empty in source logs

On this page

  • Why this happens
  • What to do
  • Frequently asked questions
  • Related