A lot of client discussions regarding tag management recently have covered the conditional tag serving of TagMan so thought it was worth giving a quick overview.  TagMan can be configured with a number of tagsets each delivering a different vendors tag into the container tag (e.g affiliate network pixels, if affiliate de-duplication is the goal). The user configuring TagMan can decide whether the tag should be served at all times or conditionally, depending on the campaign that was responsible for delivering the user and thus providing CPA de-duplication.

The campaign setup can also include natural search tracked as an impression and paid search tracked as a click to ensure priority campaigns have a greater level of traction.  Different campaigns can be allocated different lengths of window for a user to arrive at the site (if tracking views) or to return and convert depending on the rules set in the interface.

TagMan uses cookie data that is created when a user views or clicks on TagMan tracked media, to decide which tagset to deliver into the container tag, and therefore only delivering the relevant tag for the action that has occurred. This allows you control the online marketing campaigns and the valuable data associated with those conversions.