It's not best practise to do it that way. There should be a tag manager, eg. something that is a part of the statistics/tracking system and inserts the correct code for the correct place. This usually handles this kind of stuff.

What you should do is, first of all add checks to see if the window.dataLayer object exists. Otherwise this script will fail, and it can stop script execution on the page and make other functions not working.

For tracking the first page visited, you need to add code that stores this information. You could either store it on the server side in a session variable or a cookie. Or, what I suggest, is to store it in a cookie next to the code for the tracking, so that you have it in one place. So; check the value of the cookie, and if it is empty, save the current page URL to this cookie. To have it stay the same during the session but be a new one on next visit, the cookie should be stored as a session cookie.

Hi ZZ,

I think you kinda answered you own question.

Session State?

Essientally you can choose a storage mechanism of you choice. When a user visits the site for the first time up date the storage with the value of that page.

On subsequent page visits you check that storage and if it is set use it, otherwise set and use it.

Checkout some of the storage options and comparsions here https://www.sitepoint.com/client-side-storage-options-comparison/.

Paul

You should really avoid session state as it requires sticky sessions and is not maintained if the user is sent to another server.  You could check for the existance of a `__firstPage` cookie and if it is absent, then create it with the Id of the current page, set it to samesite, secure with lifespan of browser session.  You could then use this when assembling this in your script in your razor file.