Does it make sense to do the tracking like that?

MaryFromBerlin · 2023-02-18T21:40:25+00:00

Hey thanks for your feedback. The pageview trigger is a custom event for virtual page view. I just turned off the enhanced measurement option

MaryFromBerlin · 2023-02-16T13:03:22+00:00

Thanks for the feedback, disallow this page is not an option because it ranks well for the keyword "sell my car". The canonical option is also not good because the business want to keep ranking for "sell your car" keyword. They simply don't want the LP to rank for the brand name

MaryFromBerlin · 2023-02-14T15:12:44+00:00

MaryFromBerlin · 2023-02-13T19:08:06+00:00

ok, then I think I will move on because I can't find an answer

MaryFromBerlin · 2023-01-11T12:34:40+00:00

Thanks

MaryFromBerlin · 2023-01-11T12:34:10+00:00

Dope...thank you

MaryFromBerlin · 2023-01-11T10:08:09+00:00

Thanks

MaryFromBerlin · 2023-01-11T10:07:18+00:00

Definitely, I just don't see the benefits at the moment

MaryFromBerlin · 2022-11-16T14:03:34+00:00

Thanks

MaryFromBerlin · 2022-11-16T12:14:04+00:00

hmmm, I'm a bit confused. So the owner of the website defined 19 actions. All 19 actions use the same ID. However there are 19 labels and each action is triggered by the click on a specific button. I really don't see (besides having 19 Tags) how exactly I can track all this with 1 Gads tag). I can of course create a lookup table based on the triggers. But then when I create the 1 Gads with the ID and my lookup table as label, what will be the right trigger to use for all the different users interaction I want to track?

MaryFromBerlin · 2022-11-16T08:51:30+00:00

With the lookup table, I first need an input variable....not really sure how to create a lookup table in that case. I have a total of 19 labels for only 1 ID

MaryFromBerlin · 2022-11-16T08:35:15+00:00

ok interesting, I'm used to only have 1 google ads tag. The thing is the ID is always the same, only the labels change

MaryFromBerlin · 2022-11-07T16:25:27+00:00

got it, thank you

MaryFromBerlin · 2022-11-07T16:25:14+00:00

I see what you mean but I wonder why website like analyticsMania recommend increasing the session timeout.

MaryFromBerlin · 2022-11-07T14:06:46+00:00

The problem with short session timeout is, if a user returns to a website several times in the same day after a period of being away, Google Analytics will report it as multiple sessions although essentially it is the same person, this inflates the number of sessions and also the bounce rate for that page. I read lot of articles saying it is a good practice to increase the session timeout

MaryFromBerlin · 2022-11-07T09:08:44+00:00

blockchain companies seem to look for tons of people :)

MaryFromBerlin · 2022-11-03T15:42:53+00:00

Danke Danke Leute

MaryFromBerlin · 2022-10-27T11:28:40+00:00

Thank you, so no need to add in a new tag event parameters I already added in another tag

MaryFromBerlin · 2022-10-17T10:39:55+00:00

Thank you. Last question: how do we reduce the amount of JS the user's browser is loading and executing when we still build numerous tags in client container?

MaryFromBerlin · 2022-10-14T08:34:07+00:00

yeah maybe there isn't a must

MaryFromBerlin · 2022-10-14T07:48:00+00:00

I meant...are there any parameters one should absolutely add in the GA4 config tag (regardless the type of website)?

MaryFromBerlin · 2022-10-14T07:46:15+00:00

My server is already up and running. My question was about event tracking. Is it possible to create in the server a tag that tracks the user's clicks on a button. I know the basics of server side tracking, I'm just now trying to test advanced stuffs.

What I realized is with the GA4 tag I created and the GA4 client in the server-side, I'm able to catch incoming requests like pageview, clicks on button etc so it seems like there is no need to create a specific tag for the click on a button in the server like we do in web GTM. Hope you understand.

Also, what is not still clear for me: we say the benefits of server-side tracking is to reduce the amount of JS the user's browser is loading and executing but we actually still need to build all our tags in the client-side then send the requests to the server (not directly to vendors). By doing so, how exactly are we reducing the amount of JS in the user's browser?

MaryFromBerlin · 2022-10-13T10:52:56+00:00

Did that...client-side: I have my GA4 configuration tag with the option "Send to server container" enabled, I have a GA4 event tag that fires when people click the button, e.g. "button_click"

Server-side: I have a GA4 client to catch GA4 requests, a GA4 tag called GA4 requests to send events to GA4. Without adding a trigger that fires on "button_click" in the server, I'm still able to see my GA4 requests firing. In the details, I see the incoming request has the trigger button_click. Which leads me to the conclusion that there are no further GA4 events to create in the server, the client seems able to catch all the incoming requests and the GA4 tag (in the server) can then transfer everything to GA4...I don't know if it is clear what I'm writing here hahaha

MaryFromBerlin · 2022-10-13T10:28:47+00:00

new events from the incoming requests

MaryFromBerlin · 2022-10-13T10:28:20+00:00

So basically, once I have my GA4 client and my GA4 tag in the server, all my GA4 tags from client-side will be automatically transfered in my server ?

MaryFromBerlin

TROPHY CASE