5 min read
Meta Ads to RevenueCat: Find Campaigns That Produce Paying Subscribers
The connection is not one universal attribution switch. The Meta SDK, privacy permission, customer identifiers, RevenueCat delivery path, campaign settings, and duplicate event rules all affect what Meta can match and report.
· Grometrics Team
Meta Ads can drive an app install while RevenueCat records the trial, purchase, renewal, and cancellation. Connecting the two lets a mobile app team judge campaigns by paying subscribers instead of installs alone.
The connection is not one universal attribution switch. The Meta SDK, privacy permission, customer identifiers, RevenueCat delivery path, campaign settings, and duplicate event rules all affect what Meta can match and report.
Assign each system one job
The Meta SDK provides app side and device context. RevenueCat manages subscription lifecycle events and can send eligible events to Meta even when the app is closed. Meta applies its own matching, attribution, and campaign reporting rules.
RevenueCat delivery means Meta accepted an event. It does not guarantee campaign credit, optimization eligibility, or the same number shown in your payment backed report.
- Meta SDK for supported app side signals.
- RevenueCat for subscription lifecycle events.
- Meta for provider attribution and optimization.
- Your revenue report for payment backed campaign value.
Set identifiers before the purchase
RevenueCat must have the required customer identifiers when it processes the event. The exact requirements depend on platform and integration path. Empty or zeroed advertising identifiers do not provide useful matching.
When privacy rules permit, set supported identifiers and matching attributes before the first purchase. Late values cannot repair every event that was already delivered without them.
- RevenueCat App User ID.
- Supported device advertising identifier when available.
- Facebook anonymous identifier where required.
- Email or phone only when collected and permitted.
- Final campaign fields from an attribution provider when used.
Choose one purchase delivery path
RevenueCat supports Meta delivery paths including the Conversions API. The Meta SDK can also log purchase events. Sending the same purchase through independent paths without coordinated deduplication can double count revenue.
RevenueCat documents that its SDK integration and the Meta SDK do not coordinate a shared event identifier automatically. Decide which system owns subscription purchase delivery and disable conflicting automatic logging when required.
- List every system that sends purchase events.
- Choose one owner for each event meaning.
- Confirm the event name and value mapping.
- Test duplicate behavior before using campaign totals.
Keep trials, conversions, and renewals distinct
A trial start, trial conversion, initial purchase, and renewal answer different growth questions. Send and report them as distinct lifecycle events.
Campaign quality appears over time. A campaign with many trials can still be weak when trial conversion and renewal are low. Group RevenueCat value under the original acquisition context for cohort analysis.
- Trial starts by campaign.
- Trial to paid conversion.
- Initial subscription revenue.
- Renewal revenue.
- Refunds and cancellations.
- Net customer value.
Respect iOS measurement limits
Meta app promotion campaigns may use privacy preserving systems such as SKAN or Aggregated Event Measurement alongside direct event delivery. RevenueCat does not configure those systems or update SKAN conversion values for you.
Do not claim that server delivery removes App Tracking Transparency limits. Report what was observed, what Meta attributed, and how much subscription revenue RevenueCat recorded. Keep missing campaign detail visible.
- ATT consent state where applicable.
- Event delivery result.
- Meta matching and attribution result.
- RevenueCat subscription value.
- Unattributed revenue share.
Accepted is not attributed: A successful provider response confirms delivery. Meta still decides whether the event can be matched, attributed, reported, or used for optimization.
Compare the two reports without forcing agreement
Meta can credit a campaign according to its attribution window and modeling rules. RevenueCat can record the subscription event and value. Your payment backed report can connect known acquisition context to the same customer. These views can differ for valid reasons.
Compare campaign spend, Meta attributed subscribers, RevenueCat subscribers, initial revenue, renewal revenue, refunds, and unattributed value. Investigate the gap by identifier availability, event duplication, attribution window, privacy state, and campaign eligibility.
- Provider attributed subscriber count.
- Payment backed subscriber count.
- Initial and renewal revenue.
- Duplicate event risk.
- Unmatched and unattributed share.
Verify with one controlled subscriber
Use a test path supported by the configured integration. Confirm identifiers exist before purchase, one purchase event reaches Meta, RevenueCat records the subscription, and no duplicate event appears from the SDK.
Grometrics Meta Ads revenue attribution adds payment backed campaign reporting so teams can compare Meta spend with real subscriber revenue and refunds.
Sources
CONNECT YOUR PAYMENTS
Grometrics works with Stripe, RevenueCat, Gumroad, Shopify, and more. Setup takes about 5 minutes.
Connect payments →See the full page:
Meta Ads revenue attributionRELATED POSTS