Whether GA4 records a click to your documentation depends entirely on where the documentation lives. The outbound clicks option in enhanced measurement sends a click event each time a visitor clicks a link that leads them away from the current domain and to another website, so docs served from the same domain as the page linking to them produce nothing at all. Docs on a domain you also own will produce the event — right up until you add that domain to cross-domain measurement, at which point Google stops firing it on purpose.
The outbound clicks option in GA4's enhanced measurement produces an event named click, and it carries five parameters: link_classes, link_domain, link_id, link_url and a boolean called outbound. Those populate the Link classes, Link domain, Link ID, Link URL and Outbound dimensions in reporting. Nothing has to be added to the page for this — it is a switch on the web data stream — which is also why it is easy to assume it is covering a link that it is not.
Documentation ends up in one of four places, and each one changes what the built-in event can tell you. The table below is the decision, and the second row is the one to test rather than assume: the trigger is described in terms of leaving the current domain, and whether a subdomain of your own site counts as leaving depends on how the tag resolves the two hostnames on your property.
| Where the docs are served | Does the click event fire | What to do about it |
|---|---|---|
| The same domain, at /docs | No | Send your own event, or read docs pages as page views |
| A subdomain such as docs.example.com | Test it on your own property before assuming | Check in DebugView whether a click event with outbound true appears |
| A separate domain you own | Yes, unless it is in cross-domain measurement | Choose between the click event and one joined session |
| A hosted documentation product | Yes | The click is the last thing you see; what happens after it is theirs |
A consent banner changes what GA4 can measure, and the reports carry no marker saying so. What the seven consent types cover, what basic and advanced consent mode each do when someone declines, and how to read numbers collected under either.
Market4 turns one release note into a changelog page, a blog post, a mail-out and a week of social posts — and then tells you which of them brought anyone back.
Cross-domain measurement and outbound click events answer opposite questions, and Google makes you pick. Links to domains configured for cross-domain measurement do not trigger outbound click events, because the point of that configuration is that the second domain is not somewhere the visitor left to — it is more of your site. The identifiers are carried across in a URL parameter named _gl so the cookies on the second domain keep the same user and session ids, and the journey stays one session instead of two.
Not configuring it has a cost that is easy to underestimate. Without cross-domain measurement a new cookie with new identifiers is created for each domain a visitor touches, so one person moving from your marketing site to your docs on a second root domain is counted as two users and two sessions, and the first domain starts appearing as a referrer to the second. Trading that for a tidy click event is rarely the right trade when both domains are yours.
Documentation on the same domain needs no outbound click event and cannot have one, which is worth stating plainly because a lot of time gets spent looking for it. Docs pages on the same domain are ordinary page views in the same property, so the visit itself is already measured. The question that usually sits underneath is a different one: which product pages send people into the docs, and how often. Three ways to answer it, in order of effort:
A custom event here has the same failure mode as any other GA4 event: it is configured, it looks correct, and it never appears in a report because the parameter was never registered as a custom dimension or the tag never fired on the pages that mattered. Check it in DebugView on the exact page before wiring anything downstream to it.
An outbound click event is recorded when the link is clicked, not when the destination finishes loading, so it measures intent to leave rather than arrival. A click to a docs page that then failed to load, was cancelled by a fast second click, or landed on a redirect chain still counts as one click event. Comparing the click count on your side with the page view count on the destination side is what shows that gap, and it needs both properties or one property covering both domains.
Only if the documentation is on a different domain. The enhanced measurement option for outbound clicks fires a click event when a visitor clicks a link that leads away from the current domain and to another website, so a link from example.com to example.com/docs produces nothing. Documentation on a separate domain does produce the event, unless that domain has been added to your cross-domain measurement configuration.
Five: link_classes, link_domain, link_id, link_url and outbound, which is a boolean. They populate the Link classes, Link domain, Link ID, Link URL and Outbound dimensions in reporting. link_url is the one most reports are built on, because it is the full destination address; link_id and link_classes are only useful if the links on your pages actually carry ids and meaningful class names.
The most likely cause is that the destination domain was added to cross-domain measurement. Links to domains configured for cross-domain measurement do not trigger outbound click events, by design, because that configuration declares the second domain to be part of the same site rather than somewhere the visitor left to. Check the cross-domain settings on the data stream before looking for anything broken on the page.
Only if reading the documentation is a step you actually want people to take on the way to something you care about. Marking every outbound click as a key event turns the key event count into a general activity count and makes it useless for comparing campaigns. If docs reading genuinely predicts activation for your product, mark it and measure whether that prediction holds; if it does not, leave it as an ordinary event.
A signup that starts on your marketing site and finishes in your app is two users in GA4 unless the domains are configured together. Here is what the setting does and what it cannot fix.
A server container is a service you now operate: a host, a domain, a deployment and someone to notice when it stops. Here is what that buys, and when it does not buy enough.
