Android Meta Ads (start trial) with RevenueCat - No results

[fvates]

I created a new meta campaign with start trial as app event.
I'm using the RevenueCats implementation to forward the event details to meta which are sent correctly. However, I'm not seeing any results in my campaign. The events manager already shows some start trial events but it doesn't show any event match quality.

Anyone noticed something similar? Did it show up at some point? The campaign is now running since 8 days.

I didn't install the Meta SDK, the RC implementation mentions that i only have to send the Purchases.sharedInstance.collectDeviceIdentifiers so nothing about any meta ids specifically.

 

[Jack811]

May I ask why you decided to use RC event for meta campaign? Is there any benefit to doing so instead of using Meta SDK or MMP event?

 

[davamosk]

Meta Ads | In-App Subscriptions Made Easy – RevenueCat

With our Meta Ads (formerly Facebook Ads) integration you can:

www.revenuecat.com

First thing you have to do to have the campaigns running properly is to have the meta SDK. I'm 100% sure that you are not seeing conversions because the setup is simply not ready.

 

[fvates]

May I ask why you decided to use RC event for meta campaign? Is there any benefit to doing so instead of using Meta SDK or MMP event?

I really don't like having the SDK in the app, it bloats it for no reason and adds privacy concerns.. so I thought as long as I don't have to, I won't

 

[fvates]

Meta Ads | In-App Subscriptions Made Easy – RevenueCat

With our Meta Ads (formerly Facebook Ads) integration you can:

www.revenuecat.com

First thing you have to do to have the campaigns running properly is to have the meta SDK. I'm 100% sure that you are not seeing conversions because the setup is simply not ready.


View attachment 59

I saw that but I think this is for iOS only. If you scroll down, you see that iOS needs to set the Purchases.shared.attribution.setFBAnonymousID


But Android doesn't..



So it feels like I don't have to..

I also asked the RC internal AI about it and it also confirmed that i don't need it..

**Short answer: No — on Android you don't need the Meta SDK or `setFBAnonymousID` to get proper attribution.** The Kotlin setup doesn't show it because the Facebook anonymous ID (`$fbAnonId`) is an **iOS-only** identifier.

Here's how it breaks down per the [Meta Ads attribution docs](https://www.revenuecat.com/docs/integrations/attribution/meta-ads):

**What Meta matches on, by platform:**
- **iOS:** `$fbAnonId` *or* `$idfa` (plus ATT consent)
- **Android:** `$fbAnonId` *or* `$gpsAdId` (Google Advertising ID)

So on Android, the primary identifier is **`$gpsAdId`**, which you collect with:

```kotlin
Purchases.sharedInstance.collectDeviceIdentifiers()
```

That's the call that matters for Android attribution. The `$fbAnonId` path only adds value on iOS (where it can substitute for the IDFA when ATT isn't authorized), and `setFbAnonymousId()` requires the Meta SDK to actually obtain that ID.

**A few important notes:**
- Call `collectDeviceIdentifiers()` **after** `Purchases` is configured and **before** the first purchase.
- Since Play Store policy changes, **Android ID is no longer collected** (SDK 6.9.8+ / 7.11.1+) — Google's Advertising ID is now the primary device identifier on Android, so make sure you're on a current SDK version.
- If you *do* install the Meta SDK for other reasons, **disable its automatic in-app purchase event logging** (Settings → Platform → Log In-App Events Automatically → No) so you don't double-count revenue, since RevenueCat sends the purchase events.

**Bottom line:** For Android-only Meta attribution, `collectDeviceIdentifiers()` is what you need. The Meta SDK + `setFBAnonymousID` is optional and primarily relevant for iOS. Want me to check which SDK version your project is running to confirm you're past the Android ID deprecation cutoff?

 

[davamosk]

I have never faced this before as normally everyone goes with SDK or MMP.
If you are following the calls that RC says in their docs and still see zero results, I'd just go with the SDK which is very easy to implement. I understand your concerns with the app size and the privacy but nowadays, privacy is something everyone deals with and the bloating effect is not that concerning for your Android score.