Connector Improvement: Google Analytics (GA) MCF - Additional / Missing Dimensions (Transaction ID, Search Query Path)
Answered
It would be very helpful to get access to more of the dimensions / metrics available in this API – either through more pre-built reports, or the ability to build custom reports.
The highest priority dimension is Transaction ID. This allows you to join data on the standard Google Analytics connector data in transformation – making the MCF connector way more powerful. This dimension is stored in 'Interactions' in the documentation.
There are a few path dimensions which are missing from the FT connector. For us, the most important additions would be: mcf:keywordPath and mcf:adwordsMatchedSearchQueryPath to analyse how Paid Search / user search behaviour is impacting the conversion path.
Also, the paths are pretty complex when logged in the two tables (as nodes); I understand why, but it could be helpful to also provide the option to request the whole conversion path as a single string / row. Such as: "Email -> Paid Search -> Direct"
https://developers.google.com/analytics/devguides/reporting/mcf/dimsmets/conversionpaths
-
Official comment
Hi Dan, Drew from the Product Team here!
Thanks for sharing this request. I've added it to our backlog for now, but we will consider it in the future as a feature request.
-
Seconded. TransactionID is key.
-
This is a must-have and something that nearly every other platform delivers. I can even pull this from Supermetrics.
Imagine all the MAR generated by breaking down each transaction by that user's individual web sessions! It'll be 3-5x the size of the standard GA Transactions table. This is a high revenue opportunity and something that many of your users would take advantage of if it was available to them.
Please sign in to leave a comment.
Comments
3 comments