Reader TTS

As with my first article, the objective is keep the Google analytics users and other analytics expert informed and updated about some common aspects in GA reporting and implementation to

prevent all the headache afterwards. If you have not gone through my first article, please have a look for first instance of what you are going to read in this article. GOOD NEWS: The

article is short & cover less pointers so it will be easy to remember :) Get… Set… Go !!!! ATTRIBUTION IN ENHANCED E-COMMERCE In my first article, I have explained that how different

interactions in Enhanced e-commerce tracking is not persistent and we need to pass it with every hit. However, google analytics do have certain interactions or parameters that persists and

is not required to be passed with each and every hit. They are: _Product List -_ * While it may surprise many, this is TRUE!! We all know, the report “Product List name” (under Product List

Performance report) displays the data for the values passed in the “actionField” object * This “actionfield” passed in any ONE of the enhance e-commerce interactions like add to cart,

product clicks, product detail views etc will automatically persists to the final purchase. Unlike product information, we do not have to pass this info again and again with each interaction

* The value will only be overwritten if the field captures different value within the same session (this is just like session scoped custom dimension) * Due to the attribution in product

list, we often see “(not set)” value in our product list performance reports. This is due to sessions expiring and new ones starting without any Product List information at all…. SOLUTION :

As per Simo Ahava, we should leave this AS IS since it can be actually useful to have it there to give you insight to how often sessions break mid-funnel * Also, keep in mind that the

attribution will only work against the same PRODUCT IDS and not product name or brand etc. So, if we have different product names but same product ids, attribution will work correctly but

not the other way round _Internal Promotion -_ We see transaction details in “Internal Promotion” reports even when we have not passed the promotion info on purchase/thank you page. This is

only possible due to GA attribution techniques * GA follows a sequence to attribute promotions. The first preference is always given to “Promotion Clicks” and then “Promotion Views” * The

attribution is similar to last touch and gives credit to the last promotion clicked. If there are no clicks in the session, but one of user’s previous session did include promotion clicks,

it will be attributed accordingly * Only when both the conditions above in point two does not satisfy, promotion views are taken into consideration and follow the same norms For more info

read the article by Simo Ahava : https://www.simoahava.com/analytics/attribution-enhanced-ecommerce-reports/ BOTH CLASSICAL AND GTM IMPLEMENTATION ON THE WEBSITE According to Simo Ahava

posts and my own experience, IT IS POSSIBLE to keep both types of tracking on the website. So, whenever clients are in doubts and ask this questions around whether GA classical would break

if I have GTM implementation in place? The answer will be NO in most cases. So, what is that case when the answer is otherwise? _TRACKER NAME,_ yes, the tracker name must not be altered in

any way and must be kept as default. Only then having both types of implementation will run smoothly on the website. If the tracker name is different then the last tracker name and all its

setting will be taken up with the next tags including the “GA property ID”. _E.g_ : if we have data tracked to UA-12345678–1 in the snippet, using the ga(‘create’,’UA-12345678–1')

command. Then, we have an Event Tag in GTM, collecting data to ‘UA-12345678–2’, firing on link click after the ga command. If this Tag has the same tracker name as the snippet-based tracker,

any ga(‘send’,…) commands you run on the page after this GTM Tag has fired will now use the settings in the GTM Tag, _including the new property ID_ (this example is copied from one of the

posts to explain better) Hence, it is important to understand the demerits of changing the tracker name and handle it accordingly. However, GTM never suggests changing it AT ALL!! Read more

here. COPY CUSTOM DIMENSIONS AND METRICS IN DIFFERENT PROPERTIES This might sound easy and no big deal but trust me if you have 100 custom dimensions and metric to copy, gods be good with

you. While there is a sharing option in GA (one CD/CM at a time though) to copy them to a different property but doing the procedure for just 1 CD will take approx. 1min. Doing the math it

would take 100mins i.e. more than an hour to copy all the 100 CDs. I hope you now see the trouble here! But, no need to worry, it’s GOOGLE, there is always a solution, you just have to look

for it. And, for this problem we have a GOOGLE APP SCRIPT… TA DAAAAA !!! Yes, there is a script that is easily available here (the code is only for Custom dimensions but can be written for

Custom metrics, filter and goals as well, you just need to do some customization) and can be used to make this whole work done in _less than a min_. Interesting, Isn’t ? _CONCLUSION_ So, I

just hope this read was useful and if not much but atleast you have few pointers for brainstorming and taking care of GA before it explodes. Feel free to correct/add more pointers that I

might have missed and spread more knowledge!!! Good luck and thanks a lot for your time!!