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.

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!

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!

Segments in Mautic are a way of grouping your leads so that you can take action - for example kick off a campaign - based on their behaviour. Sometimes you may need to manually remove a contact from a segment and there is a simple way to do this.