Yes - it looks like we are having a mismatch in the case of the letters between the URL GCLID and the CLICK_PERFORMANCE_REPORT GCLID, only on occasion and without a clear pattern (such as in account, type of ad, landing page, etc.). We are looking into this and will post an update when we have one.
On Monday, November 30, 2015 at 1:15:57 PM UTC-5, Josh Radcliff (AdWords API Team) wrote: > > Hi, > > The GCLIDs are generated strings, so it's entirely possible that some of > those strings will contain mixed case. Are you saying that the GCLIDs you > are seeing from clicks are not matching the case you see in the > CLICK_PERFORMANCE_REPORT? I would expect the case to match between those > two. > > Thanks, > Josh, AdWords API Team > > On Monday, November 30, 2015 at 11:47:09 AM UTC-5, OMCC wrote: >> >> Thanks - that seems to be the issue indeed. But why would the GCLIDs be >> all lowercase in certain specific cases? We are grabbing them directly from >> the URLs and most of the time they are fine. This issue seems to be >> scattered across different accounts and ad types. >> >> >> On Monday, November 30, 2015 at 9:03:50 AM UTC-5, Josh Radcliff (AdWords >> API Team) wrote: >>> >>> Hi, >>> >>> I think I know what's happening here: the >>> OfflineConversionFeed.googleClickId >>> <https://developers.google.com/adwords/api/docs/reference/v201509/OfflineConversionFeedService.OfflineConversionFeed#googleclickid> >>> is >>> case-*sensitive*. In your log file, I see that this field's value is >>> all lowercase, but the *googleClickId*s you mentioned contain uppercase >>> letters. Please try the request again after changing the click IDs to have >>> the proper case and let me know if you still encounter issues. >>> >>> Thanks, >>> Josh, AdWords API Team >>> >>> On Wednesday, November 25, 2015 at 3:14:59 PM UTC-5, OMCC wrote: >>>> >>>> Hi, >>>> >>>> The error seems to have returned and we've found two of the GCLIDs in >>>> the click performance report. We are sending the logs. >>>> >>>> >>>> On Tuesday, November 24, 2015 at 9:18:20 AM UTC-5, Umesh Dengale wrote: >>>>> >>>>> Hello, >>>>> >>>>> I am glad that you found the solution. Let us know if you need help >>>>> with any other issues. >>>>> >>>>> Thanks, >>>>> Umesh, AdWords API Team. >>>>> >>>>> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at http://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/d113c382-baac-4d4c-ad39-5d81ca58a67f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
