صقور في الملعب، وصقور في المدرجات 🦅🇸🇦
من المدرجات، من البيت، أو مع الأهل والأصحاب… كلنا خلف صقورنا 💚
شاركنا فرحتك الخضراء وخلّونا نعيشها سوا
#السعوديه_الامارات#السعودية#خليجي٢٧
I’m going to say this quietly…
These are the top 5 consumer app niches with the lowest app store competition right now:
1. Female health
2. Hyrox Training
3. Niche Nutrition
4. Productivity
5. Creator utility
Thank me later
The 1AM frustration trying to use AppsFlyer, Meta ads, and Tiktok ads to promote my react native app.
SKAN, IDFA, and a hundred more annoying configurations to fill with no clear guidance whatsoever 😵
I am not sure if relying on SDK - Meta communication alone is the recommended approach. To my understanding, creating an integration between RevenueCat & Meta (assuming you rely on Meta Ads) is a more reliable approach.
For your campaign, you need to pick a target. If it is app installs - which seems to be the case in your scenario(?), all ad sets within that campaign has to share the same target. That is the target Meta optimize your campaign for. You unfortunately cannot change this later on. If you want to change it to subscription start, you need to start a new campaign, which unfortunately starts learning from scratch. Your SDK surely sends subscription start events as well as long as you do not actively block them, but what matters here is your campaign target.
Here is the deal form my earlier notes which may help you as well: Three data channels connect your app, RevenueCat, Apple, and Meta:
1) Device => Meta (SDK)
The app has Meta's SDK embedded. When a user grants tracking permission (ATT prompt), the SDK sends their advertising ID and app-open events directly to Meta. If they decline, nothing is sent from the device.
2) RevenueCat => Meta (server-to-server)
When a user subscribes, RevenueCat sends a "Subscribe" event to Meta via their Conversions API, which is a server to server integration, and no device involved here. This works for all users regardless of their tracking choice. For users who declined tracking, the advertising ID is omitted and a flag (advertiser_tracking_enabled=0) tells Meta to use the data only for aggregated measurement, not ad personalization. But this is still useful for Meta to optimize the search for your case.
3) Apple => Meta (SKAdNetwork)
Apple independently sends Meta an anonymous, aggregated signal confirming someone installed the app from their ad. No user identifiers, delayed 24–48 hours. This always works regardless of the user's tracking choice.
Summary: Meta gets install attribution from Apple, app engagement from the SDK (opted-in users only), and subscription revenue from RevenueCat; enough to measure campaign performance and optimize ad delivery.
I am a fan of your channel and relatively long term follower. You were stuck at 70K, but saw recently that you actually hit 93K, which I assumed happened with the help of ads. This message sounds a bit like I am educating you but if this jump has happened with the help of ads, you likely have nothing to learn from me. :)
Keep up the good work. You are an inspiration.