If you run Meta app-install or app-event campaigns, you need Meta Ads data alongside your attribution to see true ROAS. VibesFlyer connects Meta Ads and brings campaign spend and conversions into your normalized metrics.
Before you start
- A Meta Business account running app campaigns for your app.
- Your VibesFlyer project created, ideally with AppsFlyer connected for attribution.
Connect
Have your agent call connect_provider with provider meta for your project. VibesFlyer auto-discovers the ad accounts and campaigns available to your business account.
What you get
- Campaign + ad-set data — spend, installs, and conversions, pulled via
get_meta_campaigns. - ROAS — Meta spend reconciled against in-app revenue, surfaced in normalized metrics.
How attribution fits
For mobile, the install-to-campaign link usually comes from your MMP (AppsFlyer) plus Meta's own SDK/SKAdNetwork signals. VibesFlyer combines the ad-account spend from Meta with the attributed conversions so the ROAS number is consistent with your other channels rather than each platform's self-reported figure.
Verify
Confirm campaigns appear via get_meta_campaigns, then call validate_tracking. Meta spend and ROAS then sit beside Firebase product metrics and AppsFlyer attribution in one normalized view.
iOS note
Expect SKAdNetwork's delayed, aggregated reporting on iOS. Lower-than-web fidelity is normal — VibesFlyer's tracking-health checks account for it so it isn't flagged as a gap.