Best Practices

The Ultimate Guide to Google Ads Offline Conversion Tracking

Nate Corliss
Nate Corliss February 23, 2023

Nate manages ads for Census. He’s a growth marketer with over a decade of experience. When he’s not optimizing ads, you’ll find him on his SUP or strolling through the woods with his family.

Ask your marketing team (or yourself, if you’re on the marketing team) this simple question: “How do you send offline conversions?”

If the answer is either, "We don’t" or “Via manual CSV uploads," then you have both a data security issue and an ads optimization issue. 😬

With third-party cookies sunsetting, ad blockers, and privacy-centric browsers like Brave, marketers are finding it more difficult than ever to measure campaigns AND critically send conversion data back to ad platforms for ads optimization around conversion actions. 

In this attribution guide, we’ll show you how to set up Google offline conversions, a vital method to track and measure advertising efforts. Of course, Google offline conversions offer a semi-permanent fix for this tracking effort – there’s no guarantee they’ll be here forever, but my bottom dollar is we’ve got at least five years – but this is 🔑 to advertisers’ success in circumstances where it may be (extra) challenging to get attribution. 

Note: This guide can serve as a template for sending offline conversions to Meta Ads, Twitter Ads, TikTok Ads, Reddit Ads, Microsoft Ads, GA4, LinkedIn Ads, and a variety of programmatic platforms like The Trade Desk, but we’ll start with using first-party data for Google Ads attribution via offline conversions.
A significant benefit of properly configured Google Ads attribution via offline conversions is that you can stop serving ads to users who have completed a conversion action (e.g. made a purchase or filled out a form).

How do offline conversions work?

With offline conversions, advertisers can send conversion data to Google Ads, allowing them to see a complete picture of the impact their advertising is having on their business. This data can also be used to optimize their campaigns by identifying which keywords, ad placements, and targeting strategies are driving the most valuable offline actions.

Putting this 👆 all together: Offline conversions build audiences (e.g., everybody who did the conversion action). Depending on where these users land in the conversion funnel, they can be used for remarketing or ad exclusions. And with offline conversion-based audiences, you can ensure you’re not annoying users with ads after they make a purchase. 🤪

The superpower of using first-party data for offline conversions is that you can blend different data entities. 🦸 Imagine this B2B use case: 

  • You want to combine business intelligence data like a user “score” with conversion data like a form submission. 


  • You could combine these two 👆to make a high-quality offline conversion to send to Google. 

Traditionally, a marketer would only capture the form submission, missing the critical quality association needed for better B2B ads optimization. But when they’re armed with the ability to track and measure offline conversions, advertisers can make more informed decisions about how to allocate their advertising budgets and improve the overall ROI of their online advertising efforts.

Building the measurement and attribution dream team 🤩

With third-party cookies sunsetting and ad blockers being built into devices (looking at you, iOS 14 and later 👀), gone are the days when a semi-technical marketer could set up conversions via Google Tag Manager or simple code placement on a site/in an app. Instead, first-party data sent as offline conversions is the best path to Google Ads attribution. 

Keep in mind: First-party data spans different teams, so you’ll most likely need measurement champions from the following teams 👇

  • Marketing & Advertising. As the owner of Google Ads, this team is critical in defining, requesting, and testing conversion events. 
  • Web. Your website developer will likely play a role in capturing things like the GCLID and ensuring it’s passed along to relevant destinations. 
  • Product. Your product manager knows your product's onboarding process like the back of their hand. ✋ This person will help you identify the most important conversion points on the onboarding journey. 
  • RevOps. This team can give you real financial data on how much a conversion is worth if you’re not in e-commerce. Note that this number may need to be estimated. 
  • Data & Analytics. You’ve got an analytics owner, right? Like product, they should be able to provide conversion data and – more crucially – conversion rates between different steps in the funnel, which may all have their own conversion value (e.g. views product, adds a product to cart, views cart, views billing page, checks out).
  • Engineering. Should you have a product, engineering may need to help with implementation. Most likely, your product manager can facilitate this, but getting engineering in on conversion tracking early will certainly make the final implementation not fall into the “square peg round hole” dilemma. You want to do attribution right and have the tracking last. 
  • Project Management. This effort might be a major undertaking, and in that case, a good project manager is worth their weight in gold. Acting as a translator and resource allocator among different teams, the buck stops with the product manager. Be sure to treat them with kindness and empathy. Wrangling so many disparate teams is hard work! 

