What each error means, whether it is something you can fix or something that fixes itself, and exactly what to do about it.
Most conversions go through without anyone looking. This is the page for the ones that don't.
Worth knowing
Converly distinguishes a conversion that failed from one that was deliberately not sent. Both are visible, and confusing the two is the usual reason people think tracking is broken when it is working correctly.
Where to find the error
Open the conversion log, click the conversion, then click the destination that didn't work. The error sits at the top of that panel in plain language, with a suggested next step underneath it.
The platform's own raw error text is tucked behind a "Show technical details" toggle. You rarely need it, but it is the thing a platform's support team will ask for.
Errors you fix by reconnecting
These all mean the same thing. The credential Converly uses to talk to that platform no longer works, usually because it was revoked, regenerated or expired. Conversions will keep failing until you reconnect, and the ones that failed in the meantime are not re-sent automatically.
| Destination | What went wrong | What to do |
|---|---|---|
| Google Ads | Google rejected the sign in, or the connection is missing a permission Google now requires for conversion uploads. | Reconnect Google Ads from Connected Accounts and approve every permission on Google's consent screen. |
| Meta | The access token for your pixel expired or was revoked. | Reconnect Meta, or generate a new System User access token in Meta Business Manager and paste it in. |
| The token was revoked or regenerated in Campaign Manager, or the connection reached its 12 month expiry. | Generate a fresh Conversions API token in Campaign Manager under Analyze, then Signals Manager, then Direct API. Then reconnect LinkedIn. | |
| TikTok | The access token was deleted or regenerated in Events Manager, or the connected TikTok account lost access to the ad account. | Generate a fresh Events API token in Events Manager, or reconnect with an account that can manage that ad account. |
| The authorisation was revoked. | Reconnect your Reddit Ads account. | |
| ChatGPT Ads | The Conversions API key was deleted or regenerated. | Reconnect ChatGPT Ads. |
Errors you fix in your ad platform
These mean the connection is fine but something in the ad account itself is blocking the conversion. Nothing in Converly will fix them.
| Destination | What went wrong | What to do |
|---|---|---|
| Google Ads | Google declined permission for this account. | Usually one of two things. Either the account has not accepted Google's Customer Data Terms, which an admin can do under Data manager, or the connected Google user needs Standard access or higher. Check the terms first. |
| Google Ads | Enhanced conversions are switched off, so conversions carrying customer details can't be recorded. | In Google Ads open Goals, then Conversions, then Settings, turn on enhanced conversions and accept the terms. Conversions matched by click ID alone still record while this is off. |
| Google Ads | The conversion action this flow sends to no longer exists. | Check it still exists in Google Ads, then edit the flow and reselect it. |
| GA4 | The property has not accepted Google's User Data Collection terms. | In GA4 open Admin, then Data Streams, then your stream, and accept the User Data Collection Acknowledgement. |
| GA4 | The connected Google account only has Viewer access. | Ask your GA4 admin for Editor access, or reconnect with an account that already has it. |
| The conversion rule is disabled, deleted, or belongs to a different ad account than the token. | Check the rule in Campaign Manager under Measurement, then Conversion tracking, and update the rule in your flow if it changed. | |
| TikTok | The pixel code in your TikTok connection doesn't match the pixel the token was generated in. | Reconnect TikTok making sure the pixel code matches. |
| The pixel was deleted, or the connected account lost access to it. | Reconnect and pick a current pixel. | |
| ChatGPT Ads | The pixel or data source was removed in Ads Manager. | Reconnect ChatGPT Ads to pick a current one. |
Errors you fix in your flow
These mean the conversion itself is configured in a way the platform won't accept. They are all fixed by editing the flow and publishing it again.
| Destination | What went wrong | What to do |
|---|---|---|
| Google Ads | The Google Ads connection changed after the conversion action was chosen, so the flow is pointing at something that no longer lines up. | Open the flow, reselect the conversion action, and republish. |
| The flow's conversion rule isn't tied to an ad account, or is tied to a different one than the account now connected. | Open the flow, reselect the LinkedIn conversion rules, and republish. | |
| TikTok | The event name isn't valid for TikTok. | Edit the TikTok destination and use letters, numbers, underscores and hyphens only, starting with a letter, up to 50 characters. |
| ChatGPT Ads | The conversion type isn't one ChatGPT Ads accepts. | Edit the ChatGPT Ads destination, pick a supported conversion type, and republish. |
Errors that resolve themselves
You don't need to do anything with these. The platform was temporarily unavailable or throttling us, Converly retried automatically, and new conversions go through as normal. They are worth recognising so you don't go looking for a problem that isn't there.
| Destination | What went wrong | What to do |
|---|---|---|
| Any platform | The platform is rate limiting conversion uploads right now. | Nothing. Rate limits usually clear within minutes. If you see this constantly, tell us. |
| Google Ads, ChatGPT Ads | The platform's own service had a temporary problem. | Nothing, unless it keeps happening. |
| TikTok | TikTok was reconnected while this conversion was being sent. | Nothing. It is retried against the new connection. |
Conversions that were never eligible
These are not failures in the normal sense. The conversion was real, but that particular platform could never have accepted it. The most common cause by far is the first row.
| Destination | What went wrong | What to do |
|---|---|---|
| LinkedIn, TikTok, ChatGPT Ads | The submission carried nothing the platform can match a person with. | Make sure your form collects an email address, and a phone number where the platform accepts one. Visitors who arrived by clicking an ad on that platform can also be matched by the click identifier it left behind. |
| The conversion's timestamp was more than 90 days old. | Nothing, unless you were deliberately replaying old conversions. New ones are unaffected. | |
| ChatGPT Ads | The conversion was more than 7 days old. | Usually means it sat waiting on data from another tool. Newer conversions are unaffected. |
| TikTok, ChatGPT Ads | No page URL was available, and both platforms require one on every web conversion. | Nothing in normal use. This only affects conversions recorded outside an ordinary page visit. |
For the full set of platform age limits, see How delivery works.
Problems at our end
Some errors are ours. Converly says so rather than dressing them up as something you configured wrongly, and these are reported to us automatically.
| Destination | What went wrong | What to do |
|---|---|---|
| Any platform | The platform rejected the conversion as invalid, which usually means Converly formatted something incorrectly. | Nothing you can fix. Contact us with the conversion's event ID and we'll look at it. |
| Google Ads | A configuration issue on our side is temporarily blocking uploads. | Contact us. This is not something to fix in your account. |
| ChatGPT Ads | OpenAI's network blocked the request before it reached their conversion API. | Nothing. Not a problem with your account or your key. |
When a conversion was never counted at all
Everything above is about a conversion that exists and failed to reach one destination. Separately, a conversion can fail to be counted in the first place, usually because Converly could not confirm with the source tool that the submission or booking actually happened.
These appear as a notice on the conversion rather than as a per-destination error, because the problem affects the whole thing rather than one platform.
| What went wrong | What to do |
|---|---|
| The connection to your form or scheduling tool expired, was revoked, or lost a permission it needs. | Reconnect that tool from your dashboard. Until you do, conversions from it are either not counted or counted with much weaker matching. |
| The booking was cancelled or declined. | Nothing. Converly deliberately does not count a booking that did not go ahead. |
| The tool never made the submission or booking readable, even after repeated attempts. | Nothing immediately. If it keeps happening on the same tool, tell us. |
| The submission didn't match the filter set on the flow. | Nothing. This is the filter working. These are hidden from the conversion log by default. |
| The filter couldn't be evaluated, usually because the connection it depends on is gone. | Reconnect the tool the filter depends on. |
| Your Acuity plan doesn't include API access. | Converly falls back to what it can read from the page, which matches less well. Upgrading your Acuity plan restores full matching. |
| The visitor's browser data never reached us, so the conversion was sent with the email address alone. | Check the Converly script is installed on every page where the booking widget or form can be reached. Matching will be weaker for these. |