Google UA is closing. Are you GA4 Ready?
|
Main Parameters
# equivalent of the classic analytics utmhid parameter * must be present on EVERY call to be accepted by GA servers. + see http://stackoverflow.com/questions/26849042/u-parameter-in-universal-google-analytics-collect-hits for full explanation Override Parameters
Events Parameters
You will only see any of these when t (type) = event |
Custom Parameters
Campaign Variable Parameters
To register any campaign variables (c*) you MUST populate Campaign Source AND Campaign Medium as a minimum. Timing Parameters
|
eCommerce Parameters
You will only see these when t (Type) = transaction or item. App Tracking Parameters
Other Parameters
aip: The value of this parameter can be absolutely anything to cause the IP to be anonymized. This includes a blank value. $aip=, $aip=0, &aip=1 will all cause anonymity. Google Experiments Parameters
Social Tracking Parameters
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Created By
www.dmpgteam.com
Metadata
Favourited By
Comments
Thanks man!
No worries, glad its helping so many people.
great stuff, thanx though the irony is that _u parameter is causing me headache - any pageview sends duplicate collect requests which only differ on '_u' parameter...
Sorry for long time to reply. I've updated the _u parameter explanation with notes. If you're still struggling with this issue, let me know a URL where I can see the issue happening or ping me an email on tm (at) dmpg.co.uk and i'll see if i can identify the problem. It's unlikely to be anything other than your code firing off multiple pageview requests as opposed to a config error.
Thank. you. so. much.
No problem!
Can you set the date and time in the request string ? I'm thinking about offline processing, where the data might be sent a few days after the process took place.
Hi Phil, sorry for late reply. Depending on what type of data set you want to place in GA, you need either the Measurement Protocol or Data Import using the GA management API.
- Measurement Protocol allows standard GA hits to be sent (pageviews, events, ecommerce data etc) where you specify all the parameters. You can tell GA what time the hit occurred using the Queue Time (qt) parameter (https://developers.google.com/analytics/devguides/collection/protocol/v1/parameters#qt) however you should note the max recommended offset is just 4 hours!
- Data Import is more for uploading meta data to enrich your hit data, so it's not for sending pageviews, events etc. The exception to that is refunds which are very much a hit data type. Start here https://developers.google.com/analytics/devguides/config/mgmt/v3/mgmtDataImport
In conclusion, if you were thinking about sending hits within a 4 hour window of them occurring then it's easy but otherwise you may well be out of luck with this one.
NB If you or your client are using GA Premium then there are probably other options open to you.
We are a GA Certified Partner so can help either way. Ping me an email at tm (at) dmpg.co.uk if you would like us to help further.
Bravo!!
Do you know what jid parameter is?
Aviv, jid is the JoinID for the DoubleClick beacon. When a site has display advertising enabled each GA hit will be redirected to DoubleClick aswell. The jid (JoinID) is used to bind your existing DoubleClick cookie value with your GA cookie value thus permanently linking the pair together.
Add a Comment
Related Cheat Sheets
More Cheat Sheets by dmpg_tom