Summary: Marketing channels on GA using 'cid' instead of 'utm' parameter in URL
We use Adobe Analytics and hence all traffic channels are configured with 'cid' parameter for all campaign tracking. For ex.
cid=ps:Tata_Cliq_Westside_Exact_Apparel:Google:Search_Sok_Tatacliqwestside_E:Apparel-Unisex
This parameter is taken by Adobe Analytics and processing rules then give the data under various channels.
How do I use the same setup and implement marketing channels on Google Analytics? I don't want to use utm as a query-string parameter.
You can use View Advanced Filters to rewrite campaign/source data from URL with the help of regexp but I suppose that it would be a very complicated filter and data will only be available in the view where the filter is applied.
If you're using Google Tag Manager you can set up custom javascript variables to extract data from URL and pass it along with Google Analytics tags as pre-set fields for source/campaign/medium etc.
Related
Is there any way to query the google analytics data to look for ClientID and then extract source and medium information of that client?
The scenario is, to look each clientID for x period amount of time and retrieve related info of that client like source, medium especially organic and direct, then append it to a custom URL as a parameter to pass it long between different system.
Client X -> Google API -> Source/Medium -> Website -> (Custom page with custom URL parameter + GA-source-medium-parameter) -> Next system -> Billing -> CRM (Client X - organic or Client X - Direct etc).
Is it possible on GA universal and GA4?
Or it something can be setup using tag manager easily, by using cookie session or utm parameters?
PS - Not an API guy but did some decent research but couldn't locate the right info or examples.
There are no standard dimension Client_ID in both API UA (https://ga-dev-tools.web.app/dimensions-metrics-explorer/) and GA4 (https://developers.google.com/analytics/devguides/reporting/data/v1/api-schema). You should create custom dimension at first and after data collecting it will be possible to query Client_ID and source/medium. But keep in mind that one Client_ID can have a few sources.
Yes you can for UA. The dimension is called ga:clientId. For GA4, it’s available in Bigquery and is called user_pseudo_id. If you want to query it in the ga4 api, you will need to pass it as a custom user property in gtm.
Something I cannot find information about in the GA tracking documentation of branch.io is how to attach parameters other than the default GA ones to a link?
For example on top of UTM tracking our company uses custom URL parameters like ?acc=amex in order to provide special access pages on web that triggers certain things. Since in Branch we only have "Channel" "Campaign" and "tags" then I'm wondering would branch pass those custom link parameters and how?
We do pass custom link parameters to Google Analytics and this requires a custom webhook implementation. As this requires more information from your end, I would request you to send an email to integrations#branch.io to take this forward.
I am currently querying my Google Analytics data using the Google Analytics API via R.
I would like to query based on the unique client ID as my primary dimension, but I can't find this dimension using the API.
Is it possible to query Google analytics from the API using the client Id as a dimensions?
Update: Client ID is now available in Google Analytics Core Reporting api as ga:clientId.
I've added it in my script and works seamlessly.
Query explorer doesn't support it yet, hopefully soon...
The only dimensions and metrics that you can use with the Google Analytics API can be found in the Dimensions and metrics explorer you could also check the metadata API.
As you can see client id is not a valid dimension exposed via the Google Analytics API. You could set this in a custom dimension yourself however for it to work your going to have to make sure that its set on every single request you send to Google Analytics.
then you can use the custom dimension metadata
update
As of late 2018 early 2019 it is now possible to query ga:clientid from the google analytics api.
I need to track E-Commerce data in my Google analytic account using measurement Protocol. In the request I need to send following data and those data need to be tracked in my account.
Billing City (utmtci)
Billing Region (utmtrg)
Billing Country (utmtco)
But when I tried to find the parameters for these using enter link description here I could not find any matching parameter. Please help if any one know whether I can track these using measurement protocol.
This has been discussed (but not yet answered) here - basically it seems those fields have been deprecated.
I do not see that spelled out in the documentation, but those field do not appear in the parameter reference, not in the API (via the query explorer) and not in the GA user interface. If stuff is not part of the documentation it's pretty safe to assume that it is not there.
You can create custom dimensions in your property settings and send the geo information there.
I have a website that uses Google Universal analytics and need to integrate to a booking engine which uses the old version (ga.js).
They want us to the the utma, utmb ... values in the query string when we redirect to the booking engine but those cookies and their values no longer exist.
Is it even possible to integrate the two versions of the analytics engine so we can pass the source information to the booking engine?
Should we downgrade and use ga.js tracking javascript?
Downgrading is not actually possible, but you might run the old code in parallel (which really seems a bit hackish).
A proper solution might to
attribute an id to each of the visits and store it in GA
pass the id as url parameter to the booking page so they can store in their analytics
send them a weekly report that includes visit id and source/medium/campaign so they can match it with their data
Of course you can store campaign tags (if any) in a cookie and pass them to the booking site, or write a custom function that emulates the way Google computes source/medium. But you cannot get source information from UA since this info is now computed on the tracking server and not stored with the client.