Turn your almost-fans into a warm audience.
git-royal turns those real, engaged fans into a Meta retargeting audience — built in one click, inside your own ad account.
The majors don't win because their music is better — they win because their data is. They retarget the people who engaged, over and over, at a cost cold advertising can't touch. That machine was locked away from independent artists behind complexity, not price.
git-royal hands it to you. Every git-royal page tracks who previewed and who clicked to stream, and sends those events server-side to your pixel — so they survive ad blockers and your audiences stay full. Then, from a release's analytics, one click packages your warmest fans into a Meta Custom Audience you can advertise to again.
The fans who engage are an audience you own — not scraped, not guessed.
Built from real intent
Audiences come from people who actually previewed or tapped to stream — your warmest, cheapest fans to reach again, not a cold interest guess.
One-click on Meta
From a release's analytics, build the Custom Audience in your own ad account in a single click. TikTok audiences you build in Ads Manager — we feed the pixel.
Blocker-proof data
Events fire server-side via Meta CAPI and TikTok's Events API, so the conversions a browser-only pixel loses still land — fuller, more accurate pools.
Your account, your data
The audience lives in your own ad account, built from your own pixel's history. No fan data ever leaves your account; we never upload a customer list.
Exclude your converters
Build an audience of people who already streamed and exclude it — so you stop paying to reach fans you've already won.
Every release compounds
Each release feeds the same growing pool of warm fans. The more you release, the cheaper your results get.
From an ad click to a fan you keep reaching.
Connect your pixel
Add your Meta and TikTok pixel in Settings once — server-side tracking turns on, no code.
Capture clean data
Every preview and stream-click fires as a first-party event you own, deduplicated and blocker-proof.
Build the audience
From a release's analytics, one click builds a Meta Custom Audience of your warmest fans in your ad account.
Retarget + exclude
Run a campaign to that warm audience, exclude the fans who already converted, and watch cost-per-result drop.
Your pixel, your audience
Everything is built inside your own Meta and TikTok accounts. You own it and keep it if you ever leave.
Built on Meta CAPI
The same server-side protocol serious advertisers rely on — the reason your audiences don't quietly shrink.
No ad-budget markup
You pay Meta and TikTok directly for spend. git-royal never touches your ad money.
Retargeting, answered.
What is retargeting, and why does it matter for music?+
Retargeting shows ads to people who already engaged with you — previewed your song, tapped to stream — instead of cold strangers. Those warm fans are far cheaper to convert, and they're where a fanbase actually compounds. git-royal turns your release engagement into that audience automatically.
Does git-royal build the audience for me?+
On Meta, yes — one click from a release's Analytics builds a Custom Audience in your own ad account, from your own pixel's history (Pro, with your ad account connected). On TikTok you build the audience in Ads Manager for now; git-royal feeds the pixel server-side so it's full and accurate. TikTok one-click is on our roadmap.
How is this different from boosting a post?+
Boosting sprays a post at broad audiences. Retargeting reaches the specific people who showed intent on your release, with the next ask — and lets you exclude people who already converted, so you're not paying to reach fans you already won.
Do ad blockers shrink my audience?+
Much less than with a browser-only pixel. git-royal sends your events server-side through Meta's Conversions API and TikTok's Events API, so conversions a blocker would drop still land — meaning fuller, more accurate audiences to retarget.
Whose ad account and data is it?+
Yours. The audience is a rule-based Website Custom Audience built inside your own ad account, from your own pixel. No fan data ever leaves your account, and git-royal never uploads a customer list.
Do you run my ads for me?+
No — and that's deliberate. Some music-ad services run your campaigns inside their own ad account. Your pixel data is still yours, but everything that compounds inside an ad account — the campaign history, the creative performance record, the spend reputation, and Meta's optimization learning — builds up in their account, not yours. Leave, and you start from zero. git-royal never runs your ads. We build the audience in YOUR ad account, with YOUR token, and you launch from there. We don't run your ads; we make your ad account smarter.
What does it cost?+
Free to build pages, connect your pixels, and turn on server-side tracking (Meta CAPI + TikTok Events API) — all of it. Pro adds the part nobody else does: the audience built for you in your own ad account, ad-fatigue alerts, and ROAS that matches your spend to real sales. You pay Meta and TikTok directly for ad spend — git-royal never touches your ad budget.
Want the strategy behind it? Read the almost-fan and the retargeting playbook.
The parts nobody else writes about.
Is your retargeting audience full of bots?
How invalid traffic gets into an audience, what it does to your lookalikes, and how to clean it out.
How small is too small?
Meta publishes no minimum custom-audience size — the page everyone cites for “100” redirects to one that gives no number at all.
Who to exclude, and in what order
The cheapest optimisation available, and the one nobody writes about. Excluding aggressively costs you reach you never wanted.
What pixel events actually tell the optimiser
An event is a labelled example you hand a model, not a counter. Optimise for a shallow one and you train a worse model.
Lookalike audiences, properly
A lookalike is a statistical projection of your seed, not “similar people”. Contaminate the seed and you get a large, confident, wrong audience.
Ad fatigue on a small warm audience
A 2,000-person pool and a 200,000-person pool absorb the same spend at a 100:1 difference in frequency. The arithmetic is the argument.
Video vs static
Everyone states the rule. Nobody shows the evidence. Here is the mechanism, why it might be wrong, and how to test it on your own campaigns.
TikTok server-side tracking
TikTok publishes a 1,000 matched-user minimum where Meta publishes none. On Meta a thin audience is expensive; on TikTok it is unusable.
Close the loop on your ad spend.
Build a page, connect your pixel, and every release starts building the warm audience you'll retarget next.
Start 7-day free trial