๐BookWatch was voted the #1 ๐ฅ pick at Github AI night in SF!
And I'm giving away FREE Lifetime Premium Access to the BookWatch app, as a token of gratitude to the incredible SF startup community.
Having arrived from Greece just two weeks ago, I'm overwhelmed by the warmth and support of the San Francisco startup ecosystem. Your encouragement has been truly inspiring!
For those unfamiliar with BookWatch, we are creating the first visual library. Our platform offers animated summaries of top non-fiction books, tailored for visual learners.
๐ Exclusive Offer: While our annual subscription typically costs $89, I'm extending a special offer to my LinkedIn network (available only for the first week of this post).
To claim your FREE Lifetime Pro Access:
1. Follow me
2. Comment on this post
3. Send me a dm
I'll personally ensure you receive your lifetime pro access at no cost!
@czypant And I have done the same thing with fb sdk and with deep linking and matching users with ip etc from web to app this is not a new method it exists years. But it always underperforms.
Your product's headline is literally talking about web campaigns brother.
Your original post was saying how to run app install campaigns with "fully enriched mobile attribution in 5 mins"
Your own docs prove my point.
You are not running native app install campaigns. Your docs say to run Meta Sales campaigns with Website as the conversion location, send users to a landing page, then redirect to the App Store.
That is web2app.
Useful? Yes.
Same as app campaigns? No.
In my experience normal app promotion campaigns optimizing for purchases/trials with AEM perform better than Web2App.
Also my issue was with your original post that says just connect revenuecat.
RevenueCatโs Meta integration is not magic identity resolution.
It works like this:
You install the Meta SDK, RevenueCat collects allowed attribution/device data like fbAnonId, IDFA if available, IDFV, IP, etc., and then RevenueCat sends subscription events to Meta through App Events API / Conversions API.
Trial Started maps to StartTrial.
Initial Purchase / Trial Converted / Renewal maps to Subscribe.
They also tell you to disable Meta SDK purchase tracking because RevenueCat will send the revenue events server-side, otherwise you double count.
So what is RevenueCat doing?
A better event pipeline.
Server-side subscription events.
Renewals and trial conversions.
Dedupe / reporting convenience.
Not magic ATT bypassing.
And yes, this is the same AEM world.
AEM is Metaโs privacy-limited measurement/optimization protocol for iOS when IDFA is unavailable. RevenueCat feeds Meta the events and identifiers Meta can use; Meta decides AEM eligibility/matching quality.
If ATT is accepted, stronger deterministic signals like IDFA can be used.
If ATT is denied, events can still be sent and used through privacy-limited AEM-style measurement, but not raw user-level tracking.
So your product is doing the same category of thing: SDK/CAPI events + allowed matching signals.
It cannot magically skip ATT or Appleโs rules.
App store doesnt review our latest update for 8 days now, anyone knows what to do? I already contacted support multiple times but nothing. @Apple@AppStore@AppStoreGames