Conversion Tracking & Data

Google Tag vs Offline Conversion Import

In short: Both feed conversions into Google Ads so bidding can learn from them, but they report entirely different moments. The Google tag reports what happens on your website, live, automatically. Offline Conversion Import reports what happens after the click leaves your website - a signed contract, a phone sale - manually or on a schedule, tied back to the gclid the Google tag captured at click time. Every site needs the Google tag as the baseline; add offline import only when the real outcome happens somewhere the tag can never see, after the click.

By the AdFlint research team · Fact-checked against current Google and Meta platform behavior · Last reviewed July 2026

Google Tag

A single site-wide snippet, gtag.js, that collects measurement data and routes it to Google Ads and Analytics destinations.

One tag on every page handles page views, conversions, and the linker that preserves the gclid in a first-party cookie, then distributes data to whichever destination IDs you configure. It is the simplest correct install for a site without a tag manager. The usual failure is leaving legacy conversion snippets in place next to it, which produces duplicate conversions, or omitting the tag from the actual confirmation page.

Full definition

Offline Conversion Import

Uploads conversions that happened outside the website, such as a signed contract or a phone sale, back to the ad platform.

You store the click identifier, gclid for Google or the lead's hashed details, capture the outcome in your CRM, then upload conversion time and value so bidding learns which clicks produced revenue. It is essential for anything with a sales cycle. Uploads fail most often on window and timezone problems: a conversion recorded after the click-through window closes, or timestamps submitted in the wrong account timezone, is discarded.

Full definition

Side by side.

The differences that actually change what happens in your account.

 Google TagOffline Conversion Import
When it firesLive, inside the browser session.After the fact, on whatever cadence your CRM export runs.
What it needs to have already happenedNothing - it's the first thing that has to exist.A click that generated a gclid the Google tag already captured and preserved.
AutomationFully automatic once installed.Manual or scheduled, driven by your CRM's export process.
Data sourceBrowser events - page views, form submissions, on-site conversions.CRM records - outcome, timestamp, and the click identifier.
What breaks itA legacy snippet left in place next to it, or the tag missing from the confirmation page.A conversion recorded after the window closes, or a timestamp submitted in the wrong timezone.
Dependency directionIndependent - needs nothing downstream to function.Depends entirely on the Google tag having captured the gclid first.

What actually separates them.

01

The Google tag fires live, inside the browser session; offline conversion import happens after the fact, on whatever cadence your CRM export runs.

02

Offline conversion import cannot function without the Google tag first capturing and preserving the gclid at the original click - it depends on the tag, not the other way around.

03

The Google tag reports website behavior like page views and on-site conversions; offline import reports outcomes that happen entirely off the website, in a sales call or a signed document.

04

A missing or misfiring Google tag means no conversion tracking at all; a missing offline upload just means bidding never learns which clicks turned into revenue, on-site counting still works.

05

Offline uploads are time-boxed to the conversion window and sensitive to timezone; the Google tag has no such window, it simply reports the moment the event happens.

Which one should you use?

Use Google Tag when

  • You're setting up conversion tracking on a new site or funnel for the first time.
  • You need page views, remarketing lists, or any on-site conversion to work at all.
  • Every meaningful conversion happens entirely on your website.
  • You're debugging why nothing is tracking, before touching anything downstream.

Use Offline Conversion Import when

  • Your product has a sales cycle - a quote, a call, a signed contract after the click.
  • Website conversions like form fills or calls started are only a proxy, not the real outcome.
  • You want Smart Bidding optimizing toward actual revenue or won deals.
  • You have a CRM that can export outcome, timestamp, and the original click identifier.

Common questions.

Do I need the Google tag if I'm only using offline conversion import?

Yes, offline import needs a gclid to attach the later outcome to, and the Google tag is what captures and preserves that gclid at the moment of the click. Without it, there's no click identifier for the upload to reconnect to.

My offline upload didn't show up in the account. Why?

Check the conversion window - was the outcome recorded after it closed - and the timezone the timestamp was submitted in. Both are the most common reasons an upload gets silently discarded rather than posted.

Can offline conversion import replace the Google tag?

No, they report different things. The tag reports on-site behavior in real time, offline import reports outcomes that happen later and elsewhere, and most accounts with a sales cycle need both running together.

Or stop choosing between them.

AdFlint picks the setting, writes the ads, and keeps optimizing inside the Google and Meta accounts you already own.

Related comparisons

All comparisons