Updating / rejecting firebase conversion events for App campaigns

[Anirudh Beria]

Hi, I am running a Android-App campaign, in which bidding is based on the in-app-action-value. This value / conversion is reported through firebase-event from the user's mobile. What amount to report is being fetched by our servers. Now I have some incorrect values reported, which I want to update. How do I do that? This can be done in case of Enhanced-conversions by APIs (click imports), but I couldn't find any way to do this for this scenario.

Also I tried this: Since I have the associated gclids also, I tried to change the way reporting is done, from firebase-events to conversion-APIs. But the APIs gets rejected saying that conversion actions  "isn't set up for uploading conversions." 

1. How to correct some mis-reported conversions in this case?

2. If a rogue element (rogue App) sent random conversion events , how to safeguard against that?

Any leads will be helpful. Thanks!

-Beria

[Google Ads API Forum Advisor]

Hi,

Thank you for contacting the Google Ads API support team.

Upon reviewing your concern, what I understand is that you are recording conversion events using firebase, have linked firebase to some conversion action in the Google Ads and are uploading enhanced conversion for leads to this linked conversion action for the same conversion event using the Google Ads API. While uploading the conversions, you are getting an error which states that “isn't set up for uploading conversions.”. Please confirm if my understanding is correct. 

This error message generally corresponds to the INVALID_CONVERSION_ACTION_TYPE error. This error indicates that the conversion action specified in the upload request isn't set up for uploading conversions. In order to assist you further and answer your queries, please provide your Google Ads customer Id, conversion action Id and the complete API logs (request and response with request-id and request header) generated at your end for the conversion uploads without redacting any information.

If you are using a client library and haven't enabled the logging yet, I would request you to enable logging for the specific client library that you are using. You can refer to the guides Java, .Net, PHP, Python, Ruby or Perl to enable logging at your end. For REST interface requests, you can enable logging via the curl command by using the -i flag.

You can send the details via Reply privately to the author option, or direct private reply to this email.

Thanks,
 

Google Ads API Team

Feedback
How was our support today?

               
[2025-08-19 03:35:38Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01szSYe:ref" (ADR-00330296)