Sometimes you will have the need to properly kill a page on your website - perhaps a member of staff has left and you want to remove their profile, or you're taking down a section that is no longer relevant. A 410 status code tells visitors that the page has been removed and will not be returning - and it is the 'correct' way to remove resources.
Recently I read a post by a famous designer claiming that "Good design is ephemeral" at first I felt annoyed and his point of view gave me food for thought. While a part of me wouldn't like to admit it, I realise that his point was true.
So in our visual world how critical can the design of a website be?
Using a lookup table to render the correct Google Analytics property based on the environment or hostname was one of the great tips I picked up from the Google Tag Manager training at Brighton SEO. It is pretty simple to set up, and once you have done it you'll never look back!
A problem we have faced in our Joomla development work has been ensuring that the correct Google Tag Manager environment code is being deployed with the right environments - for example in our development environments we need to deploy the container code from GTM related to the dev environment, but in production, we need the live container code.
After some discussions about the best way to implement it, we came up with a simple way to ensure this 'just worked' across all our sites without any complicated settings.
If you've followed our other posts about setting up Google Tag Manager for different development environments and how to implement GTM container code within Joomla templates, you'll probably next be asking how to set up Google Analytics so that you can separate out your development, demo and production sites. Let's take a dive into the easiest way to do this with Google Analytics properties.
I often have moments in the office where I am so excited by a new feature that I start clapping excitedly and pointing at the screen - this was definitely one of them! For some time we had been trying to figure out how to reliably test our marketing tags between different environments - development, demo and production - without accidentally putting tags in the wrong place or leaving debug mode enabled.
We used to achieve this with different containers in Google Tag Manager for each environment or using the 'preview' mode, which was very cumbersome - so the day back in November 2015 when Google launched its 'environments' feature in Google Tag Manager was most definitely a happy clappy day!