Once you have your dream team assembled, you can start sending Google Ads Attribution as offline conversions from your data warehouse (Snowflake, BigQuery, PostGres, Redshift, MySQL, etc.) to Google Ads. Note that this method only works if you have a data warehouse, but if not, you can also use Google Sheets in a pinch. 🤏

Of course, like everything in life, there’s the traditional (but difficult) way to do this — or you can take the new, easy-breezy approach. 😏

The traditional (but hard) way to set up Google Offline Conversions via the Google Conversion API 

Setting up Google offline conversions with a conversion API involves a few steps and requires some technical expertise. Here’s a general overview of the process, but we’ll leave the nitty-gritty technical write-up of this to Google

  1. Prepare your data. You'll need to have a way to collect data about offline conversions and store it in a format that can be uploaded to Google Ads. This may involve setting up a CRM system, creating a custom spreadsheet, or using a third-party integration.
  2. Set up conversion tracking. To upload offline conversion data, you first need to have conversion tracking set up in Google Ads. This involves creating a conversion action for the type of conversion you want to track, such as a phone call or in-store purchase.
  3. Create an offline conversion upload file. Once you have your offline conversion data ready, you'll need to create a file that can be uploaded to Google Ads. This involves formatting your data into a specific structure and including certain required fields, such as the conversion date and value.
  4. Upload your data. Once your file is ready, upload it to Google Ads through the Offline Conversions section of the Conversion Actions page.
  5. Verify and monitor your conversions. After you've uploaded your data, you'll need to verify that it was processed correctly and monitor your offline conversion data in Google Ads to ensure it's accurate and up-to-date.

Again, this is just a speed run of the process, and the exact steps may vary depending on your specific situation and the tools you're using. You may also need to work with a developer or technical expert to set up and implement offline conversion tracking correctly.

The easy way to set up Google offline conversions with first-party data from your data warehouse (in just four steps)

Now, if you want to make life difficult for yourself and go it the hard way, more power to you. The folks at Census, on the other hand, created a quick, streamlined approach to achieve the same results. Just follow the steps in the example below to start sending offline conversions from Snowflake to Google Ads. 👇

  1. Great a free Census Account (Census is a data activation platform with a ready-made connection from your data warehouse to Google Ads, you can create and send a basic set of offline conversions on the free plan).
  2. Connect your data warehouse to Census. 
  3. Connect your Google Ads account to Census.  
  4. Send your offline conversions, so you finally have Google Ads attribution! 
  5. If you’re reading this as a marketer or data person, you know these “events” don’t define themselves. Ensure you’ve determined what offline conversion(s) you want to send. 
  6. For additional guidance and technical details, hop over to Census docs - Google Offline Conversions, or schedule a demo with a product expert, and they’ll run you through the setup. 

Or if you’d rather watch a step-by-step visual guide on how to send your offline conversions from Snowflake to Google Ads, check out this video.👇

‎The future of Google attribution 

No matter how you slice and dice it, offline conversions are the future of Google Ads Attribution. 🔮 You could, of course, throw up your hands and ignore attribution and hope for the best. But this would take you back to the days before Claude Hopkins introduced Scientific Advertising in 1923, which included strategies for attribution around putting unique coupons on different marketing assets. 

You don’t actually want to follow this, trust us.

Without offline conversion data, you’re giving up on the promise of machine learning and ads conversions optimization that is getting more and more reliable on Google Ads. And now that you’re armed with the tools to set up Google Ads offline conversions, be sure to pay it forward and tell your friends and colleagues. 

✨ Have feedback on this article, or want a personalized data activation strategy session? Schedule a jam session with a Census data activation expert. We’ll show you just how easy it can be to combine different data entities into single conversion events.

Related articles

Customer Stories
Built With Census Embedded: Labelbox Becomes Data Warehouse-Native
Built With Census Embedded: Labelbox Becomes Data Warehouse-Native

Every business’s best source of truth is in their cloud data warehouse. If you’re a SaaS provider, your customer’s best data is in their cloud data warehouse, too.

Best Practices
Keeping Data Private with the Composable CDP
Keeping Data Private with the Composable CDP

