";s:4:"text";s:3126:" Honestly, I haven’t seen a situation where no History Variable contained something useful, maybe it’s even impossible. I don't refresh the browser at any point between users sessions however i can do this if needs be. I have no preference here, so it’s up to you which one to choose. In the article you indicated a full URI, but in the comment above it's just the URN. Theoretically, it should be able to catch such URL changes.
A developer should take care of that.
Condition: New History Fragment contains /login/ (or something like that). Your email address will not be published. 3. But we have an issue: before login or registration we have SEF URL, like /category/page. 'event' : 'custom-pageview', However, in single-page website/app, all of the necessary code is loaded once and the page does not reload during the entire user session. I'll re-read your article again . The URL of the page changes as it should (no hash, the URL acually changes) and below the menu the content changes. On the other hand, if you’re really working with an SPA, every time you navigate from page A to page B, the Preview and Debug console stays as it is and continues tracking your interactions (e.g. Hi Julius, I'm struggling to get this working correctly for my site. Hi Julius, in that case it's same with fragment parameter through custom variable, and send the value as virtual page in custom field in google analytics tag? Thank you for your useful guide. If you have a website where the url does not change (only the content dynamically reloads) is it better to push virtual pageviews or track navigating through the app as events? window.dataLayer.push({ And if so, why shouldn't I do the same for UTM parameters? Custom tags may be used to implement tags that are not yet supported by Tag Manager's native templates. Every time you navigate somewhere, a Universal Analytics Pageview Tag should fire. If the conditions are met though then you can push an event into the data layer with whatever information you want (we push the lastUrl into the data layer) then we fire the analytics from that event. Is it a Custom JavaScript variable? Does the New History Fragment contain some data?
Because of this, you need to do some additional configuration (and maybe even with the help of a developer). History change with fragment is a solution for non-developers who can easily track URL changes without writing additional JavaScript. People land on /app#/thankyou , so this means i can setup just hitting URL /app/thankyou in GA as a goal. * (enable Regex checkbox) But I saw on some other websites that with REactJS, it seems mandatory to use specific library like :