You open the weekly ads report and see fewer conversions, a higher acquisition cost, and spend that looks normal. Google Ads shows more leads than your CRM, while yesterday's analytics export doesn't match today's. Before you cut a budget, you need to know whether performance changed or the numbers aren't ready yet.
Good pay per click reporting makes that distinction visible. It tells readers what each metric counts, when the data was updated, and which business outcome the conversion represents. Without those labels, two accurate reports can lead to opposite decisions.
Table of Contents
- Core PPC Metrics at a Glance
- How Paid Search Billing Shapes Every Report
- Data Freshness and Reporting Cadence
- Choosing an Attribution Model Before You Compare Campaigns
- Reading Auction Insights to Explain Lost Visibility
- Diagnosing Results When the Numbers Move
- Build a Weekly Reporting Routine You Can Verify
Core PPC Metrics at a Glance
PPC reporting turns paid-click activity into decisions about bids, budgets, and keywords, so every number needs a formula and a question it answers. Start with a shared vocabulary, then check whether the metrics describe the same campaign scope, reporting period, and conversion action.
Core PPC metrics, formulas and what each reveals
| Metric | Formula | Question it answers |
|---|---|---|
| Impressions | Count of times the ad was shown | How often was the ad displayed after entering eligible auctions? |
| Click-through rate (CTR) | Clicks ÷ Impressions × 100 | Does the ad earn attention? |
| Cost per click (CPC) | Cost ÷ Clicks | What does each paid click cost? |
| Conversion rate | Conversions ÷ Clicks × 100 | Does the landing experience convert clicks? |
| Cost per acquisition (CPA) | Cost ÷ Conversions | What does each recorded lead or sale cost? |
| Return on ad spend (ROAS) | Conversion value ÷ Cost | How much recorded value returns per unit spent? |
| Impression share | Impressions ÷ Eligible impressions | How much eligible visibility is captured? |
An impression means the ad appeared, not merely that it entered an auction. Impression share uses estimated eligible opportunities as its denominator, so it isn't a measure of your share of the entire market.
The conversion-rate formula above is a click-based reporting definition. When importing a platform's native rate, preserve its actual denominator rather than assuming every campaign measures interactions identically.
Check the arithmetic before interpreting performance
Consider a hypothetical search campaign with $1,000 spend, 10,000 impressions, 400 clicks, and 20 conversions. Those inputs produce:
- CTR: 400 ÷ 10,000 × 100 = 4%.
- CPC: $1,000 ÷ 400 = $2.50.
- Conversion rate: 20 ÷ 400 × 100 = 5%.
- CPA: $1,000 ÷ 20 = $50.
If that same hypothetical campaign records $4,000 in conversion value, its ROAS is $4,000 ÷ $1,000 = 4.0. That means recorded value equals four times media spend. It doesn't establish profit, because product costs, service delivery, and other expenses aren't included.
The calculations are straightforward. The interpretation requires more care: a conversion might be a purchase, a form submission, or a qualified lead. A lower CPA for form submissions isn't necessarily better than a higher CPA for sales-ready opportunities.
Practical rule: Name the outcome beside the metric. Cost per qualified lead is more useful than CPA when lead quality drives the decision.
These metrics form the vocabulary of a useful report, but none should be read alone. Put traffic cost beside conversion efficiency, and put recorded conversion value beside the business's actual revenue and margin.
How Paid Search Billing Shapes Every Report
Think of a shop window. A passer-by who sees the display resembles an impression; someone who walks inside resembles a click. For click-billed search advertising, the click triggers media cost, not the exposure alone.
The IAB/PwC Internet Advertising Revenue Report distinguishes paid listings, where advertisers pay for clicks on text links near search results, from contextual search, where links are placed according to page content. Keep those placement categories separate so readers can connect visibility, clicks, and costs within a consistent definition.
The billing relationship is easier to follow visually.

Write the billing definitions into the report
A blended dashboard can hide differences between search, display, and social advertising. Adding spend is useful, but comparing efficiency requires compatible click definitions, billing rules, and attributed outcomes.
Include these definitions in the report's notes:
- Click: Specify the field, such as a billable ad click recorded by the advertising platform. Don't substitute analytics sessions.
- Cost: State whether the total includes media spend only or also includes fees and tax.
- Channel taxonomy: Keep search, display, social, and contextual placements in separate columns before building an aggregate view.
This also prevents a common reconciliation mistake. A paid click and a recorded website visit describe different events, so a mismatch doesn't automatically mean either system is wrong.
Use the billing definition to explain expenditure, then use site and CRM records to investigate what happened after the click.
Data Freshness and Reporting Cadence
The same account can show different totals depending on when you pull the report. Fresh data isn't necessarily complete data, particularly when event collection and attribution processing happen on different schedules.
According to Google Analytics' BigQuery export documentation, streaming export can make same-day events available within a few minutes, but it's best-effort and may omit late events or failed uploads; attribution for existing users may require approximately 24 hours to process. Google recommends the stable daily export for finalized analysis rather than relying solely on intraday tables.
Use this timeline to distinguish monitoring from decision-ready analysis.

Reporting cadence and data status
| Tier | Data source | Status label | Use |
|---|---|---|---|
| Daily pacing | GA4 intraday BigQuery tables | Provisional | Spot anomalies and pacing |
| Weekly review | Completed daily export | Provisional until lag passes | Trend checks and channel comparison |
| Monthly decisions | Finalized daily export after observed lag | Finalized | CPA, ROAS, and budget decisions |
Use advertising-platform spend for budget pacing, alongside intraday analytics for site activity. An event export isn't a replacement for the account's media-cost ledger.
Preserve the fields that explain discrepancies
Keep timezone, currency, event timestamp, click identifier, conversion action, and update status in the reporting layer. Also display the extraction timestamp so another analyst can reproduce the comparison.
A CRM record created after a sales review won't necessarily align with an analytics event timestamp. A missing click identifier can also prevent a downstream outcome from matching an advertising interaction. Investigate those joins before concluding that campaign quality declined.
Treat finalized as a defined reporting status, not a promise that a record can never be adjusted.
For a walkthrough of the reporting context, use the video below.
Copy this operational timeline into your reporting notes: intraday monitoring, provisional → completed daily tables for weekly review, still provisional where outcomes remain immature → reconciled monthly decision view, finalized after the observed lag. Compare periods at equivalent maturity rather than comparing a newly opened period with a fully settled one.
Choosing an Attribution Model Before You Compare Campaigns
The latest week can look weak even when its eventual results aren't. Standard Google Ads conversion reporting assigns outcomes to the ad interaction date rather than the date the conversion occurred, so delayed outcomes keep revising recent click-date totals after the week closes. A campaign that looked unprofitable on Monday can look acceptable once those late conversions land.
Google's data-driven attribution guidance explains how the model distributes fractional credit across converting and non-converting paths, and it calls for substantial conversion and ad-interaction volume over a 30-day window before the learned allocation becomes dependable. Lower-volume accounts can still work with the rule-based comparisons below; the volume requirement governs how much trust to place in the data-driven option specifically.
Attribution models compared for PPC reporting
| Model | How it assigns credit | Best used for | Main risk |
|---|---|---|---|
| Last click | All credit to the final eligible click before conversion | Examining bottom-funnel capture and simple paths | Undervalues earlier interactions |
| First click | All credit to the first click in the path | Identifying journey starters | Ignores nurturing clicks |
| Linear | Equal credit to every click in the path | A balanced sensitivity view of multi-touch paths | Treats strong and weak touches equally |
| Time decay | More credit to clicks closer to conversion | Examining recency in short sales cycles | Still favors late-stage clicks |
| Data-driven | Fractional credit learned from converting and non-converting paths | Accounts with sufficient path and conversion volume | Harder to inspect, especially with sparse observations |
These are analytical models, not a claim that every option is available in every advertising platform. Rule-based models can still be useful for a warehouse or path-analysis comparison when the required interaction records exist.
Follow the same customer path under different rules
Suppose a display campaign generated an early click in six of ten converting paths, while search supplied the final click in all ten. Last-click attribution assigns search all ten conversions and display none. Linear attribution gives each touch equal weight, so display picks up partial credit on those six paths. Time decay weights the late search clicks more heavily and pushes the split back toward search.
Data-driven attribution may assign display fractional credit if its analysis supports a contribution. Appearing early doesn't guarantee credit, and the path counts alone aren't enough to calculate the allocation.
That distinction matters when someone proposes cutting display because its last-click CPA looks poor. The right response is to inspect the paths and compare credit rules, not assume every early interaction caused the eventual sale.
For cross-platform ROAS analysis, align the outcome, attribution model, and observation window before comparing channel totals. Otherwise, multiple platforms may claim the same customer outcome under different rules, and summing their reported conversions will overstate what you sold.
Before changing allocation: Show click-date spend beside conversion cohorts old enough to evaluate, and label both the attribution model and lag window.
With limited account volume, use transparent rule-based sensitivity views where possible and state what you can't infer. Compare last click with an alternative supported view before restructuring campaigns, but don't treat agreement between models as proof of incremental sales. Two models can share the same blind spot: both still describe credited conversions, and neither measures what would have happened without the spend.
Reading Auction Insights to Explain Lost Visibility
When impressions fall, a manager usually asks whether budget, rank, or competitors caused the loss. Start with Auction Insights for competitive context, then use campaign delivery diagnostics to test the explanation.
Google Ads' Auction Insights documentation lists six Search metrics: impression share, overlap rate, outranking share, position-above rate, top-of-page rate, and absolute-top-of-page rate. Shopping reports three of these: impression share, overlap rate, and outranking share.
Turn competitive metrics into diagnostic questions
- Impression share: How much eligible visibility did we receive? Pair it with lost impression share due to budget and rank.
- Overlap rate: How often did another advertiser appear when we appeared? Check whether competitor presence changed.
- Outranking share: How often did we rank above another advertiser or appear when they didn't? A higher value indicates stronger relative visibility for us, not them.
- Position-above rate: When both ads appeared, how often was the competitor higher?
- Top and absolute-top rates: How often did impressions appear above organic results or in the first ad position?
If lost share points to budget, remove low-value expenditure before considering an increase. If it points to rank, inspect bids, relevance, and landing-page quality rather than assuming budget alone will help.
A hypothetical weekend mobile dip warrants a time-and-device investigation, not an immediate campaign-wide change. Compare that segment's delivery, conversion quality, and bid strategy constraints before choosing an intervention.
A missing Auction Insights row isn't evidence of no competition.
Activity thresholds can prevent low-volume entities from showing competitive data. Check eligibility and volume before interpreting absence as a performance finding.
Diagnosing Results When the Numbers Move
A sudden decline is easy to blame on the campaign. First establish whether the comparison uses compatible definitions, mature outcomes, and working measurement.
Use this table as a triage checklist. The causes are hypotheses to test, not conclusions to copy into a client report.
Reporting symptoms, likely causes and first checks
| Symptom | Likely cause | First check |
|---|---|---|
| Conversions drop in the latest week | Conversion lag on recent click dates | Compare click-date cohorts aged beyond the observed lag window |
| CPA rises while spend stays flat | Attribution model change or edited conversion action | Confirm the model label and conversion-action history |
| Impression share falls | Budget limit, low ad rank, or competitor pressure | Check lost impression share split between budget and rank |
| Platform conversions far above CRM counts | Modeled conversions, consent gaps, different definitions, or double counting | Check consent coverage and CRM-qualified counts |
| Uplift estimate missing | Consent Mode learning period incomplete or minimum thresholds unmet | Confirm eligibility before interpreting the field |
| Clicks with no conversions | Tracking not firing or low conversion volume | Test the conversion tag and check volume |
| Search-term totals differ from ad-group totals | Unreported queries or automated inventory, potentially including AI-mediated results | Compare search-term, ad-group, and keyword totals; label the residual as estimated |
For an absent uplift estimate, Google's Consent Mode guidance says reporting may require at least seven full days and minimum data thresholds. An empty field is therefore a data state, not a measured absence of additional conversions.
Reconcile outcomes without forcing agreement
Build a variance report that separates observed outcomes, modeled outcomes where identifiable, and CRM-qualified results. Record consent coverage, conversion-action definitions, matching coverage, and the reporting cutoff alongside them.
Don't invent a modeled-versus-observed split when an export doesn't expose it. Mark it unavailable and explain the limitation.
Advertising platforms support delivery optimization, analytics describes measured site behavior, and the CRM validates downstream qualification and revenue. A platform lead and a sales-qualified CRM opportunity can both be correct while representing different stages.
For unexplained gaps, use a Google Ads conversion audit checklist to organize tag tests, action settings, duplicates, and downstream matching. Test a complete lead journey rather than stopping when a browser tag fires.
Keep AI-search estimates separate from observed traffic
A Search Engine Land analysis of more than 400 Google Ads accounts found that AI-search activity wasn't identifiable in the analyzed search-term reports. That supports a visibility warning, not a reliable formula for assigning every unreported query to AI search.
Compare totals only after aligning dates, campaign scope, and metric definitions. Call the remainder unclassified traffic and treat any proposed AI allocation as a modeled estimate, not an observed placement total.
The same restraint applies throughout diagnosis: confirm the reporting cause first, then investigate the campaign cause. Where measurement remains incomplete, publish the uncertainty alongside the result.
Build a Weekly Reporting Routine You Can Verify
A weekly routine works like a pre-flight checklist: every item has an owner, a due date, and evidence left behind. Run these actions in a shared sheet, a project tracker, or your existing reporting workflow, and review them at the start of each week.
- Tracking owner: Validate each conversion action through a test journey and its recorded history before analysis.
- Reporting analyst: Publish the attribution model and observed lag window with the report, so readers know which conversions are still arriving.
- Media buyer: Check daily pacing against the spending plan, marking unsettled metrics provisional until the lag window closes.
- Search lead: Review weekly auction diagnostics, including budget and rank constraints.
- Marketing operations owner: Reconcile monthly platform outcomes with CRM-qualified leads or revenue in a variance log.
- Change approver: Record each approved change with its date, reason, and expected effect, so a later dip or spike can be traced to a cause.
Use the checklist below as a quick weekly reminder of who owns each step.

Choose tools that preserve accountability
Any tool that records who changed what, and when, can carry this routine: a spreadsheet, a warehouse dashboard, or a Google Ads dashboard alternative with approval controls. NotFair's advertising connections expose reporting and supported campaign changes, and clients connect Google Ads, Meta, and Search Console with their own logins, so the data and history stay with them. Diagnostic queries run freely, while every write is approval-gated and logged with full provenance, and nothing goes live or changes an ad budget until it is approved.
When a movement doesn't match the change log, treat the numbers as a measurement question first and the campaign as a suspect second. Copy the six actions into a shared sheet, assign an owner and a due date to each, and the next unexplained dip becomes an audit trail instead of a guessing game.
NotFair connects your AI assistant to advertising, analytics, and CRM platforms so you can investigate PPC discrepancies using live account data. Visit NotFair to connect your accounts, ask why conversions changed, and review proposed campaign edits before approving them.



