Google Analytics 4 on a Spotify Link: Free GA4 Setup

To add Google Analytics 4 to a Spotify link, paste your G- Measurement ID into Sptfy once; from then on every click on every link sends a page_view to GA4 before the fan reaches Spotify. There is no code to install and nothing to add per link. GA4 is the one network Sptfy supports that isn't an ad platform, so it doesn't build an ad audience on its own. What it does is put your link clicks next to your website data, with Google's reporting on top, and give you a second way into Google Ads if the two accounts are linked.

What you get

Each click records one page_view event. The hostname is sptfy.co and the page path is your slug, so a click on sptfy.co/your-song shows up in GA4 as a view of /your-song. The page title is the track, album or playlist name. Referrer, device, country, language and the rest are filled in by GA4 the same way they are for any page. The event fires in the background as the fan clicks through, on the branded page that sits between your link and Spotify, so there is nothing to install and nothing for the fan to do.

That is the whole event list. Sptfy sends no custom events, no parameters of its own and nothing from inside Spotify. Worth knowing before you design a report around it.

Step 1: find your Measurement ID

A Measurement ID looks like G-XXXXXXXXXX: the letter G, a hyphen, then ten letters and numbers. As of 2026 it is at Admin → Data collection and modification → Data streams → your web stream, near the top of the stream details. Google moves menus around; if it isn't there, search the Admin page for "Measurement ID". Don't confuse it with the property ID, which is a plain number, or with an AW- Google Ads tag.

There are two reasonable setups and both work:

• Same stream as your website. Link clicks land in the reports you already look at, separated from your site by hostname.
• A separate property for Sptfy links. Nothing mixes, the reports are cleaner, and you have one more property to check.

If you don't have a website, create a GA4 property with a web data stream for sptfy.co. It takes a couple of minutes and gives you a Measurement ID straight away.

Step 2: paste it into Sptfy

Go to Dashboard → Settings → Tracking Pixels and paste the ID into "Google Analytics 4 Measurement ID", then save. Sptfy checks the format before accepting it, so a typo is rejected rather than silently ignored. Entering your first pixel ID turns tracking on for your account, and every link fires GA4 from then on unless you flip that link's "Disable Tracking" switch.

If you also use the Google Ads remarketing tag, both run from a single gtag.js load, so adding GA4 doesn't add a second script or extra time before Spotify opens. The Google Ads remarketing guide covers that side.

Step 3: verify in Realtime

Open one of your links in an ordinary browser tab, then in GA4 go to Reports → Realtime. Within a few seconds you should see one active user and, under views by page title, the title of your track with the path /your-slug. If nothing appears, check the ID for a stray space, make sure you clicked the link in a browser rather than pasting it into a chat app (link previews and crawlers never fire pixels), and check that the link's tracking isn't disabled.

Standard reports fill in over the following day or so. Realtime is the only place you'll see a click the moment it happens.

Step 4: use it

Reports. As of 2026, Reports → Engagement → Pages and screens, filtered to hostname sptfy.co, lists your slugs with views and users. That is roughly what Sptfy's own dashboard shows, in Google's format, with Google's date comparisons and its own retention window.

Explorations. A free-form exploration with page path as the rows lets you break each slug down by session source, device category, city or anything else GA4 records. This is where one slug per channel pays off: song-ig, song-tt and song-yt sit side by side. The custom short link guide covers the naming pattern.

Audiences. Create an audience with the condition page_location contains sptfy.co, or contains a single slug for one release. If your GA4 property is linked to a Google Ads account, that audience can, as of 2026, be shared with Google Ads and used for remarketing. The exact steps depend on how the accounts are linked, so check Google's help if it doesn't show up on the Ads side. For a route that doesn't go through GA4 at all, paste your AW- tag into Sptfy as well.

Limits

• page_view only. No custom events, no parameters of your own and no conversion events sent by Sptfy.
• Nothing from inside Spotify. There is no cross-domain tracking into open.spotify.com. The session ends when the fan leaves the Sptfy page, so streams, saves and follows never reach GA4.
• Engagement metrics mean nothing here. The Sptfy page is on screen for a fraction of a second, 2.5 seconds at most. Count views and users; ignore engagement time and bounce rate.
• Ad blockers. gtag.js is blocked on a Sptfy page the same as on any site, so GA4 will count fewer clicks than Sptfy's own dashboard, which records every click whether or not a script runs.

For the numbers you get with no Google account at all, see Spotify link analytics. For why musicians put pixels on their links in the first place, read Spotify retargeting ads for musicians, and the FAQ covers the rest.