Brand promotion: this article introduces Guangsuan's Google Ads management service. It is a vendor introduction, not an independent review or a commissioned evaluation.
Revenue operations and attribution teams at B2B SaaS companies run into the same argument: the Google Ads report counts conversions, the CRM counts leads that sales accepted, and the board counts closed revenue. Offline conversion import is the standard way to send the later stages back to the ad platform so that bidding can use more than a form submission. What goes wrong is rarely the upload itself. It is that the three counts were never defined against each other before anything was sent.
This article answers one question: before a B2B SaaS team imports offline conversions into Google Ads, what should it check first? It closes with where Guangsuan's Google Ads management service fits, because this work sits inside that scope. Nothing here is a commitment about your results, and no provider can promise a specific inquiry volume or close rate.
The short answer
Write one definition of a qualified lead, confirm that the identifier linking a CRM record to an ad click survives from the landing page into the CRM, and record the event's real occurrence time rather than the upload date. Then import only events your sales team already accepts under that written definition. If the definition changes later, change it deliberately and note the date, because mixing two definitions inside one reporting period makes the comparison unreliable.
Four different counts, one argument
Keep these events separate, because each answers a different question:
- Clicks record that someone reached your site from an ad.
- Conversions are the actions the ad account was configured and able to record, such as a form submission. Only conversion actions marked as primary roll into the Conversions column and into bidding; secondary actions are reported separately and should be labelled as such when you export.
- Qualified leads are a sales judgement that a written condition has been met.
- Closed deals are a business outcome recorded in your own systems.
Guangsuan's published position is that clicks, conversions, qualified inquiries and closed deals should be read as separate figures rather than combined into a single performance number. That is also why the import exists: to move the last two events into an account that only saw the first two.
Step 1: write one definition of a qualified lead
The definition has to be usable by someone who did not write it. A status table that names the entry condition, the person who decides, and the timestamp to record is enough to start:
| Status | Entry condition | Recorded by | Timestamp used |
|---|---|---|---|
| Submitted | The form reached your system and was stored | Marketing or web operations | Form submission time |
| Contactable | Contact details are complete and a reply is possible | Sales development | First response time |
| Qualified | The written product, market and purchase conditions are met | The named decision owner | Time the condition was met |
| Not a fit | Confirmed spam, a job application, or a product you do not supply | The same decision owner | Time the exclusion was confirmed |
| Business outcome | A quotation, contract or payment step agreed in advance | Sales operations or finance | Time the business step occurred |
Two things follow from writing it down. First, qualified leads and converted leads stop being the same word: a converted lead is a step your company defined, and it does not automatically mean a paid customer. Second, the timestamp column decides what a month means, so agree it before anyone pulls a report.
Step 2: verify the fields before the first upload
The upload can only match what it is given. Check these five things on a real record that passed through the whole path, not on a test entry created in the CRM:
- The click identifier. This is the value Google Ads uses to connect a click to a later event. Verify that it is captured on the landing page, stored with the form submission, and carried into the CRM record rather than left behind in analytics. If older leads have no identifier, they cannot be matched retroactively, and rebuilding one from country, device or a nearby timestamp is not a match.
- The conversion action. Name the exact action you intend to upload into, and note whether it is primary or secondary, because only primary actions roll into the Conversions column and into bidding.
- The event time and its time zone. Send the time the business event occurred, not the time the record was uploaded, and write down which time zone the CRM stores.
- The value and currency. If you send a value, send the currency with it, and keep forecast value separate from booked value.
- A stable dedupe key. An internal lead or opportunity ID with an event version, so that a retry after an error does not create a second customer record.
Step 3: record the basis and the time zone before comparing periods
Google Ads can report conversions on a click-time basis and a conversion-time basis, which place the same conversion in different reporting periods. Pick one basis and keep it on both sides of a comparison, because switching between them changes the question rather than only the display. Write the basis, the account time zone and the conversion window next to every export file you keep, and compare only files that share those settings.
Step 4: reconcile in a fixed order
- Choose one conversion action, one campaign group and one reporting period. A small difference is easier to explain than an account-wide total.
- Align the basis and the date: compare qualified leads by conversion time against the same action by conversion time.
- Separate the population. Organic, referral and other-channel leads do not belong in a one-to-one comparison with an ad account.
- Check the counting settings, the attribution model and any repeated uploads before treating a difference as unexplained.
- Read the upload diagnostics before calling a missing event a reporting delay.
An export from Google Ads only shows what Google was able to record; sales-confirmed numbers stay in your own system. Keep a short exception list with the reason found, the evidence checked and the owner, and leave the rest marked as unresolved rather than forcing the two totals to match.
A hypothetical example (invented numbers)
The numbers below are invented teaching numbers for a fictional account. They are not a client case, a benchmark or an observed result.
Suppose an account records 40 form submissions in a month, and the definition accepted by sales is that a qualified lead has a named product, a deliverable market and a contact willing to share requirements. Of the 40 submissions, sales mark 15 as qualified: 11 during the same month and 4 after the month closes. The month's submissions, the month's qualifications and the number of closed deals are three different figures. Uploading all 40 as qualified leads would replace the account's picture of a good lead with the picture of a form fill; uploading the 15 matches the written definition, and the 4 that qualify later belong in a later comparison rather than in this one.
Where Guangsuan fits
Guangsuan's Google Ads management service covers account structure, search terms, landing pages, conversion checks and reporting, and its published scope includes linking website analytics and deploying and checking conversion tracking. The company states that its service aligns conversion definitions with sales feedback so that it is clear where budget should continue to go, and it says plainly that it does not promise a fixed volume of inquiries or a guaranteed closing result.
If the immediate problem is producing a clean file to reconcile against the CRM, Guangsuan's guide to exporting Google Ads data and reading dates and conversions correctly is the companion to this article.
What to prepare before you ask
For an existing account, Guangsuan asks for the website, the target market, the current problem and the historical data you are authorised to share, which is what an account diagnosis works from. Two additions make the first conversation more useful: the current conversion action list with primary and secondary status marked, and the lead dictionary from Step 1 with one real record filled in.
FAQ
Should we import only closed deals?
Not necessarily. Closed deals arrive late and in small numbers, which makes them a weak signal early on. An intermediate event, such as a sales-accepted qualified lead, can be imported first, provided its definition is written down, matched consistently and kept separate from closed deals in reporting.
What if old leads have no click identifier?
They cannot be matched retroactively. Start capturing the identifier for new leads and treat the earlier period as unmeasured rather than reconstructing an identifier from country, device or a nearby timestamp.
How long can we wait before uploading an event?
The matching and import windows depend on the data source you use, so confirm the current limits in Google's documentation for that route instead of assuming one deadline covers every upload method. Keep the event's real occurrence time, and expect that events older than the window you actually use may be rejected.
Will importing qualified leads make the account find more of them?
No provider can commit to that, and Guangsuan states that it does not promise a fixed volume of inquiries or a guaranteed closing result. What better data changes is what the account is optimised against, and that only helps once the signal's volume and consistency are sufficient for the way you are bidding.