If you double a budget and read cost per SQL the week the test ends, you're comparing leads that had weeks to qualify with leads that had days. The newer period looks worse because its leads haven't been through the sales process yet, not because the budget failed.
Read cost per lead early. Judge cost per SQL only once the newer leads are as old as the older ones were when you counted them.
Cost per SQL doubled. The test hadn't failed.
A B2B client of ours ran a campaign at $40 a day, then doubled the budget for a similar stretch to see how sales-qualified leads responded. For this client, an SQL is a lead that books a demo, completes it, and leaves the call looking likely to buy.
When we put the two periods side by side, cost per lead after doubling was $3 cheaper. Cost per SQL had gone from $210 to $402. Read flat, doubling the budget had doubled what an SQL cost.
But when we ran the analysis, the leads from the first period had had time to mature and move down the funnel. The second period's leads hadn't had that time. Our conclusion in the report: the top of the funnel was fine, and the SQL verdict had to wait until the newer leads had matured. Only then could we say whether doubling worked.
Why the newest period always looks worse
Spend is counted the day it happens. Qualified outcomes arrive later. That gap exists in your CRM, and Google Ads builds it into its reporting too.
- Conversions land on the click date. Google's standard conversion columns report a conversion against the day of the click, so a lead who clicked last week and converted this week counts last week. Recent weeks keep filling in after you look.
- They can keep arriving for a while. Google says conversions can be reported up to 90 days after the click, depending on the conversion window.
- Google warns about this exact comparison. Recent performance may not look as strong as past performance, it says, because spend is fully reported while some conversions are still to come, which shows up as a higher cost per conversion.
The "by conv. time" columns, such as Conversions (by conv. time), report conversions on the date they happened instead. They're useful for matching Google Ads to your CRM, but they don't make a young cohort's leads qualify any faster.
How we read a budget test
- Read the fast metric first. Cost per lead settles quickly. If it moved the wrong way, you know something early.
- Measure your lag. Check how long leads take to become SQLs in your CRM. In Google Ads, segment by Conversions, then Days to conversion, using a date range that ends at least 30 days ago, as Google recommends, so the data is complete.
- Compare cohorts at the same age. Count each period's SQLs the same number of days after that period ended, not on the same calendar date.
- Give bidding the same patience. If Smart Bidding optimizes toward SQLs, Google suggests evaluating over 2 conversion cycles or 2 weeks, whichever is longer, allowing for conversion delay.
Switching what you optimize toward has the same lag, only longer. We cover that in why a conversion goal switch is hard to A/B test.
The takeaways
- Cost per SQL right after a budget test compares mature leads with young ones.
- Google Ads reports conversions on the click date, so recent periods fill in later.
- Conversions can be reported up to 90 days after a click, depending on the conversion window.
- Read cost per lead early. Judge SQLs once the newer leads are as old as the older ones were.
- Find your delay with the Days to conversion segment and compare periods at the same lead age.
Common questions
Why does cost per SQL look worse right after I increase the budget?
Usually because the newest leads haven't had time to qualify. The spend for the period is fully counted, but many of its leads haven't booked or completed a sales call yet. Compared with an older period whose leads had weeks to move through the funnel, the new period will look more expensive until it catches up.
Does Google Ads report conversions on the click date?
Yes, in the standard conversion columns. Google says a click last week that converts this week is reported last week, so cost per conversion lines up with spend. The "by conv. time" columns, such as Conversions (by conv. time), report conversions on the date they happened instead.
How long after a click can a Google Ads conversion be reported?
Up to 90 days, depending on the conversion window you set. Google warns that this delay can make recent periods show fewer conversions and a higher cost per conversion than they will once the late conversions arrive.
How do I see my conversion delay in Google Ads?
Segment a campaign, ad group or keyword report by Conversions, then Days to conversion. Google recommends a date range that ends at least 30 days ago, or longer if your conversion window is longer, so the report has complete data.
How long should I wait before judging a budget test on SQLs?
There's no platform rule. We wait until the newer leads are as old as the older leads were when we counted them, which is at least one full lead-to-SQL cycle. Cost per lead can be read sooner.