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: fbclid is empty in source logs

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

Updated August 30, 20263 min
This error appears in Logs — журналы событий 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 fbclid, Tracker cannot link the click to a specific ad impression — the event is recorded, but the source label remains “organic”.


Why this happens

fbclid is a click identifier that Facebook automatically adds to the link when a user clicks an ad. If fbclid is empty, it means the lead reached the link not through a Facebook ad. Possible reasons:
Testing the link manually — copying it from the browser or opening it directly without real ad delivery. This is the most common reason.
A direct visit via a saved link (bookmark, messenger, another channel that is not Facebook).
A browser or extension that strips UTM parameters and tracking (some “privacy” extensions).
An error in the setup of the ad itself in Facebook Ads Manager — the automatic appended parameter is disabled, or the link is built through a third-party shortener.


How to check

  1. 1

    Use Test inside the campaign

    Open your campaign in Campaigns — advertising campaigns and go to the Test tab (Test — checking a campaign before launch). This is a special mode that simulates an ad click with a valid fbclid — it lets you check the landing page → link → bot chain without real ad delivery.
  2. 2

    Check the link in Facebook itself

    In Ads Manager, open the ad and copy the Destination URL. Make sure it contains the {{fbclid}} parameter or automatic click ID substitution is enabled. If the link is built through a third-party API (Keitaro, Voluum, any external tracker), fbclid must be passed there as well.
  3. 3

    Ignore rare fbclid-empty events

    If only 1–3% of events in the overall traffic flow have fbclid empty, this is normal. Part of the audience reaches the bot via link sharing, comes from browser history, or uses privacy extensions. It makes sense to worry when every second event is fbclid empty.
What to consider “organic” traffic
Tracker records all visits without fbclid with the source organic (or empty). Postbacks from the affiliate network do not work for such leads — the FD/RD event will not be linked to the click, and the campaign will not get credit. If your affiliate network pays for actions, this is lost money.
To prevent this from happening again
Never test the link “by hand” in the browser by opening it directly — always use the Test section in the campaign. If you need to give a link to a colleague for checking, use the Test link; it is specially tagged and does not get into live statistics.


Frequently asked questions

The postbacks will arrive (the affiliate network will send the event by clickid), but Tracker will not be able to link it to the click. In analytics, you will see an FD event without a link to the campaign, without a buyer, and without a specific source. Financially, it will not be counted in the results of the traffic run.

This is a signal that something is wrong on the Facebook side or in the intermediate redirect. Check that: (1) the link in the ad contains ?fbclid={{fbclid}} or Facebook has enabled substitution automatically. (2) if you use cloaking or a bridge page, it forwards all query parameters to the final URL. (3) the landing page does not perform an additional redirect that loses fbclid.

There is no direct “do not let them through” option, but you can configure Auto Actions — auto actions based on postbacks — for example, don’t assign high priorities to such leads or run the main flow for them. You shouldn’t reject them completely: some organic traffic converts too.

No. If you paste the link into the browser’s address bar, fbclid will be empty — this is normal. This is exactly why manual testing is not allowed. Use Test — checking a campaign before launch — it will insert a real fbclid and go through the chain like a real ad.


Related

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
Test — checking a campaign before launch
The Test tab is a built-in simulation of a real user journey through a campaign link. It opens the landing page on your behalf, takes you through the entire path all the way to Telegram, and records e
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 — журналы событий
Откройте Tracker → Logs. В верхней части страницы доступны четыре журнала: отправка постбэков, события источников, S2S-запросы и история изменений объектов Tracker. Для поиска одной цепочки используйт

Was this article helpful?

BackTracker ErrorsNextError: Post graph.facebook.com in source logs

On this page

  • Why this happens
  • How to check
  • Frequently asked questions
  • Related