Because, of course, if I start telling you that my neighbor has taken to having conversations with her dog, who is a puppy and a bit dirty… I say, the “spoken” violence thing… does it also apply to animals? ? Because she tells him some things. The other day she told him that as she continued to “do it in the yard” she was going to buy him the cheapest feed she could find. Without contemplations. What a girl she is. Not seriously. That scares me. The next time I take the trash down I’ll scrub the stairs… Good morning! How are you? How was January? I hope that very good. Me the same, super cool mega guachi. And even more so now that I finally have a « Get to know me » page (I give birth to the donkey).
How to record And we leave it here
okay Because today’s post has a nautical theme, so if you want to learn. How to record WordPress data (such as post category, format, author, date, etc.) in Google Analytics with custom dimensions . This is your post! ! By the way, in case you don’t remember or you’re new, this post company data continues or complements , or complefresa although I prefer compleorange. Well, if you haven’t done it before, you should take a look at this post: Introduction to dimensions and custom metrics in Google Analytics . If we think about it the other way around: we want Google Analytics. To understand post categories so we have to create that custom dimension and receive the data. Since it is Tag Manager that sends the data to Analytics. We need to configure Tag Manager to do so.
But Tag Manager doesn't
Understand post categories either, so we have to tell our WordPress to send that data to Tag Manager. Totally logical, don’t you think? The hit refers to each event BM Leads or event in Analytics. For example, on each page load. This means that every time you load the page, the custom dimension could change. For example, the category of the post would be a hit type dimension since the same user. In the same session, could visit several pages and each of them belong to a category. Session: This scope refers to the session process of a specific user.
In this case, the metric could be different for the same user, but as long as he visits us, for example, on different days. Imagine that we want to record in Analytics if it is raining in the place from which a person visits us (yes, it can). Well, in this case the scope would be a session, because it is rare for the weather to change during a visit ( unless it is a tropical climate, right Che? ) but the same user could visit us on different days, with different weather situations.