By default Google Tag Manager (GTM) provides several handy macros and lookup table macro is one of them. In GTM, by using lookup table macro you can reduce number of deployed tags as well as the number of rules you need to load the tags. When implementing tags in GTM always follow famous DRY principle (don’t repeat yourself). Use of lookup table avoids duplication and enables reusability.

In simple words, a Google Tag Manager (GTM) container holds other tags. GTM container is also know as universal container tag or site-wide tag. A GTM container is managed via GTM dashboard and controls tag dependencies and tag firing order. On your web page, you can have multiple GTM containers. GTM container code looks like following - embedded either header or footer of your web page template.

Believe it or not, on average an US ecommerce website has between 15-20 marketing tags. Implementing and maintaining these many marketing tags on your website is often a cumbersome job. Google Tag Manager (GTM) is a great tool for marketer as well as developers. Like any other Tag management solution (TMS), GTM not only decouples deployment of these marketing tags but also introduces an efficient way of sharing data to these tags via data layer.

Few months back I managed to get Statamic working with Varnish. Setting up Varnish for Statamic was quite easy and my website performance improved drastically (you can see load and performance testing benchmarks here). One of the biggest challenges was Varnish cache invalidation on content update. Every time, Statamic content was updated I have to invalidate cache manually using curl requests.

SeeWhy ¹ a market leader in real-time behavioural marketing, has recently published an extensive and empirical research on ROI of 1-to-1 email remarketing programs.

After working with Adobe AEM and several other JCR backed content management systems in last few years I have realised that there are a lot of mis-conceptions about Adobe AEM. As matter of fact, brain washing is quite common these days when Adobe AEM is on the table. Sometimes Adobe is on fault, on other occasions rhetoric of competitors, agencies and architects.

A recent report by Forrester Research on digital experience delivery platforms has named Adobe and Hybris as leading strong performers. Adobe was recognised for its web experience management suit which includes content management, digital assets management, targeting and personalisation capabilities.

Vagrant is a perfect choice for virtual development environment . Vagrant was created and maintained by Mitchell Hashimoto. It benefits developers, operations engineer and designers. Vagrant really shines when working in a team of any size - small, medium or large.

Today I want to talk about the performance testing. Automated web application testing is not very rare these days. This includes functional, unit and regression tests at minimum. A good web application delivery approach normally includes a continuous integration setup to run automated tests.

AWS allows tagging of EC2 resources using your own metadata (key-value pair). Tagging of EC2 resources is quite helpful in managing instances, images and organise billing by tag names. An EC2 instance can be tagged by CLI tools, API wrappers or using AWS Console when launching the instance as well as after launching the instance.

Term “marketing middleware” was recently pioneered by marketing technologist and blogger Scott Brinker (at least in context of marketing technology). Search for term “marketing middleware” on web leads to Scott Brinker’s posts on Marketing Technology Landscape Supergraphic and Tag management software as marketing middleware.