Spotify Smart Link with Meta Pixel: Free Setup Guide
Add your Meta (Facebook) Pixel to a Spotify link for free. Find the Pixel ID, paste it in Sptfy, verify the PageView, then build a retargeting audience.
Updated
To add a Meta Pixel to a Spotify link, paste your 15–16 digit Pixel ID into Dashboard → Settings → Tracking Pixels in Sptfy; from then on, every click of every link you own fires a PageView before Spotify opens. That takes about two minutes. The rest of this guide is where to find the ID, how to check it's working, and how to turn the clicks into a Custom Audience you can retarget on Instagram and Facebook. If you want the why first, read Spotify retargeting ads for musicians.
What you get
When a fan clicks your link with tracking on, Sptfy shows a small branded page with your cover art for a fraction of a second, 2.5 seconds at most. On that page the Meta Pixel loads and sends one PageView event with the URL https://sptfy.co/your-slug. For browsers with JavaScript off, a no-script image fallback sends the same PageView. Then the page hands off to Spotify. It all happens in the background as the fan clicks through: nothing for the fan to do, nothing for you to install.
That is all it sends. No custom events, no conversion events, no Conversions API or server-side events, no advanced matching. Nothing that happens inside Spotify (the stream, the save, the follow) is visible to the pixel. What you get is a clean list of people who clicked through to your music, which is exactly what a retargeting audience needs.
Step 1: find your Pixel ID
Your Meta Pixel ID is a 15 to 16 digit number. As of 2026 it lives in Meta Events Manager: open Events Manager, click Data sources in the left column, select your pixel (Meta calls it a dataset in some accounts), and the ID is shown under the name and again in the Settings tab. Menus move; if it isn't there, search Events Manager for "Pixel ID" or "Dataset ID". They are the same number.
If you don't have a pixel yet, create one from the same Data sources screen. You don't need to install any code on a website; for this purpose, Sptfy is the website. One pixel per artist project is the usual setup. Because pixels are set at account level, an account that runs links for several artists should be split into one Sptfy account per artist.
Step 2: paste it into Sptfy
Log in, go to Dashboard → Settings → Tracking Pixels, and paste the number into the field labelled "Meta (Facebook) Pixel ID". Save. Tracking switches on automatically the first time you enter an ID. The ID is validated on the server, so if you've pasted a dataset name, a URL or a stray character by mistake, it's rejected rather than silently saved.
That's it for setup. You don't add the pixel to each link; it fires on every click of every link in your account. If you want one particular link to skip the pixel, open that link and flip its "Disable Tracking" switch. It becomes a direct redirect and its clicks still show in analytics.
Step 3: verify it fires
Click your own link in a normal browser, let Spotify open, then go back to Events Manager. In the Overview for your pixel you should see a PageView within a few minutes, and under the event's details the URL should be your sptfy.co link. That is the confirmation that matters.
The Meta Pixel Helper browser extension also works, but the Sptfy page hands off to Spotify quickly, so you may only catch a brief flash of the icon. Events Manager is the more reliable check. Two things that will never produce a PageView: pasting the link into a chat or a social post (the link-preview crawler fetches the page but never runs pixels, on purpose), and testing with a content-blocking extension or private mode that blocks trackers.
Step 4: build a retargeting audience
As of 2026, in Meta Ads Manager open Audiences, click Create audience → Custom Audience → Website, and choose your pixel. Then pick one of two rules:
- All website visitors. Everyone who clicked any of your Sptfy links. This is the audience most artists want: everyone who has ever clicked through to your music.
- People who visited specific web pages, with a rule such as URL contains
sptfy.co/your-slug. This gives you an audience per release or per channel, useful when you made a separate slug for a single and want to retarget only the people who clicked it.
Set the retention window as long as Meta allows (up to 180 days as of 2026; the audience form shows the current limit), give it a clear name, and save. Meta fills the audience as PageViews arrive. It needs enough people before ads can deliver, and that threshold is Meta's to set, so give it time.
Once it's populated, create a Lookalike Audience with your website visitors as the source. That reaches people who behave like your link clickers but haven't heard you yet. Between the two, you have a warm audience for the next single and a cold audience that starts much closer to home than an interest target.
Tips
- One slug per channel. Make
song-igfor Instagram andsong-fbfor Facebook. You can retarget by channel with a URL rule and compare them in the Slug breakdown of your click analytics. See also Spotify link for Instagram bio. - Volume matters. A tiny audience won't deliver ads. Put the link everywhere fans already click and let it fill up before you spend.
- Combine networks. Sptfy fires all five pixels together, so add your TikTok Pixel alongside Meta and build both audiences from the same clicks.
- Stay honest. The tracking page is visible to fans and the privacy policy says what is collected. If you need a pixel-free link, use Disable Tracking on that link.
Short answers to common questions are in the FAQ.
FAQ
What does a Meta Pixel ID look like?
A 15 or 16 digit number, for example 123456789012345. As of 2026 it is shown in Meta Events Manager under Data sources, next to your pixel or dataset name. Sptfy takes the number only, not the pixel code snippet.
Which event does Sptfy send to Meta?
A single PageView on the Sptfy page before Spotify opens, plus a no-script image fallback for browsers without JavaScript. No custom events and no conversion events.
Does Sptfy support the Meta Conversions API?
No. Sptfy fires the browser pixel only. There is no Conversions API, no server-side event and no advanced matching.
Can I build a separate audience for each release?
Yes. Give each release its own slug, then create a Custom Audience with a rule such as URL contains sptfy.co/that-slug. All-visitor audiences cover every link at once.
Do I need to add the pixel to each link?
No. Paste the ID once in Dashboard → Settings → Tracking Pixels and it fires on every click of every link you own. Use the Disable Tracking switch on any link you want to keep pixel-free.