Offline conversions - Salesforce x Google Ads

176 views
Skip to first unread message

SD

unread,
Feb 5, 2025, 3:38:33 AM2/5/25
to Google Ads API and AdWords API Forum
Hello! We have recently established the connection between Salesforce and Google Ads and set up two offline conversions. Although everything seems to be working fine, when we check the migration status of the conversions between both platforms we get the following errors:
  • The imported event cannot be recorded because its click occurred before this post-click conversion window. Make sure you import the most recent data.
  • The conversion action is associated with another Google Ads account. Make sure you import to the correct account and have the necessary permissions.

We have contacted the Google technical team, but they have been unable to help us. Has anyone found themselves in a similar situation? Thank you very much in advance.

Google Ads API Forum Advisor

unread,
Feb 5, 2025, 7:08:41 AM2/5/25
to serve...@gmail.com, adwor...@googlegroups.com
Hi,

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

Based on the information provided, I understand that you have established the connection between Salesforce and Google Ads and set up two offline conversions. Can you confirm whether you are using the Google Ads API or the Google Ads UI for uploading the conversions? If you are using the Google Ads API, I would request you to share the customer ID and the conversion action ID for which you are encountering these errors. I would suggest you refer to this "Debug common errors" documentation for more information. I would recommend you to refer to the Monitor offline data diagnostics documentation as it helps to find the overall health of the conversion upload processes.

Upon checking, I could see that you are encountering the EXPIRED_EVENT error. Regarding "EXPIRED_EVENT" error, you may double-check if the given identifier is not too old or occurred before the lookback window for the specified combination of conversion date and conversion action. You may use the click_view report resource to verify your GCLID. In addition, you can first verify the click_through_lookback_window_days specified in your conversion_action. From the value retrieved, then perform a request using the click_view report for each day (with date filter for one day) until the last valid date, in reference to the lookback window days. A click-through conversion is counted when someone clicks on your ad and installs your app within the length of time you select. If you have a 90-day click-through conversion window, conversions that happen within 90 days after someone clicks on your ad will be recorded as a click-through conversion.

If you are using the Google Ads API for uploading the conversions, kindly provide us with the complete API logs (request and response logs with request-id and request header) generated at your end to further assist you better.

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.NetPHPPythonRuby 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.!5004Q02vH0EI:ref" (ADR-00287142)

Thanks,
 
Google Logo Google Ads API Team

Feedback
How was our support today?

rating1    rating2    rating3    rating4    rating5


 


Reply all
Reply to author
Forward
0 new messages