folder_open Analytics & Attribution

Signed-job uploads after Google's Data Manager API switch

Martin Marinov Martin Marinov
11 min read
Topics offline-conversionsgoogle-adsconversion-trackingdata-manager-apismart-bidding

If your CRM or a Zapier zap uploads won jobs to Google Ads, those uploads may have stopped reaching Smart Bidding without any warning. Since June 15, 2026, Google handles offline conversion imports and enhanced conversions for leads through its Data Manager API. A connector that never moved to the new path can keep “running” on your side while nothing useful lands on Google’s side.

That matters because your bidding learns from whatever data arrives. If signed jobs stop arriving, the only signal left is the form fill or the call. Google then shifts spend toward whoever fills out forms most cheaply, and those people are not always the ones who sign.

This post covers how to check which path your data manager api offline conversions use, how to confirm every lead carries the right identifiers, and how to catch a broken upload in the conversions diagnostics before your bids drift.

What the June switch changed for signed-job uploads

Before the switch, most tools sent offline conversions straight into Google Ads through the older upload methods. A CRM would mark a lead as “won,” find the click ID saved with that lead, and push a conversion back to the matching campaign.

The idea has not changed. You still send Google a record that says “this click turned into a signed job, worth this much, on this date.” What changed is the route that record has to take. Offline conversion imports and enhanced conversions for leads now go through the Data Manager API, so any software doing the uploading for you has to be built for it.

The risk for a contractor is not that tracking breaks loudly. The risk is that it breaks quietly. Your CRM still shows “sent.” Your zap history may still show green checkmarks. Meanwhile Google Ads stops counting new signed jobs, and you only find out weeks later when lead quality slips.

Find out which path your won-job uploads use

Start by listing every tool that sends conversions to Google Ads on your behalf. For most offline conversion import contractors set up, that list is short:

  • Your CRM’s built-in Google Ads connection (job management and field service software often has one)
  • A Zapier, Make or similar automation that fires when a deal or job changes status
  • A call tracking platform that sends qualified calls back to Google Ads
  • A spreadsheet someone uploads by hand, or a scheduled upload from Google Sheets

For each one, ask a direct question: “Does this send conversions through Google’s Data Manager API, and when did you update it?” Ask your software vendor’s support team, or check their help center and changelog. If the answer is vague, treat it as a no until you see proof inside Google Ads.

Manual and scheduled file uploads live inside Google Ads itself, so check those against the upload history there rather than assuming they are fine. Zaps are the ones we see go stale most often. A zap built years ago by someone who no longer works with you can keep firing on an old action that the app has since replaced. Open the zap, look at the Google Ads step, and see whether the app is flagging that action as outdated or asking you to reconnect.

If you run more than one of these, also check that two tools are not sending the same signed job. Doubled conversions make jobs look cheaper to win than they are, and bids get pushed up for the wrong reasons.

Data manager API offline conversions need two things on every lead

The new path does not fix bad data. An upload only helps if Google can match it to an ad click. That match comes from two kinds of identifiers, and you want both on every lead.

The click ID

When someone clicks your ad, Google adds a click ID to the landing page address. On most devices that is the GCLID. On some Apple devices you may see GBRAID or WBRAID instead. Your website form has to read that value and save it with the lead in your CRM.

Common ways it gets lost:

  • The form plugin does not have a hidden field for it, so it is never captured
  • A redirect between the ad and your page strips the parameter. Run your landing page URLs through our redirect chain checker to see every hop
  • The visitor browses two or three pages before filling out the form, and the click ID is not stored in a cookie to carry it along
  • Phone leads come in with no click ID at all because nobody set up call tracking that ties the call back to the ad

The hashed phone number or email

This is what enhanced conversions for leads data manager uploads rely on. Your site or CRM captures the customer’s email or phone number, normalizes it, and hashes it with SHA-256 before it goes to Google. Google can then match the record to a signed-in Google user even when the click ID is missing.

Normalizing matters. Phone numbers should be in full international format with the country code. Emails should be lowercase with extra spaces trimmed. Sloppy formatting means the hash will not match, and the upload counts for nothing even though it technically “succeeded.”

Having both identifiers gives you a backup. If a redirect drops the GCLID on one lead, the hashed email or phone can still connect that signed job to the right campaign.

Read the conversions diagnostics before bids drift

Google Ads shows you whether your uploads are working. You just have to look. Open the conversion action you use for signed jobs from the conversions section under Goals. Inside it you will find diagnostics for offline imports and for enhanced conversions for leads, plus a history of recent uploads.

