Thanks Josh,
The 2 hyphens, as you wrote, are cause the gclid to change in our site.
We'll search our proxies, load balancers, any rewrite engines etc.. to fix
it.
On Monday, July 31, 2017 at 7:44:09 PM UTC+3, Josh Radcliff (AdWords API
Team) wrote:
>
> Hi Nadav,
>
> Thanks for sending that
Hi Nadav,
Thanks for sending that over. I ran a *CLICK_PERFORMANCE_REPORT* for that
customer and noticed that it contained a row that matched the GCLID if I:
a) ignore case, and b) add an additional hyphen (-).
GCLID you sent over:
*Click date:* 19-07-2017
*Client Customer ID:* 272-772-9533
On Monday, July 31, 2017 at 3:48:20 PM UTC+3, Josh Radcliff (AdWords API
Team) wrote:
>
> Hi Nadav,
>
> Could you send me the click date and client customer ID for the GCLID
> below?
>
> Thanks,
> Josh, AdWords API Team
>
> On Monday,
Hi Nadav,
Could you send me the click date and client customer ID for the GCLID below?
Thanks,
Josh, AdWords API Team
On Monday, July 31, 2017 at 3:14:03 AM UTC-4, Nadav De Bruin wrote:
>
> Some of the AdWords redirections we get on our site comes with lower-case
> gclid value.
>
> When we
Some of the AdWords redirections we get on our site comes with lower-case
gclid value.
When we report offline to AdWords by AdWords API with this lower-case gclid
we get an error back saying: “OfflineConversionError.UNPARSEABLE_GCLID”.
>From the start of the implementation 2 month ago, we
