Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Add Google Adwords Paid Search Keyword integration

Avatar

Level 4

18-05-2014

Now that google has encryptet paid search keywords we get a lot of "not provided" in the paid keywords reports. Unfurtunately if you have linkedin your Adwords account with your Google Analytics account you still get the keyword data. For this we get a lot of push back from clients.

Make it possible to add a Google Adwords account in the admin console so we get the same data in Analytics. I know that the Media Optimizer product allows for this but many are not ready to pay the price for this. Its a serious disadvantage for Analytics that will drive Google Analytics uptake, so please consider this asap.

19 Comments

Avatar

Level 2

17-10-2018

Hmmm, I have 0 "AMO Id Instances", but 1700 "AMO Clicks" - and I cannot break it down by any other dimension/evar. Any  ideas?

Avatar

Employee Advisor

17-10-2018

Agreed, it sounds like the query parameter is not getting passed into your landing page URLs.

Heads up that, as Jen mentioned, AMO metrics will only be available to break down by AMO dimensions. AMO dimensions can be broken down by other AMO (ad analytics) dimensions, Analytics dimensions, AMO (ad analytics) metrics, and Analytics dimensions.

Avatar

Community Advisor

18-10-2018

alessandrov92748270​ have you made some test if your ad links have any query parameter for tracking? at least the "s_kwcid" should be on the final url - as far as I know.

remark: we choose the manual mode because we want to propperly test it and have control over the final links...

Avatar

Level 2

19-10-2018

No, the s_kwcid is not in the URL. We will try the manual tracking then. Just didn't see the benefit, because it seemed to be working (we get the AMO Impressions, Clicks, Costs etc...)

Avatar

Employee Advisor

22-10-2018

Metrics are imported via the API connection whereas the Dimensions are imported based on classifications applied to the value captured by s_kwcid.

Hopefully adding in that query param to the landing page URLs resolves the issue - please let us know how it goes