One of the benefits of composing your Customer Data Platform on your data warehouse is enforcing and maintaining strong controls over how, where, and to whom your data is exposed.

Product News
Sync data 100x faster on Snowflake with Census Live Syncs
Sync data 100x faster on Snowflake with Census Live Syncs

For years, working with high-quality data in real time was an elusive goal for data teams. Two hurdles blocked real-time data activation on Snowflake from becoming a reality: Lack of low-latency data flows and transformation pipelines The compute cost of running queries at high frequency in order to provide real-time insights Today, we’re solving both of those challenges by partnering with Snowflake to support our real-time Live Syncs, which can be 100 times faster and 100 times cheaper to operate than traditional Reverse ETL. You can create a Live Sync using any Snowflake table (including Dynamic Tables) as a source, and sync data to over 200 business tools within seconds. We’re proud to offer the fastest Reverse ETL platform on the planet, and the only one capable of real-time activation with Snowflake. 👉 Luke Ambrosetti discusses Live Sync architecture in-depth on Snowflake’s Medium blog here. Real-Time Composable CDP with Snowflake Developed alongside Snowflake’s product team, we’re excited to enable the fastest-ever data activation on Snowflake. Today marks a massive paradigm shift in how quickly companies can leverage their first-party data to stay ahead of their competition. In the past, businesses had to implement their real-time use cases outside their Data Cloud by building a separate fast path, through hosted custom infrastructure and event buses, or piles of if-this-then-that no-code hacks — all with painful limitations such as lack of scalability, data silos, and low adaptability. Census Live Syncs were born to tear down the latency barrier that previously prevented companies from centralizing these integrations with all of their others. Census Live Syncs and Snowflake now combine to offer real-time CDP capabilities without having to abandon the Data Cloud. This Composable CDP approach transforms the Data Cloud infrastructure that companies already have into an engine that drives business growth and revenue, delivering huge cost savings and data-driven decisions without complex engineering. Together we’re enabling marketing and business teams to interact with customers at the moment of intent, deliver the most personalized recommendations, and update AI models with the freshest insights. Doing the Math: 100x Faster and 100x Cheaper There are two primary ways to use Census Live Syncs — through Snowflake Dynamic Tables, or directly through Snowflake Streams. Near real time: Dynamic Tables have a target lag of minimum 1 minute (as of March 2024). Real time: Live Syncs can operate off a Snowflake Stream directly to achieve true real-time activation in single-digit seconds. Using a real-world example, one of our customers was looking for real-time activation to personalize in-app content immediately. They replaced their previous hourly process with Census Live Syncs, achieving an end-to-end latency of <1 minute. They observed that Live Syncs are 144 times cheaper and 150 times faster than their previous Reverse ETL process. It’s rare to offer customers multiple orders of magnitude of improvement as part of a product release, but we did the math. Continuous Syncs (traditional Reverse ETL) Census Live Syncs Improvement Cost 24 hours = 24 Snowflake credits. 24 * $2 * 30 = $1440/month ⅙ of a credit per day. ⅙ * $2 * 30 = $10/month 144x Speed Transformation hourly job + 15 minutes for ETL = 75 minutes on average 30 seconds on average 150x Cost The previous method of lowest latency Reverse ETL, called Continuous Syncs, required a Snowflake compute platform to be live 24/7 in order to continuously detect changes. This was expensive and also wasteful for datasets that don’t change often. Assuming that one Snowflake credit is on average $2, traditional Reverse ETL costs 24 credits * $2 * 30 days = $1440 per month. Using Snowflake’s Streams to detect changes offers a huge saving in credits to detect changes, just 1/6th of a single credit in equivalent cost, lowering the cost to $10 per month. Speed Real-time activation also requires ETL and transformation workflows to be low latency. In this example, our customer needed real-time activation of an event that occurs 10 times per day. First, we reduced their ETL processing time to 1 second with our HTTP Request source. On the activation side, Live Syncs activate data with subsecond latency. 1 second HTTP Live Sync + 1 minute Dynamic Table refresh + 1 second Census Snowflake Live Sync = 1 minute end-to-end latency. This process can be even faster when using Live Syncs with a Snowflake Stream. For this customer, using Census Live Syncs on Snowflake was 144x cheaper and 150x faster than their previous Reverse ETL process How Live Syncs work It’s easy to set up a real-time workflow with Snowflake as a source in three steps: