Analytics & Reporting
November 2, 2026

Is GA4 Enough? What <blue>It Can and Can't Answer for a Paid Media Team</blue>

Troy Diffenderfer
Troy Diffenderfer
Title card: Is GA4 Enough? What It Can and Can't Answer for a Paid Media Team
Table of contents

Scale Smarter with

Connect your sources, clean your data, and watch performance marketing soar with a flat fee and zero drama. Get started with a discovery call

GA4 is enough to understand what happens on your website and to compare channels on a consistent set of rules. It is not enough to run paid media to profit. GA4 does not know your product margins, it will not fully reconcile with the revenue in your store or CRM, and its attribution is a model, not a measure of incrementality. Most paid media teams get the best results by using GA4 as one important source inside a broader measurement setup.

Key takeaways

  • GA4 is strong for on-site behavior, landing page and funnel analysis, channel comparison through UTMs, and audiences for Google Ads.
  • GA4 has no native view of COGS, shipping, returns, or contribution margin, so it cannot tell you which campaigns are profitable.
  • GA4 numbers will not match Shopify, Stripe, or your CRM exactly because of consent, ad blockers, cross-device behavior, and modeling.
  • Exporting GA4 to BigQuery early and joining it with ad cost, order, and product cost data is what turns it from a reporting tool into decision infrastructure.

What GA4 does well for a paid media team

GA4 gives paid media teams a single, platform-neutral view of site traffic. Unlike Meta or Google Ads reporting, it applies the same rules to every channel, which makes it useful for spotting trends and comparing sources. That neutral view is a good input to marketing data infrastructure, even if it cannot be the whole system.

As of November 2026, GA4 is useful for:

  • Channel and campaign comparison based on UTMs, with session, engagement, and conversion data in one place.
  • Landing page and funnel analysis, including where paid visitors drop off between landing, product view, cart, and checkout.
  • Cross-channel attribution using data-driven or last-click models.
  • Audiences that can be shared with Google Ads for remarketing and bidding.
  • Cost import. GA4 supports importing campaign cost data from non-Google platforms, and Google now lists direct connectors for Meta and several other platforms. The Meta connector requires a consistent utm_source and utm_medium for paid Meta traffic.
  • BigQuery export, which gives you raw event data you can query and join with other sources.

Where GA4 falls short

It does not know your margins

GA4 records revenue as the value sent with each purchase event. It does not natively track product cost, fulfillment, discounts that were not passed in, returns that happen later, or payment fees. Two campaigns with the same revenue in GA4 can produce very different profit. That is the same problem covered in why ROAS can hide losses, and it applies to GA4 revenue as much as to platform revenue.

It will not match your backend

GA4 only sees users who load its tag and, where consent mode applies, may fill in gaps with modeled data. Ad blockers, declined consent, cross-device journeys, and broken tagging all create differences between GA4 and the orders in your store or payment processor. GA4 is directionally useful, but it should not be treated as the financial record. Songfinch is a good example of what changes when you reconcile to the actual payment system: how Songfinch reached 99% data reconciliation against Stripe.

Its attribution is a model, not proof of lift

GA4 offers data-driven attribution and last-click options. Google retired the first-click, linear, time-decay, and position-based models in November 2023. Data-driven attribution distributes credit across touchpoints, but it does not tell you whether a campaign caused sales that would not have happened anyway. Questions about incrementality need holdout tests, geo tests, or other experiments.

It has data limits

Standard GA4 properties keep event-level data for explorations for either 2 or 14 months. Standard reports are not affected, but long-range custom analysis is. Explorations can also be sampled on large properties, and data thresholds can hide rows with small counts. The free BigQuery export has a daily limit of 1 million events for standard properties. If you do not turn on BigQuery export early, you cannot go back and recover the raw history later.

It does not see offline or CRM revenue by default

For B2B and high-consideration businesses, the real outcome is often a qualified opportunity or closed deal in the CRM. GA4 can receive offline events through data import or the Measurement Protocol, but someone has to build and maintain that flow. Without it, GA4 measures form fills, not revenue. A setup for connecting ad clicks to closed-won revenue usually lives outside GA4.

Questions GA4 can and cannot answer

GA4 can usually answer:

  • Which landing pages convert paid traffic best?
  • Where in the funnel do paid visitors drop off?
  • How do channels compare under one consistent attribution model?
  • Which audiences engage most with the site?

GA4 cannot answer on its own:

  • Which campaigns produced the most contribution margin?
  • What is our true cost to acquire a new customer, net of returns?
  • Did this campaign create sales that would not have happened anyway?
  • Which leads became paying customers, and what are they worth over time?

What to add on top of GA4

The answer is not to replace GA4. It is to connect it. A practical stack joins GA4's BigQuery export with ad platform cost data, order data from Shopify or another ecommerce platform, payment data, CRM stages, and product costs. Once those live together, you can report contribution margin by channel and campaign, and compare GA4 attribution with backend results.

Illustration of data source logos including Google Analytics, Shopify, Stripe, Meta, HubSpot, LinkedIn, TikTok, and Google Sheets
GA4 is one source among many in a complete measurement setup.

This is the difference between a reporting tool and a measurement system. The case for a client-owned marketing data warehouse is that no single platform, including GA4, sees the full picture. Onward's approach to connecting ad spend to backend revenue starts from the same idea.

A GA4 setup checklist for paid media teams

  1. Standardize UTMs across every platform and campaign, including the source and medium values Meta cost import requires.
  2. Define key events that match real business outcomes, not just page views or button clicks.
  3. Send complete ecommerce data, including item IDs, prices, discounts, and transaction IDs, so purchases can be matched to orders later.
  4. Implement consent mode where required and understand how modeled data affects reports.
  5. Turn on BigQuery export now, even if nobody queries it yet, so raw history accumulates.
  6. Import ad costs so GA4 can show spend alongside sessions and conversions.
  7. Reconcile monthly against store, payment, or CRM totals and document the expected gap.

How Onward uses GA4

Onward treats GA4 as a valuable behavioral and attribution source, not the system of record. GA4 data flows into a warehouse alongside ad platform data, ecommerce and CRM data, and product costs. Media decisions are then made on contribution margin and backend-reconciled revenue, with GA4 used to diagnose landing pages, funnels, and channel trends.

The bottom line

GA4 is a strong free tool for understanding site behavior and comparing channels. It is not enough on its own to tell a paid media team which campaigns make money. Set it up carefully, export it early, and connect it to the data GA4 cannot see.

If you want to know what your GA4 setup is missing, schedule a free audit with Onward.