Connect your Meta ad account for retargeting
Retargeting turns the fans who previewed or clicked to stream your release into the warmest, cheapest audience to reach again. git-royal builds it inside your own ad account, from your own pixel. Connect once — then every release is a single click.
The short version: git-royal already forwards your funnel events — previews, clicks to stream — to your Meta pixel. Retargeting takes those real, engaged fans and packages them as a Custom Audience you can advertise to again. No fan data ever leaves your account; the audience is built in your ad account, from your pixel's own history.
To do that, git-royal needs permission to create audiences in your account. You give it three values — a Pixel ID, an Ad account ID, and a Marketing API token — and paste them into Settings once.
Warmest fans
Built from people who actually previewed or clicked to stream — not cold traffic.
Your account
The audience lives in your own ad account, from your own pixel. You own it.
One click after
Connect once. Building an audience for any release is then a single button.
What you need.
A Meta Business account (business.facebook.com) that contains your ad account and your pixel. If you've only ever “boosted” posts from a Facebook Page, you'll first need to set up a proper ad account in Business settings — the retargeting tools require it.
Your pixel connected to your git-royal pages so it has events to build from. If you haven't done that yet, start with the Meta Conversions API setup guide. Connecting here takes about 10 minutes.
Get your three values + connect
- 1
Your Pixel ID
Go to business.facebook.com → Business settings → Data sources → Datasets (older menus call this “Pixels”). Click your pixel — the ID (a long number) appears right under its name. You can also find it in Events Manager, under the pixel name.
- 2
Your Ad account ID
Business settings → Accounts → Ad accounts → click your ad account. The Account ID is the number shown (e.g.
1234567890). In git-royal you can paste it with or without theact_prefix. - 3
Your Marketing API token
This is a secure key that lets git-royal build audiences in your account. The reliable way is a System User token:a. Business settings → Users → System users → Add (name it something like
git-royal, role Admin).b. Click Add assets → Ad accounts → select your ad account → turn on Manage / full control → Save. ⚠️ Don't skip this — assigning the ad account here is what lets the token actually work. It's the #1 thing people miss.c. Click Add assets → Pixels/Datasets → select your pixel → Save.d. Click Generate token → choose your app → check the permissionsads_managementandads_read→ Generate.e. Copy the token now — Meta shows it only once.No Meta app to generate the token under? Create one free at developers.facebook.com → My Apps → Create App → “Create & manage ads with Marketing API.” You only need it to mint the token. - 4
Paste them into git-royal
In git-royal, go to Settings → Meta, enter your Pixel ID, Ad account ID, and Marketing API token, and save. A green “· connected” confirms the token saved. It's stored securely and never shown in your browser again.
- 5
Build your first audience
Open a published release page → Analytics. Find the Retargeting audience card → pick a tier (start with Clicked to stream (warmest)) → Build audience. You'll see “Audience created in Meta — ready to target,” and the row is tagged In Meta. Check Ads Manager → Audiences — it appears there, “Populating” for a little while as Meta matches your pixel history, then sized.
- 6
Use it in a campaign
In Meta Ads Manager, create a campaign (objective Traffic, or Sales optimizing your stream-click event). At the ad set level, under Audiences → Custom audiences, add your “Clicked to stream” audience. Recommended: also build an audience of people who already streamed and add it as an exclusion, so you're not paying to reach fans you've already converted. Add your creative and smart link, set a budget, and publish.
Your Marketing API token is like a password for your ad account — git-royal stores it encrypted and server-side, and you can revoke it anytime from Business settings → System users → Revoke tokens. Never share it in an email or chat.
If something goes wrong.
“Object with ID act_… does not exist / missing permissions.”+
The token can't reach your ad account. Almost always: the ad account wasn't assigned to your System user with Manage/full control (step 3b) — fix that first; or the token is missing the ads_management permission — regenerate it with that box checked; or the token saved in git-royal is an old one — paste the freshest token and save again.
How do I check a token quickly?+
Paste it into Meta's Access Token Debugger (developers.facebook.com/tools/debug/accesstoken) and confirm the scopes include ads_management.
Some rows in the Retargeting card say “Failed.”+
Those are earlier attempts from before the connection was set up. Harmless — the one tagged 'In Meta' is the live audience.
Do I have to build the audience again for each release?+
No re-connecting — you connect once. You do click 'Build audience' per release (from that release's Analytics), because each audience is scoped to that release's engaged fans.
Will any of my fans' data leave my account?+
No. The audience is a rule-based Website Custom Audience that Meta populates from your own pixel's history, inside your own ad account. git-royal never uploads a customer list.