What is container tag

Tags are comprised of elements and attributes. An element is an object on a page such as a heading, paragraph, or image , and attributes are qualities that describe that element such as width and height. Tags usually travel in pairs. An opening tag begins a section of page content, and a closing tag ends it. A few tags are called non-container tags , because they don't contain any content - they stand alone.

Examples are images and line breaks. Even when coding in HTML, you should get in the habit of writing tags in lower case. Learn JavaScript and other web development technology concepts through easy-to-understand explanations written in plain English. The container tags are tags that have some content between their opening and closing tags.

Level up your programming skills I'm sending out an occasional email with the latest programming tutorials. About Nathan Sebhastian is a software engineer with a passion for writing tech tutorials. So be careful while working with container tags. The majority of tags present in HTML are container tags. This contains all other tags in between these tags which are considered for making a webpage. It is described in the head tag. HyperLinks: Following tag is used to define a hyperlink in the webpage:.

Script tag: Following tag is used to add JavaScript code to the webpage:. Empty Tags The tags that do not contain any closing tags are known as empty tags. Empty tags contain only the opening tag but they perform some action in the webpage. Metadata is the data about data and is described in the head tag. Skip to content.

For example, the onsite tracking may be a tool like Google Analytics, or Webtrends. The site may also have a display banner campaign to help to drive traffic. If a PPC campaign is running, it may be measured through a separate tool like Adwords. Each of these types of tools has their own JavaScript codes that are placed on a site.

Without a container tag all of these different types of codes need to be placed on pages of a site in different places of the source code. Onsite tracking is there all the time, but other tools may need their tracking to be placed on a site for a length of time whilst a campaign is running.

A container tag is needed to make this process far more manageable, and at times, more cost effective. There is no need to go through development or need to redeploy the site when a change is needed to the tracking code; this is because the container tag can be updated through the Google Tag Manager interface.

Tracking codes can be at a page or event level. For example, a Google Analytics code can fire on every page, a Floodlight can fire on certain pages, or a Google Analytics event can fire on a PDF download button.