Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adapty 3.x conflicting with facebook_app_events #153

Closed
PetrKubes97 opened this issue Feb 18, 2025 · 8 comments
Closed

Adapty 3.x conflicting with facebook_app_events #153

PetrKubes97 opened this issue Feb 18, 2025 · 8 comments

Comments

@PetrKubes97
Copy link

Hi, we've tried two times to upgrade Adapty from 2.x to 3.x, but both times we've seen a massive drop in the "StartTrial" counts.

I know there's https://adapty.io/docs/facebook-ads (not supported in Flutter), so I wonder if the Adapty's Facebook integration isn't conflicting with this library: https://pub.dev/packages/facebook_app_events/, resulting in no events being send at all.

We're using the automatic events... maybe Adapty disables them? 🤔

@x401om
Copy link
Collaborator

x401om commented Feb 18, 2025

Hi @PetrKubes97! Could you please clarify how you are using Adapty? Is it in full mode or observer mode? Also, I’m not sure I fully understand the issue - am I correct that after upgrading Adapty, you no longer see any “Start Trial” events being sent from Adapty to Facebook within integration?

@PetrKubes97
Copy link
Author

We're using Adapty in full mode.
We are also using the "facebook_app_events" SDK to sent automatic startTrial events to Facebook.
With version 2.x, the automatic trial events send automatically, whereas with version 3.x, we do not receive almost any.

What could be confusing:

  • I'm talking app the "StartTrial" events, which the Facebook sdk sends directly to Facebook
  • Adapty logs trial events just fine and also successfully sends them to Facebook using the Facebook api.

Right now, I'll downgrade to 2.x and see if it fixes the issue. I'll keep you updated and send you more information later.

@x401om
Copy link
Collaborator

x401om commented Feb 18, 2025

@PetrKubes97 for now, my guess is that the issue arises because we migrated Adapty to StoreKit 2, which uses a different mechanism for transaction observation. In StoreKit 1, it was enough to simply add a listener and monitor transactions. However, in StoreKit 2, transactions from SK2 purchases may not be received by an SK1 listener, and they definitely won’t be received by any SK2 listener other than the first one.

Let me do some research on how the Facebook SDK listens to transactions, and I’ll get back to you.

Just out of curiosity - since Adapty is providing Facebook with the correct events, isn’t that sufficient for your needs?

@PetrKubes97
Copy link
Author

Thank you for that!

I'm not in charge of managing the Meta campaigns, but I think my client mentioned that they had better results with optimizing ad campaigns for the event from the SDK combined with the API event, rather than just the API event.

Who knows, Meta ads is a crazy black box.

@jiridiblik
Copy link

Hi @x401om
I’m working with @PetrKubes97 on UA campaigns, combining event data from Adapty and Meta SDK for campaign optimization. When we upgraded to v3.x in production, it completely disrupted Meta campaign optimizations, and we stopped receiving postbacks for “Start Trials” and Purchases. However, once we downgraded back to v2.x, everything started working again without any issues. It would be great to investigate this ongoing issue. We’ve already experienced this twice—once in November/December last year and again yesterday with the same problem.

@x401om
Copy link
Collaborator

x401om commented Feb 18, 2025

@PetrKubes97 @jiridiblik I believe this issue explains the situation. We have to wait until Facebook adds a reporting method for StoreKit 2. Until then, you can either stay on the pre-3.x version of Adapty or try to determine why campaign optimizations are being disrupted despite having the Adapty-to-Facebook integration set up.

@PetrKubes97
Copy link
Author

Thank you! That seems like it could be the issue. I suppose we could solve this by logging the the events manually.

@x401om
Copy link
Collaborator

x401om commented Feb 19, 2025

@PetrKubes97 in that case I am going to close the issue. Please reopen it or email us to [email protected] if you need help.

@x401om x401om closed this as completed Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants