Google Analytics on share links

You can attach your Google Analytics 4 measurement ID to a document so its viewer page loads the Google tag and reports visits to your GA4 property, alongside your other site data. GA4 and EveryPage's built-in readership measurement see different facets of the same audience.

Add your GA4 measurement ID

Open a document's sharing settings and enter your GA4 measurement ID under Google Analytics. The ID must match G- followed by 4 to 14 uppercase letters or digits—for example G-AB12CD34EF. Lowercase letters and other prefixes are rejected. You can find your measurement ID in Google Analytics under Admin, in the details of the web data stream for your property.

Once applied, the viewer page for that document loads Google's gtag.js and sends a page view. The measurement ID is set per document, not per account, so each document you want measured needs its own entry. It applies to embedded viewers as well as the standalone share link, and because the viewer carries no owner signal, your own visits to your share link register in GA4 too.

How GA4 and EveryPage readership differ

Adding GA4 is a supplement to EveryPage's built-in readership reporting, not a replacement. They complement each other:

• Google Analytics sees page views: when someone loads or reloads the viewer, GA4 records an event.
• EveryPage readership sees per-reader activity: how long they spent on each page, which pages they viewed, whether they reached the end, and (on Pro) their email or identity.

GA4 does not measure read depth, dwell time per page, or the read-through funnel—those insights live only in EveryPage. Both systems count the same visitor, but they answer different questions. Use GA4 to understand traffic volume and source (via acquisition reports) and EveryPage to understand how deeply readers engage with the document itself.

Ad blockers and tracking

Readers who have ad blockers or tracking-prevention tools enabled typically do not send data to Google Analytics: gtag.js is fetched from googletagmanager.com, a third-party host that blocklists cover by default. Those same readers usually still register in EveryPage's own readership, which is captured by first-party requests to the document's own origin rather than a third-party script. If you see a gap between your GA4 page views and EveryPage view sessions, ad blocker adoption in your audience is a likely reason.

Privacy and third-party data

Adding a GA4 property to your share links changes the privacy posture of those links. EveryPage's own readership reporting never stores visitor IP addresses—each address is mapped to a pseudonymous, salted identifier and then discarded—and EveryPage loads no third-party tracker into the viewer on its own.

Connecting GA4 adds one. The reader's browser fetches Google's script and sends the visit to Google, which processes that data as a third party under its own data practices and privacy policies—separate from, and not covered by, EveryPage's. If your documents reach people in jurisdictions with strict data protection laws (such as the EU), the consent and disclosure obligations for that processing are yours, not EveryPage's; EveryPage shows readers no consent banner for it. For details on EveryPage's own privacy model and what data it collects, see Encryption and Privacy.

Requirements

Google Analytics integration is available on Pro plans and requires an active GA4 property. Saving a measurement ID on a Free or Basic account is rejected, and the plan is re-checked when a viewer loads the document—so if you downgrade from Pro, the tag stops loading immediately. The stored ID is kept and starts working again if you return to Pro. Free and Basic owners still get EveryPage's own readership reporting.