I’ve recently integrated the Meta Ads integration as per your documentation and triggered several purchase events while running the app in development mode. However, I’m not seeing any indication that these events are being sent to Meta—neither in the RevenueCat dashboard nor on Meta’s side.
A few additional details:
I haven’t implemented the ATT prompt yet, so users have not granted tracking permission.
From the docs, it appears that the IDFA is optional and RevenueCat should still be able to forward events without it.
The app is using RevenueCat’s anonymous ID and I’ve verified that purchases are correctly being tracked in the RevenueCat dashboard.
Could you help clarify:
Are events from development builds or sandbox purchases forwarded to Meta Ads?
Is ATT permission mandatory for Meta Ads event forwarding in practice, even if IDFA is optional?
Are there any known limitations or delays when viewing these events in the dashboard or Meta Events Manager?
Let me know if there’s anything I might have missed in the setup.
@gregzeng glad this is working for you! We’re currently updating the docs for the Meta Ads integration. Here’s what we’ll be clarifying:
Either the $idfa or $fbAnonId attribute must be set for a customer in order for their App Store events to be dispatched from RevenueCat to Meta
If the Send events when ATT consent is not authorized setting is enabled on the Meta Ads Integration page in your RevenueCat Dashboard, the $attConsentStatus attribute is not required
I have a kid’s app so naturally I had to disable IDFA but the value proposition I saw in Revenue Cat Meta Ads integration was that I no longer have to rely on IDFA to record subscription events accurately by enabling Send events when ATT consent is not authorized. However, despite that I am seeing that despite getting sales, the events are not being associated with the ad sets running in my campaign. A. couple of them recorded here and there but most of them are not attributed to the ad sets responsible for them. Strangely, these events are being recorded as “subscribed” in events manager. And even more strangely, no events are showing up on meta ad revenuecat integration dashboard.
Fyi..I am using facebook SDK within my app with with explicit call - Purchases.shared.attribution.collectDeviceIdentifiers() in my App Delegate. What am I missing? You mentioned something about $fbAnonId. How do I enable that?
Make sure to remove all client side tracking of revenue. Since RevenueCat will be sending events for all revenue actions, tracking purchases with the Meta SDK directly can lead to double counting of revenue in Meta Ads Manager.
You can disable automatic In-App Purchase event logging from the Meta SDK or from your Meta app dashboard. Go to the iOS/Android card under Settings > Platform > Log In-App Events Automatically > No
In order for RevenueCat to dispatch iOS events to the Meta Conversions API, the $idfa or $fbAnonId attribute must be set. Note that events with a zero’d IDFA (e.g. 00000000-0000-0000-0000-000000000000) are not dispatched by our integration.
To set the $fbAnonId, you can use the example from our integration guidePurchases.shared.attribution.setFBAnonymousID(FBSDKCoreKit.AppEvents.shared.anonymousID)
I’m facing a somewhat similar issue. I can see the sandbox transactions being recorded properly on revenue cat with FB anon ID, idfv and idfa all being tracked properly
But on the meta ads manager side, in test events in data sources, there doesn’t seem to be a way to ensure that the events are being tracked properly by meta
@gwszeto if you open the Meta Ads integration page in RevenueCat, you should be able to see a list of recent events dispatched from RC to Meta. Clicking on each event reveals its details. In your case, it appears that the most recent two events (including the one in your screenshot) have failed due to an invalid Sandbox Datasource ID or corresponding Token.
Hey @chris_perriam , thanks for the help on this! I’m now running into another issue where I’m seeing new users purchasing the weekly plan and starting the trial on revenue cat and I can see the events being sent through from the meta ads integration tab in revenue cat
But on my meta ads manager, I don’t see the conversions popping up at all
Wanted to know what might be causing this issue here of the conversions not showing up on meta ads manager
I can see the dispatched RevenueCat events appearing in the events manager activity log
But when I set the conversion event to being “Start trial” in meta ads, none of the conversions show up on the meta ads despite them showing on the Revenue Cat dashboard
@ludwig-henne it did eventually start reporting, I believe it’s just a volume issue where meta won't report until it sees a certain number of trials or people accepting/not accepting the ATT?
I’m not entirely sure why it started working, but I’m switching towards using an MMP to start tracking this as the meta ads integration doesn’t report to SKAN/AEM
@gwszeto and @ludwig-henne having the same issue on both android and ios - let me know if you make an progress on it!
Hi RevenueCat Support Team,
I’ve recently integrated the Meta Ads integration as per your documentation and triggered several purchase events while running the app in development mode. However, I’m not seeing any indication that these events are being sent to Meta—neither in the RevenueCat dashboard nor on Meta’s side.
A few additional details:
I haven’t implemented the ATT prompt yet, so users have not granted tracking permission.
From the docs, it appears that the IDFA is optional and RevenueCat should still be able to forward events without it.
The app is using RevenueCat’s anonymous ID and I’ve verified that purchases are correctly being tracked in the RevenueCat dashboard.
Could you help clarify:
Are events from development builds or sandbox purchases forwarded to Meta Ads?
Is ATT permission mandatory for Meta Ads event forwarding in practice, even if IDFA is optional?
Are there any known limitations or delays when viewing these events in the dashboard or Meta Events Manager?
Let me know if there’s anything I might have missed in the setup.
Thanks a lot for your help!
Page 1 / 1
Just published the update — purchase events are now showing up in Meta Ads. Seems all good now!
@gregzeng glad this is working for you! We’re currently updating the docs for the Meta Ads integration. Here’s what we’ll be clarifying:
Either the $idfa or $fbAnonId attribute must be set for a customer in order for their App Store events to be dispatched from RevenueCat to Meta
If the Send events when ATT consent is not authorized setting is enabled on the Meta Ads Integration page in your RevenueCat Dashboard, the $attConsentStatus attribute is not required
I have a kid’s app so naturally I had to disable IDFA but the value proposition I saw in Revenue Cat Meta Ads integration was that I no longer have to rely on IDFA to record subscription events accurately by enabling Send events when ATT consent is not authorized. However, despite that I am seeing that despite getting sales, the events are not being associated with the ad sets running in my campaign. A. couple of them recorded here and there but most of them are not attributed to the ad sets responsible for them. Strangely, these events are being recorded as “subscribed” in events manager. And even more strangely, no events are showing up on meta ad revenuecat integration dashboard.
Fyi..I am using facebook SDK within my app with with explicit call - Purchases.shared.attribution.collectDeviceIdentifiers() in my App Delegate. What am I missing? You mentioned something about $fbAnonId. How do I enable that?
Make sure to remove all client side tracking of revenue. Since RevenueCat will be sending events for all revenue actions, tracking purchases with the Meta SDK directly can lead to double counting of revenue in Meta Ads Manager.
You can disable automatic In-App Purchase event logging from the Meta SDK or from your Meta app dashboard. Go to the iOS/Android card under Settings > Platform > Log In-App Events Automatically > No
In order for RevenueCat to dispatch iOS events to the Meta Conversions API, the $idfa or $fbAnonId attribute must be set. Note that events with a zero’d IDFA (e.g. 00000000-0000-0000-0000-000000000000) are not dispatched by our integration.
To set the $fbAnonId, you can use the example from our integration guidePurchases.shared.attribution.setFBAnonymousID(FBSDKCoreKit.AppEvents.shared.anonymousID)
I’m facing a somewhat similar issue. I can see the sandbox transactions being recorded properly on revenue cat with FB anon ID, idfv and idfa all being tracked properly
But on the meta ads manager side, in test events in data sources, there doesn’t seem to be a way to ensure that the events are being tracked properly by meta
@gwszeto if you open the Meta Ads integration page in RevenueCat, you should be able to see a list of recent events dispatched from RC to Meta. Clicking on each event reveals its details. In your case, it appears that the most recent two events (including the one in your screenshot) have failed due to an invalid Sandbox Datasource ID or corresponding Token.
Hey @chris_perriam , thanks for the help on this! I’m now running into another issue where I’m seeing new users purchasing the weekly plan and starting the trial on revenue cat and I can see the events being sent through from the meta ads integration tab in revenue cat
But on my meta ads manager, I don’t see the conversions popping up at all
Wanted to know what might be causing this issue here of the conversions not showing up on meta ads manager
I can see the dispatched RevenueCat events appearing in the events manager activity log
But when I set the conversion event to being “Start trial” in meta ads, none of the conversions show up on the meta ads despite them showing on the Revenue Cat dashboard
@gwszeto having the exact same issue. did you find a solution yet?
→ events manager shows events
→ ad campaign optimizing for trial start shows no results (I’m 99% sure some trials came from the ads, so something seems off)
@ludwig-henne it did eventually start reporting, I believe it’s just a volume issue where meta won't report until it sees a certain number of trials or people accepting/not accepting the ATT?
I’m not entirely sure why it started working, but I’m switching towards using an MMP to start tracking this as the meta ads integration doesn’t report to SKAN/AEM
@gwszeto and @ludwig-henne having the same issue on both android and ios - let me know if you make an progress on it!
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
