Short link clicks in GA4: forward every click
Send each human click on your short links to Google Analytics 4 through the Measurement Protocol, for the organisation, one folder or one link.
On this page
Your site's Google Analytics tag sees a visitor once your page loads, but the click on your short link happens before that, and a link to a partner's page or an app store never reaches your tag at all. GA4 forwarding puts short link clicks in GA4: Brevily sends each human click to your property as a short_link_click event, through Google's Measurement Protocol, within about a minute. Your links then sit beside your site's traffic, for every link, one folder or a single link.
Before you start: you need short links (see how to create a short link) and a GA4 property with a web data stream you can manage. Adding it takes the Integrations › Create permission. GA4 forwarding depends on your plan; see pricing.
Short link clicks in GA4: how forwarding works
You give Brevily two values from your GA4 stream. From then on, every human click on the links it covers goes to GA4 as one event, timed at the moment of the click. Bots and link previews are never sent.
- What GA4 receives: a
short_link_clickevent with the short link's domain and back-half, where the visitor was sent, whether it was the link or its QR code, and the visitor's country, device, browser and referring site. Anything Brevily couldn't tell is left out. - Who the visitor is: short links set no cookie, so GA4 gets a pseudonymous id for one browser on one domain, for one day in your organisation's time zone. Repeat clicks from that browser that day count as one user; the next day, as a new one.
- Events too: if you track sign-ups and sales, each reported event also goes to GA4, named as close to your event name as GA4 allows, with its amount as the value and its currency.
- No ad personalisation: every event is sent with personalised ads switched off.
Clicks are sent from the moment you add the stream. Clicks from before, or from while it was turned off, are never sent.
Get your measurement ID and API secret from GA4
- In Google Analytics, open Admin › Data streams and choose the web stream the clicks should land in.
- Copy its Measurement ID. It looks like
G-XXXXXXX. - On the same stream, open Measurement Protocol API secrets, create one, and copy its value.
Treat the API secret as private: with it and the measurement ID, anyone can send events into your property.
Add GA4 forwarding in Brevily
- Open Link setup › Integrations.
- On the Google Analytics 4 card, choose Add GA4.
- Paste the Measurement ID and the API secret.
- To send one link's clicks only, type it in One link only, such as
go.example.com/back-half. Leave it blank for every link. - Choose Add GA4.
[screenshot: Link setup › Integrations, the Add GA4 dialog with Measurement ID, API secret and One link only]
The stream appears on the card as Active, showing its measurement ID and the link it covers, or Every link. A stream for every link needs someone who can see every folder.
Send one folder's clicks
A stream can also cover one folder, hearing only the links in it, which suits an agency sending each client's links to that client's own property. Folder streams are added over the API, by the folder's code, and depend on your plan; see add an integration in the API reference and the Brevily API guide. Each GA4 stream counts against your plan's integrations, together with webhooks and retargeting pixels.
Test it and find the clicks in GA4
In the stream's row menu, choose Send test. Brevily sends a sample click to GA4's validation service, which records nothing and says what it would refuse:
- Test delivery accepted means the event itself is right.
- Google Analytics would reject it lists GA4's reasons.
A passing test checks the event, not your measurement ID and secret: GA4 accepts any event without saying whether it kept it. To be sure, open one of your links yourself, then look in GA4's Realtime report for short_link_click among the event counts.
[screenshot: GA4 Realtime with short_link_click in the event counts]
To build reports on a value such as the back-half or the source, register it in GA4 under Admin › Custom definitions as an event-scoped custom dimension. GA4 only fills it in from then on, and takes a while before it shows in reports.
Deliveries, retries and what's counted
- Every send is logged under Analytics › Deliveries, with GA4's answer and how long it took.
- A failed send is retried for about seven hours, then given up. One GA4 would refuse every time is given up at once.
- Each click or event sent to each stream is one delivery against your plan's deliveries a month, the same count webhooks use.
- Turning a stream off stops it sending and gives up what it still owed. Turn on starts it again from that moment.
Common questions
Does Brevily's GA4 forwarding replace the GA4 tag on my website?
No. Forwarding adds the click on the short link, which happens before your site loads. Your site's tag still records the visit that follows.
Why don't Brevily's clicks match GA4's users?
Brevily counts clicks. GA4 builds users from a visitor id that changes each day, so one person clicking on three days reads as three users.
Can I send different short links to different GA4 properties?
Yes. Add a stream per property, each for one link or, over the API, one folder.
Can I rename the short_link_click event in GA4?
No. Clicks always arrive as short_link_click, so reports stay comparable.
Next steps
- Click webhooks: the same clicks, signed, to your own server.
- UTM parameters on short links: credit the visit on your site to the right campaign.
- Track sign-ups and sales: report what the clicks led to, and send those events to GA4 too.
- What Brevily counts as a click: why bots and previews never reach GA4.
On this page