Here is what to look for:

  • When the last upload arrived. If your business signs jobs every week but the history shows nothing recent, uploads have stopped.
  • Rows that were not imported. Google lists rows it rejected and why, such as an unknown click ID, a click too old to count, or a conversion action that does not exist.
  • Match quality for enhanced conversions. If the share of matched records is weak or falling, your phone and email formatting is probably off, or the data is not being sent at all.
  • The status of the conversion action itself. A warning that the action has had no recent conversions is often the first sign of a silent break.

Then compare against your CRM. Say your team marked several jobs as won last week. Count them, then count what Google Ads recorded for the same dates. Some gap is normal, because not every customer clicked an ad. But if your CRM shows steady wins and Google shows nothing, the pipe is broken.

The cost of missing this shows up slowly. If your campaign bids toward signed jobs or job value and those conversions dry up, Smart Bidding falls back on whatever you are still counting. Usually that is form submissions. You will see more leads at a lower cost per lead and feel good for a week or two. Then the office notices more tire-kickers, more people outside your service area, and fewer booked estimates.

A one-hour check for your office manager or web person

Hand this list to whoever looks after your website and CRM. Most of it can be done in one sitting.

  1. List every tool that sends conversions to Google Ads, including CRMs, zaps, call tracking and manual uploads.
  2. Ask each vendor in writing whether their connection uses the Data Manager API, and save the reply.
  3. Open each zap that touches Google Ads, confirm it is on the current Google Ads action, and reconnect the account if prompted.
  4. Click one of your own ads in a private browser window, fill out the form with a test name, and confirm the GCLID shows up on that lead in your CRM.
  5. Check that the same test lead has the email and phone number saved in clean, consistent formats.
  6. Mark the test lead as won in your CRM and confirm the upload fires. Then look in Google Ads after a day to see whether it arrived or was rejected, and delete or adjust the test so it does not count as a real sale.
  7. Open the diagnostics for your signed-job conversion action and write down the date of the last successful upload and any error reasons listed.
  8. Compare last month’s won jobs in the CRM with the signed-job conversions in Google Ads for the same period.
  9. Set a recurring reminder to repeat steps 7 and 8 every couple of weeks.

If step 4 fails, fix the form before anything else. No upload method can help a lead that never had a click ID or contact details saved. Our conversion tracking setup work usually starts right there.

When to fix it yourself and when to hand it off

Some fixes are small. Reconnecting a zap, adding a hidden GCLID field to a form, or cleaning up phone number formatting in your CRM are jobs a capable web person can handle.

Other situations call for a deeper rebuild:

  • Your CRM vendor has no Data Manager API support and no plan to add it
  • Leads arrive from several sources (website, calls, quote tools, chat) and none of them share a lead ID
  • You want Google to bid on job value, not just a count of signed jobs, which means sending revenue with each upload
  • You have been running on broken data for months and need to decide whether to reset bidding targets

In those cases, the job is to rebuild the path from ad click to signed contract, then confirm every link works. That is what our offline conversion tracking service covers: capturing click IDs and hashed contact data, connecting your CRM through the current API, and setting up checks so a silent failure gets caught early.

Frequently asked questions

My CRM says the conversion was sent. Why would Google Ads not have it?

“Sent” only means your CRM tried. If the connection uses an outdated method, or the click ID is missing, or the phone and email do not match a Google user, Google can reject the record or never receive it. The upload history inside Google Ads is the only place that tells you what actually arrived.

How can I upload signed jobs to Google Ads if a customer called instead of filling out a form?

You need call tracking that ties each call back to the ad click, or you need to capture the caller’s phone number and email in your CRM so enhanced conversions for leads can match it. Without one of those, a phone-only job has nothing for Google to connect it to.

Should I switch my campaigns off signed-job bidding until uploads are fixed?

Not always. If the break is recent and you can fix it within days, keep your settings and repair the pipe. If uploads have been missing for a long stretch, bidding has already adjusted to bad data, and it is worth reviewing your targets once the conversions start flowing again.

Do I need both the GCLID and the hashed email or phone?

You need at least one to match, but having both is safer. Click IDs get dropped by redirects and multi-page visits, and contact details get mistyped. With both, one usually covers for the other.

How long after a job is signed should the upload happen?

As soon as the job is marked won in your CRM. Google only accepts conversions within a limited window after the click, and long sales cycles can push you close to it. Uploading quickly also gives Smart Bidding fresher signals.

Can a zap built before June 2026 still work?

Only if the app it uses was updated for the Data Manager API and the zap uses the current action. Open it, check the Google Ads step, and confirm with a test lead rather than assuming.

Your next step

This week, open the diagnostics for your signed-job conversion action in Google Ads and write down the date of the last successful upload. If it is older than your most recent won job, your uploads are broken. If you want us to trace where it fails and rebuild the path, Call us+1 (415) 420-4059 or start with our free marketing audit.