Meta Ads
Forward installs, trials, and purchases to Meta's Conversions API.
The Meta integration reads spend, impressions and engagement from your Meta ad accounts into the SignalSeal dashboard, and writes events to Meta's Conversions API (CAPI) so campaigns optimize against installs, trials and revenue.
You'll need an admin role in the Meta Business that owns the ad account, plus access to the pixel/dataset you want events sent to.
What's exchanged
SignalSeal pulls spend, impressions, clicks, link clicks, reach and frequency per ad account.
For the write side, you map your SignalSeal source events to Meta CAPI event names in Event mapping:
- Source events - the SDK events (
INSTALL,LOGIN,SIGN_UP,REGISTER,START_TRIAL,SUBSCRIBE,ADD_TO_CART, …), plus therc_*/sw_*events if you've connected RevenueCat or SuperWall. - Meta side - any CAPI event name. The picker offers the standard ones:
signalseal_install,CompleteRegistration,StartTrial,Subscribe,Purchase,AddToCart,InitiateCheckout,AddPaymentInfo,ViewContent,Search,Lead,Login.
Connect Meta
Start the connection
In SignalSeal: app → Ad Networks → Add ad network → Meta → Connect with Meta. Sign in with an account that has admin access to the Business that owns the ad account and approve the permissions.
Pick the ad account
After the redirect, pick the ad account this app spends from. You can add more later.
Pick the dataset and add a CAPI token
In the wizard, pick the pixel/dataset to send app events to. If it's missing, check it's owned by the same Business and that you have admin access.
In Meta Events Manager, open that dataset → Settings → Conversions API → Generate access token. Copy the token (Meta won't show it again), paste it into the wizard, and click Validate - SignalSeal makes a test call to confirm it works.
(Optional) Add a Test Event Code
To check events in Meta's Test Events tab before going live, paste your test event code - SignalSeal tags every event with it while it's set. Clear the field when you're done.
Map your events
Last wizard step: for each source event you want forwarded, pick the Meta event name to send it as. A common setup:
| SignalSeal source event | Meta CAPI event |
|---|---|
INSTALL | signalseal_install |
SIGN_UP / REGISTER | CompleteRegistration |
START_TRIAL, rc_trial_started, sw_trial_started | StartTrial |
SUBSCRIBE, rc_subscription_started, sw_subscription_started | Subscribe |
rc_trial_converted, rc_renewal, sw_trial_converted | Subscribe |
Run your Meta campaign
SignalSeal reports installs and conversions to Meta on the website surface, so you run a normal website-conversion campaign whose ad link is a SignalSeal link (it redirects to the App Store or Play Store). Meta optimizes it like any website campaign; in practice it drives app installs, and on iOS it doesn't depend on ATT or SKAdNetwork.
One-time, in Meta Events Manager for the dataset you connected:
- Under the "Confirm custom event(s)" prompt: Review events → I acknowledge,
select the events that start with
signalseal_, and Confirm them. - Settings → Traffic Permissions - Websites → Create an allow list and add
m.signalseal.net.
Then build the campaign:
Objective and conversion
Objective: Sales. Conversion location: Website only. Pick the
same dataset you connected in SignalSeal, then choose the
optimization event - one you've mapped (signalseal_install,
Subscribe, Purchase, …).
Placements (ad set level)
Placements → Show more settings: select Mobile only and the operating system this app runs on. Turn Audience Network off.
Ad link (ad level)
Copy the SignalSeal ad link from Ad Networks → Meta in SignalSeal and paste it into the Website URL field.
signalseal_install only shows up as a column in Ads Manager if it's the
campaign's optimization event.
Test it
Trigger a mapped event on a real device (often a sandbox purchase) - it shows in Live Feed within seconds. Check Audit → Postback log filtered by Meta: a green status means Meta accepted it. In Events Manager, check the Test Events tab (if you set a code) or Overview a few minutes later.
Troubleshooting
- Token rejected at validation - a CAPI token only works for the dataset it was generated from. Generate it from the same dataset you picked in SignalSeal.
- Connection went red - SignalSeal's System User was likely removed from the Business. Reconnect from Settings → Ad Accounts.
- Events accepted but campaigns not optimizing - Meta needs ~50 conversions per ad set per week. If you just launched, give it a few days.
| Error | Meaning | Fix |
|---|---|---|
Invalid access token | The CAPI token is wrong or revoked. | Generate a new one in Events Manager and paste it in. |
Auth invalid on the ad account | The OAuth connection was revoked. | Reconnect Meta from Settings → Ad Accounts. |