Tracker Errors
Errors in Tracker appear in — the service log that records everything Tracker does from the click through to recording the postback from the affiliate network. Most messages are informational (“lead w
Errors in
Tracker appear in Logs — event logs— the service log that records everything Tracker does from the click through to recording the postback from the affiliate network. Most messages are informational (“lead without fbclid”, “organic”, “proxy re-requested token”); some are critical (“postback did not arrive”, “proxy unavailable”, “Conversions API returned 401”). The errors that made it into this section are the most common ones and usually either require a single fix or a one-time understanding of the architecture (how a click is linked to a lead and the affiliate network).If the error repeats not in
Tracker, but inside the bot conversation (Telegram returns an HTTP code), see Telegram Errors— it covers codes 400 and 403. If the symptom is about the product itself (the bot “hangs”, AI “glitches”, leads disappeared somewhere) — Frequently Asked Questions. This section includes only what Tracker itself recorded in the source / postback / integration logs.Check the logs first
Before looking for a solution, open Logs — event logsand check the exact error text + time. The text identifies the problem type:
fbclid is empty — organic, post graph.facebook.com — proxy / Conversions API, postback timeout — the affiliate network is not responding, domain not found — Cloudflare has not picked up the changes yet. Tracker logs are stored for the last few days. For investigations like “something strange happened yesterday”, it is important to check them in time. Anything you did not save in a screenshot or copy is lost.What is covered
The two most common errors. Click the card you need or read the short description below:
— Error: fbclid is empty in source logs— the transition to
Telegram happened without the fbclid parameter (Facebook Click ID). Most often this happens because of a manual link test or a direct visit without ad delivery. By default, Chatterfy ignores such leads as “organic” — this protects against spam and tests, but sometimes it also filters out a real lead. The article explains how to allow this and how to tell a real lead from a test one.— Error: Post graph.facebook.com in source logs—
Tracker could not send the event to Facebook Conversions API. The problem is almost always with the proxy: either it is not in Proxy — proxy for S2S, or it is not working (blocked, token expired, IP ended up on a blocklist). The article explains how to check the proxy status, how to replace it, and how to prevent this from happening again.What this section does NOT cover
If the symptom is from the list below, it belongs in another subcategory or in the reference section, because it is not strictly a “
Tracker error”:— The postback does not arrive from the affiliate network — diagnostics are done through How event forwarding works(what should happen) and Logs — event logs(what actually happens).
— Contact / FD events are not linked to leads — this is a clickid issue in the registration link; see Why conversations and events are not tracked — only Subscribe.
— The campaign does not see the bot channel — this is about the bot’s permissions in the channel; see Channel not visible when creating a channel campaign — how to fix it?.
— SSL / domain does not work — diagnose it through How to Set Up SSL(Cloudflare Flexible mode, waiting for Active).
—Landing page does not open— Landings — Telegram redirect landing pages(creation /
Default / Custom — by landing page type).General questions about Tracker errors
Expand the item you need. For specific errors, click the cards above.
Articles in this section
Related
Was this article helpful?