Adobe Analytics vs Google Analytics 4

What the numbers say

The two price rows cannot be read against each other, and not only because one of them is free. Google’s standard property carries no charge and counts events. Adobe quotes every customer and sizes the contract in server calls, a unit that can multiply inside one implementation: when the same hit reaches several report suites, the first counts as a primary server call and the rest as secondary ones, and a dashboard under Admin, Server call usage, compares consumption with the contracted figure.

Both storage rows read the same and arrive there by different routes. Adobe names three data processing locations, in Oregon, London and Singapore, where raw data becomes a report suite, and its privacy pages name none in the EU. Google states that data from EU, Swiss and UK devices is collected through domains and servers in those regions and that those IP addresses are dropped before logging, after which the traffic goes to Analytics servers for processing. A storage region is not among the settings a Google customer picks, so the same value in that row means a different thing on each side.

Retention runs on two clocks. Adobe keeps data for 25 months by default. Google’s standard property chooses 2 or 14 months for event-level and user-level data, and that setting reaches explorations and funnel reports while standard aggregated reports carry on past it, which is why the row reads configurable rather than a single figure.

Who picks which

Adobe Analytics arrives as an implementation rather than a snippet. The documented path for new customers is the Web SDK extension inside a tag property in Experience Platform Data Collection, with the loader tag on every page; loading alloy.js yourself and the older AppMeasurement library are the alternatives. Reports are built in Analysis Workspace over report suites, projects can be shared read-only with people who have no Analytics access or sent as CSV or PDF on a schedule, and bot rules apply the Interactive Advertising Bureau spider list plus custom rules by user agent or IP address.

Google Analytics 4 is self-serve from the first screen. You create a property and a web stream in Admin, put the tag on the page or into a tag manager, and switch on enhanced measurement, which records scrolls, outbound clicks, site search, video engagement, file downloads and form interactions without code changes. Its connections are Google’s own: Ads, Search Console, BigQuery for raw events. The platform rows that read not confirmed for Adobe follow from where each vendor writes. Google publishes guides for shop platforms and site builders; Adobe documents deployment through a tag property and leaves those platforms unlisted.

Questions and answers

Do the two price columns compare?

No. One shows a free standard property counted in events, the other a quote counted in server calls, and the directory does not convert between units. Multi-suite tagging and the copies a VISTA rule makes raise the server call count without changing what a visitor did, so two sites with identical traffic can sit far apart on an Adobe contract.

Why do so many rows for Adobe read not confirmed?

Because the value records what the vendor documents, not what an agency can build. A platform row turns to yes when the vendor publishes its own app, plugin, package or guide for it, as the methodology sets out. Adobe documents deployment through its own tag property rather than platform by platform, so shop platforms, site builders and frameworks stay without entries of their own.

Can either keep data longer than the row shows?

Yes, on both sides, by different means. Adobe sells retention as yearly extensions, up to eight of them, for a stated maximum of 10 years and one month. A standard Google property stops at 14 months for event-level data, and longer windows belong to Analytics 360.