I second that emotion.
Also, there is the {random} Value Track param. It would be awesome if we
could surface that in one of these reports. Has anybody checked to see if
this value is visible in the Destination URL report?
On Tuesday, July 3, 2012 4:30:41 AM UTC-7, Stefan Podkowinski wrote:
>
> I haven't really tested the new click report yet, but reading the field
> description it seems the clickId is provided as a long datatype. Has anyone
> figured out if it can be mapped to the alphanumeric gclid parameter?
>
> Having a click level report could be a potential game changer. But there
> needs to be a way to map the clickId with your own tracking
> solution, preferably using a new value track parameter.
>
> Also without costs provided the report isn't half as useful as it could be.
>
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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].
For more options, visit https://groups.google.com/groups/opt_out.
