API conversions doesn't work

[g-apparence]

Hi,

In order to use meta ads properly with revenuecat we have to use the meta ads integration
The problem is that the event sent by the current integration seems not working properly with iOS.

Once you start getting some trial you won't be able to start a new ads campaign.
When you open your meta event manager you will get the error
"Advertiser Tracking Enabled out of range"

After searching for hours on this (and wasted a bit of money on useless ads)
it seems that the problem is that the wrong value is sent

The official meta conversion documentation says that we must send 0 or 1
At first i expected this was the same then I see many people reporting changing that and that message was actually this.
Javascript don't convert true or false to 0 or 1.
https://developers.facebook.com/docs/marketing-api/conversions-api/app-events

"advertiser_tracking_enabled": 1, // => instead of true
"application_tracking_enabled": 1 , // => instead of true

Even if meta says ok we save the event
This doesn't mean that the event is usable in ads campaign

I think the fix is pretty easy
If you could please really fix this this would be amazing

---

Secondly meta ads really like when we send the same conversion from the API AND from the mobile sdk
So for this we need to have access to the order-id you send through the conversion API.
But right now we can't have it

I'd be happy to help if you need any interview on this
I see many developers going on other solutions because of this.
We can make working ads campaign without using an MMP.

[RCGitBot]

👀 We've just linked this issue to our internal tracker and notified the team. Thank you for reporting, we're checking this out!

[WesleyClarkRC]

Hi! Thank you for raising this issue with us. We actually had another developer raise this issue with us already and we are working on this issue. We already have a fix behind a feature flag in order to use the 1 instead of true for the fields you listed. Would you like to have the feature flag enabled? I will need the project ID, which can be found in the Project Settings in the Dashboard. We are continuing to investigate the causes of this issue as well as we are not fully convinced that these fields alone are the issue.

On top of this, to give some context as to why we have not fully released this fix immediately, Meta has some contradictions within their documentation regarding the appropriate values to use. For example, this documentation says to use a boolean, but then provides 0 and 1 as their examples, so we are studying the impact in order to confirm.

[g-apparence]

@WesleyClarkRC thanks a lot for your answer
here is my project id : c26cb3b3

Would love to beta test this
I currently have a ready to launch trial campaign and need this to work to be effective.

Meta documentation isn't clear I agree with you. I noticed this by checking multiple sources and implementations.
The easiest for me is to send these events with test purchase and check the eligibility of those events within the meta events manager configuration. (eligibility test for iOS)

[g-apparence]

Do you have any updates on this?
I just wanted to follow up, as this issue is currently blocking my progress.

[g-apparence]

Hi @WesleyClarkRC Do you have any news?

[g-apparence]

@WesleyClarkRC up @RCGitBot

[Jethro87]

@g-apparence I've just enabled the feature flag for your project. I'll follow up further via DM, thanks!