What the offline conversion debugger checks

The offline conversion debugger runs 196 checks on an upload request before you send it, across six ad platforms. Every check runs in your browser, and each one shows its source: the platform’s own documentation, third-party documentation or what is seen in practice.

Google Ads (Data Manager API events:ingest)

  • Destinations: the account ID is the 10 digit Google Ads customer ID without hyphens, and productDestinationId is the conversion action ID.
  • eventTimestamp in RFC 3339 format with a time zone offset.
  • eventSource, which Google marks as required.
  • At least one identifier: a click ID (gclid, gbraid or wbraid) or hashed user data.
  • Hashing with SHA-256 and encoding as HEX or BASE64.
  • The currency code, and transactionId values that repeat inside the request.
  • The limits of 2,000 events and 10 destinations per request.

Google’s guide to sending offline events describes these fields. Google also fails every record in a request when any one record has an error, so a single bad event can stop a whole upload.

Meta Conversions API for offline events

  • event_time as a Unix timestamp in seconds.
  • The 7 day limit: if any event in the request is older than 7 days, Meta returns an error for the entire request and processes no events. For physical_store events, Meta says transactions should be uploaded within 62 days.
  • action_source, which Meta marks as required.
  • Hashed em and ph, with the phone number as digits only and no plus sign.
  • The fbc format.
  • event_id for deduplication.
  • value and currency on Purchase events.
  • The limit of 1,000 events per request.

The field rules come from Meta’s server event parameters reference.

TikTok Events API

  • event_source set to offline or crm, with its event set ID.
  • event_time in seconds.
  • Hashed email and phone, with the phone number in E.164 format including the plus sign.
  • lead_id on CRM events.

The TikTok checks are based on third-party documentation, not on TikTok’s own pages. Confirm any TikTok result with a test event in TikTok Events Manager before you rely on it.

Microsoft Advertising (UET Conversions API)

  • eventType set to pageLoad or custom, with eventName on custom events.
  • eventTime as a Unix timestamp in seconds, within the last 90 days.
  • eventId, and at least one user identifier.
  • Email and phone hashed with SHA-256, and msclkid as a 32 character ID without hyphens.
  • continueOnValidationError: while it is off, one invalid event stops the whole batch.
  • The limit of 1,000 events per batch.

Microsoft’s UET Conversions API guide describes these fields.

LinkedIn Conversions API

  • A conversion rule URN in conversion.
  • conversionHappenedAt, within the last 90 days.
  • eventId, and user IDs LinkedIn can match on, such as SHA256_EMAIL.
  • amount as a decimal string, with a 3 letter currencyCode.
  • The limit of 5,000 events per batch.

The batch limit and the 90 day window come from LinkedIn’s Conversions API FAQ.

Snapchat Conversions API

  • event_name as a Snapchat event name, with event_time and event_id.
  • action_source, with OFFLINE for offline sales.
  • At least one hashed email, phone or mobile ID on offline events.
  • value and currency on PURCHASE events.
  • Batches under 2,000 events.

Snapchat’s offline events guide describes these fields.

More tools in the offline conversion debugger

  • Explain an error: Google Data Manager API, old Google Ads API, Meta and Microsoft upload errors in plain words.
  • CSV file: checks Google Ads, Meta and TikTok upload files, repairs Excel damage, and hashes the email, phone and name columns in your browser.
  • CRM data: reads a webhook or records from HubSpot, Salesforce, GoHighLevel, Zoho, Pipedrive, Bitrix24 or another CRM and builds a hashed request for Google, Meta or TikTok.
  • Upload planner: match readiness, event age against each platform’s window, and splitting a request to the platform limit.
  • Missing conversions: a few questions that rank the likely reasons offline conversions do not show up.
  • Click IDs and time: checks click IDs from a URL or cookie, and click, conversion and upload times against each platform’s window.
  • Google migration: turns an old UploadClickConversions request or click conversions file into a Data Manager API request.
  • Compare platforms: the six platforms side by side, including how each wants email and phone written.
  • Fix, code and test: repair common problems, get the checked request as curl, Node.js, Python or PHP, or send it to Meta with a test_event_code to see it in Test Events.

Who it is for

The offline conversion debugger is for businesses and developers who send CRM, phone, WhatsApp or in-store sales to ad platforms, and for anyone moving Google offline imports to the Data Manager API. If you are planning that move, the post on Google Data Manager API offline import mistakes covers what to watch for. How sales from a CRM reach the ad platforms is explained in the offline conversion tracking bridge guide.

How to use the offline conversion debugger

  1. Paste the request body, a list of events or a curl command.
  2. Press Check request.
  3. Fix what it finds, or send the report for a fix plan.

The Hash customer data tool

Google, Meta and TikTok normalize customer data in different ways before hashing. Google removes dots and anything after a plus sign from Gmail addresses. Google and TikTok hash phone numbers in E.164 format with the plus sign, while Meta hashes the digits only. The Hash customer data tool applies each platform’s rules and hashes the result with SHA-256. Everything runs in the browser.

What it does not check

  • Chat events from WhatsApp, Messenger or Instagram that use action_source business_messaging. Check those in the CAPI Debugger.
  • Website pixel events.
  • Whether the platform received your events, or whether your click IDs are real. A clean result in the offline conversion debugger shows the request is well formed, not that it was accepted. For Meta, Send a test to Meta lets you see the request arrive in Test Events.

Privacy: requests are checked in your browser. Send a test to Meta sends the request from your browser straight to Meta, and the access token stays in the page only. A report is saved only when you create a share link or contact me from the tool. A saved report has IDs masked and personal data removed, and it is deleted after 30 days.

Frequently asked questions

Is it free?

Yes. The offline conversion debugger is free to use, and every check runs in your browser.

Does my data leave my browser?

Not while checking. If you use Send a test to Meta, the request goes from your browser straight to Meta and the access token is not saved. A report is saved only when you create a share link or contact me from the tool, with IDs masked and personal data removed, and it is deleted after 30 days.

Why does Meta reject my whole batch?

If any event_time in the request is more than 7 days in the past, Meta returns an error for the entire request and processes no events. Remove the older events and send the rest.

Why does Google say my timestamp is invalid?

eventTimestamp needs a date, a time and a time zone offset, as in Google’s example 2025-06-10T15:07:01-05:00. A timestamp without a time zone, or in another format, is flagged by the debugger.

Can I check TikTok offline events?

Yes, offline and CRM events. The TikTok checks are based on third-party documentation, so confirm the result with a test event in TikTok Events Manager.

About the author

Built by Al-Fahad Hridoy, an Attribution & Tracking Consultant who sets up Google Ads offline conversions, the Meta Conversions API and the TikTok Events API for businesses that close sales in a CRM, on the phone or on WhatsApp. Every check in the offline conversion debugger shows its source, so you can see whether it comes from platform documentation, third-party documentation or practice. Google Ads, Meta, TikTok, Microsoft Advertising, LinkedIn and Snapchat are trademarks of their respective owners. This is an independent tool and is not affiliated with or endorsed by any of them.

Privacy Policy