100% Click not found

[Anirudh Beria]

Hi,

My ads are shown on mobile, and click takes user to Appstore / Playstore. Once the user downloads the App and signs up, I upload conversion-value within 24 hours. I don't have GLID (is there any way to get it considering my setup?). I am getting 100% Click-not-found which cannot be true. Some points:

1. I am using both email and phone number (E.164 format), and hashed as per Google-API-docs

2. Since I don't have GCLID, I was setting "orderId'  as my internal customer number. I have tried uploading without orderId as well. Result is same.

Attaching the relevant code, and a sample response. Any pointers will be helpful. Thanks!

Regards,

Anirudh Beria

[Google Ads API Forum Advisor]

Hi,

Thank you for reaching out to the Google Ads API support team.

By reviewing your concern, I understand that you are getting a CLICK_NOT_FOUND error. which indicates the email address or phone number for this event can't be matched to a click. This may be because it didn't come from a Google Ads campaign, and you can safely ignore this warning. If this includes more imported events than is expected, you may need to check your setup. I would recommend you refer to this Upload Click Conversions for more information.

In order to investigate further on your queries, please provide us with the complete API logs (request and response with request-id and request header) generated at your end and uncropped UI screenshot of the Google Ads account where you are facing the issue.

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.

 

This message is in relation to case "ref:!00D1U01174p.!5004Q02rW1Co:ref"

Thanks,
 

Google Ads API Team