Android app not sending Conversions API events to Stape

Hi, I’m trying to implement the Conversions API for our Android app with Stape. I’ve followed the Meta instructions
And the [How to set up Meta Conversions API Gateway - Stape](https://Stape instructions)
But I’m not receiving the Conversion API events, neither in Meta Events Manager, neither Stape.
I’ve double checked the Events that are being sent from the Android App, and I don’t see anything being sent to Stape. The exact step
The default Facebook SDK events are being sent successfully to Meta, for example events fb_mobile_install, fb_sdk_initialize

Any suggestions? Thanks!

@Linas777

  1. Why are you not happy with Facebook SDK, is there any reason to move away from it?

  2. Meta Conversion API Gateway (the one you linked on Stape) is a product that works in conjunction with web-bases JS pixel and has nothing to do with apps and SDKs

  3. Meta instruction you’ve linked are on how to report app events to CAPI.

There is lack of coherence in what you’re trying to do here, please provide more details so that we can untie this knot.

Hi Dan,
Thanks for the reply. Let me give some more info about our goals:
Marketing team has requested the mobile team to implement Conversions API to send more data to Meta about our users to enrich Meta’s tracking. Details like email, city, phone model etc. This extra data would appear in our third-party Adjust platform.
We already have our mobile app connected to a Meta dataset, and we have some events coming in, since we have Facebook SDK implemented. In the Meta dataset, there is an option to implement the Conversions API either directly, using a partner or using the Conversions API gateway. Using the gateway seemed the easiest option. That’s where Stape came in. The setting in question:

My expectation was that we would start receiving events from Meta in Adjust with more data, like email, city etc.

Hey Linas, again, I’m seeing contradictions, so forgive me being obnoxious:

Marketing team has requested the mobile team to implement Conversions API to send more data to Meta about our users to enrich Meta’s tracking. Details like email, city, phone model etc. This extra data would appear in our third-party Adjust platform.

if Adjust holds the extra data you want to send, it is Adjust who needs to receive signal and then report to CAPI via their integrations (which they do have)

In the Meta dataset, there is an option to implement the Conversions API either directly, using a partner or using the Conversions API gateway. Using the gateway seemed the easiest option. That’s where Stape came in. The setting in question:

Gateway normally ties to browser pixel, it can’t automatically listen for your SDK events. The ‘exact setup’ you linked suggests that (well, maybe not explicitly but do check the testing part).

My expectation was that we would start receiving events from Meta in Adjust with more data, like email, city etc.

you expect events to come from Meta to Adjust? Are you sure there’s no mix-up?