Technical
Q: Why do we need a Tag Management System? Q: What is a TagMan container tag? Q: How can TagMan piggy back our existing landing pages? Q: How will TagMan effect page download speeds? Q: Will TagMan work if users do not accept Javascript or cookies? Q: Where in the page code is TagMan placed? Q: How scalable and robust is TagMan? Q: Can I write out the data from TagMan into our Web Analytics Tags? Q: Do I need to escape the values that are added in the TagMan container tag? Q: Is the TagMan impression tracking code certified across all publishers and networks? Q: I have more questions – can I email you?
Q: Why do we need a Tag Management System? A: Because it provides a consistent way of controlling the data passed to third party marketing solutions without tying up valuable IT time. Marketing teams can turn around new marketing initiatives in shorter timeframes and can set up business rules to determine which tools are used to analyze and optimize the conversion of different customer segments that use the site.
Q: What is a TagMan container tag? A: There are four types of container: Dynamic Javascript containers can be used to dynamically collect data from pages and to deploy solutions that need to run directly in the page; static Iframe tags offer limited TagMan functionality but can allay any security concerns ; static GIFs can only be used to serve one tag per page but offer absolute security; and redirect tags, which are used to track exit pages and download links. Static Iframe tags and static GIF tags do not use Javascript.
A: Dynamic tags are Javascript tags that wait for the page to load before capturing information from pre-defined variables or positions in the page. This is then inserted into the third-party tags before they are written out into the page or Iframe. This means new information can be passed into tags without the web developer having to amend the HTML source code.
Q: How can TagMan piggy back our existing landing pages? A: If you already have a system in place to report the source of marketing activity then TagMan can piggyback that information by translating the URL or referrer into a particular campaign. This means you don't have to ask partners to change their link and can make use of the time already invested to set this up.
Q: How will TagMan effect page download speeds? A: TagMan consists of a Javascript library and short amount of code that is included in each page. The library is standardised and shared across all clients so that users only download it once per session. When the page is loaded an initial call to TagMan retrieves the parameter requirements and then TagMan waits for the page to complete before continuing. Unless they need to be run directly into the page, tags are usually written out into an Iframe, along with the flash pixel. The advantage of writing tags out into an Iframe is they will not delay the page from completing. If the business logic dictates that no 3rd party tags need to be served, minimal code is sent back to the page, keeping bandwidth to an absolute minimum and reducing the impact on page download speed.
Q: Will TagMan work if users do not accept Javascript or cookies? A: If users do not run Javascript, for example with certain mobile browsers, then they will be served an Iframe by default. If users do not accept cookies then they will still be shown non-campaign related tags. Note that if users do not accept cookies then they will not be tracked with FSOs, regardless of whether they accept them or not.
Q: Where in the page code is TagMan placed? A: To ensure the highest level of learning for your online campaigns, it is highly recommended that the tag be placed immediately before the closing body tag. Do not place it before the opening body tag or after the closing body tag. If the page is using frames and/or all pages are running under the same URL, please insert the TagMan tag into the code of the individual pages you need tagged that fill the main frame.
Q: How scalable and robust is TagMan? A: TagMan has been designed to run on standard hardware across multiple data centers. Data is reported back in near real time (usually within 30 minutes) via an n-tiered approach. This means that we can increase our capacity by simply adding more servers in line with our client needs. TagMan is configured across multiple data-centers to offer complete redundancy and we have written a proprietary breakwater system that means should we experience an incredible spike in traffic we still serve back content to minimise the chance of our clients' sites being affected.
Q: Can I write out the data from TagMan into our Web Analytics Tags? A: The TagMan cookie profile contains a complete history of all of the marketing activities within the relevant time period, including which sites they have viewed banners on and the precise keywords used to locate the site. Any of this data can be written out into third-party tags to assist with attribution modeling or multivariate testing. We also have a global user id that allows users to be tracked across multiple ad serving platforms and ad networks.
Q: Do I need to escape the values that are added in the TagMan container tag? A: No, TagMan will escape any parameter values in the tag.
Q: Is the TagMan tracking code certified across all publishers and ad networks?? A: Yes, TagMan's tracking pixel is approved for serving across Google, AOL and Yahoo, which are the main publishers/networks who require certification.
Q: I have more questions – can I email you? A: Please contact us at contact@tagman.com. We will be happy to answer your questions.
|
