Follow
  • A1: No. The NoScript denotation can be removed, but VersaTag will not function in pages that are not set up as Script. However, if the VersaTag maps multiple conversion tags (each with a separate ‘NoScript’ section), all of the NoScript sections will be activated.
  • A2: The last line of code runs on the client-side, but most of the additional code runs on the server-side.
  • A3: VersaTag executes very quickly - under 60ms for up to 25 Sizmek conversion tags. Third-party tag execution also affects overall pageload performance. Running VersaTag in asynchronous mode can also help boost performance.
  • A4: It is a best practice to keep site Analytics tags separate from VersaTag (for example, SiteCatalyst, GA). You can use VersaTag to embed other 3rd party marketing tags.
  • A5: Web tools such as Gomez, Keynote, and Web Metrics have tools for monitoring the load times for specific 3rd party tags.
  • A6: Not currently, but it may be available in the near future.
  • A7: No. The tags are fired randomly.
  • A8: The values in the Total Page Views column in the VersaTag level (inside the VersaTag grid) equal the number of times that each VersaTag was activated. The values in the Total Page Views column in the mapping rule level (inside the mapping rule grid) equal the number of rule matches.
  • A9: Conditional parameters for VersaTag mapping rules are NOT case-sensitive.
  • A10: No. Sometimes the VersaTag's Total Page Views counter can be lower than the Rules - Page Views counter.

    Consider a scenario in which there are several mapping rules that mutually map the same page (overlap between mapping rules) and their mapping criteria is usually true. In this case, every time a user visits that page, the Rules - Page Views counter increases as the number of overlapped mapping rules are matched.

    An example in which the VersaTag Total Page Views counter is higher than the number of Rules - Page Views counter could be where the mapping rules are always false (no match). In this case, the total counter increases but the mapping rule counter will not change, since this counter is dependent on whether the mapping rule is matched.

  • A11: Here are a few examples of strings for the CSS Selector Criteria element in the VersaTag Mapping Rule for Browser Events. For more information about CSS Selectors, click here.

    On the Web Page CSS Selector Criteria string Description
       button#clickmore Activates when user clicks the Click here for more button.
    Click here to visit the Sizmek home page. a[href*="www.sizmek.com"]

    Returns all anchors that contain www.sizmek.com in their href attribute.

       a[href^=mailto]  

    Returns all anchors that start with mailto in their href attribute.

     

  • A12: You can only use integers in the current MDX platform; however, you will be able to use floating point expressions in future versions of MDX.
  • A13: The Browser Events featuer records any mouse click event. If the mouse click event redirects the user to another landing URL that is also mapped by VersaTag, you don't need to use the Browser Events feature. However, if it doesn't (for example, with an outgoling link), you should use the Browser Events feature.
  • A14: – When you want to pinpoint a specific HTML element, you need a reference (distinctive hook point) that can be a CSS selector. If you are certain that a specific element cannot be identified using a CSS selector, use the API.
  • A15: – Instead of generating two VersaTag codes (HTTP & HTTPs) and having the webmaster implement both, you can use one instead.
    1. Generate a secure VersaTag code and send it to the webmaster for implementation.
    2. Clear the Force HTTPs option in the VersaTag settings > Save.

    This allows the platform to track both secure and non-secure pages without clashing with any security protocols on the advertiser's site.

  • A16: – There are two scenarios in which 3rd party tags can fire.
    1. Implement as a VersaTag 3rd Party Tag. This allows the 3rd party to capture site traffic regardless of when the Sizmek conversion tag fires. This is particularly helpful if you're trying to cookie a wider audience regardless of seeing a Sizmek ad. for more information, see HOW TO: Work with VersaTag 3rd Party Tags
    2. Piggyback a 3rd party tag directly on the Conversion Tag. This will only fire the 3rd party tag when Sizmek counts a conversion. In addition, this method also allows you to control any de-duplication settings. For more information, see HOW TO: Work with VersaTag 3rd Party Tags
  • A17: – Depending on whether the webmaster has competed any development work on the site, you may need to choose between these options:
    • Browser Events: Track the button code's CSS. Although this requires dev work, it is definitely worth while in the long run. For more information, see HOW TO: Add a Mapping Rule (Browser Events).
    • VersaTag API: Use an additional JS Snippet to trigger a fake URL. For more information, see REFERENCE: Advanced VersaTag Scenarios (Using VersaTag with Buttons).

    Note: As this requires manual implementation from the webmaster every time the agency want's to track a new button, it is recommended that the website is updated to include button ID's that can be tracked.

  • A8: The Sizmek VersaTag popup in test mode does not fire for a noscript tag. It only works if the advertiser implements the script version of our tag. See HOW TO: Test VersaTags.
  • A19: One of the reasons why a Mapping rule may not fire, even if the Mapping Rule set using the CSS Selector, is because the call to the VersaTag was aborted upon clicking the button. This happens when a button or link redirects to the same page immediately even before our VersaTag code is fired. To fix this, please have the site update the anchor tag to open a new page ( a target="_blank" ) so that our tag can fire without issues.
  • A20: Mapping rule on button (using VersaTag API) gets aborted as well when the current page redirects to a new page upon clickthrough or form submission. The webmaster should update their code and add a delay using setTimeout() before redirecting to the new page.
  • A21: The main difference is when the 3rd party tag will be triggered:

    • Type Conversion: Will be triggered only if containing conversion tag is triggered.

      For example: The advertiser, Concertified, runs a campaign on an ad network named bestAdNetwork. Concertified wants to have conversion data sent over to bestAdNetwork for campaign optimization. In this case, Concertified creates a 3rd party tag of type conversion, pastes the code that they received from bestAdNetwork, defines the deduplication setting to Fire when piggybacking conversion is attributed to site, and selects bestAdNetwork as the site.

      When a conversion is attributed to bestAdNetwork (and only for bestAdNetwork), the newly-created 3rd party tag will be triggered. 

    • Type Other: Will be triggered whenever there is a match to an mapping rule – regardless of conversion.

      For example, the advertiser, Concertified, creates segments in a DMP called myBestAudience, for each visit to an event page, using a segmentation pixel. Since Concertified already uses Sizmek Tag Manager on their webpages, the webmaster or CSM can create a mapping rule with a criteria for the event page URL that will trigger the appropriate myBestAudience’s segmentation pixel.

  • A21: This feature is protected by the following permissions:
    • VersaTag Permission: Mapping Rule View Only (clear this check box)
    • VersaTag Permission: Create/Edit Mapping Rules
    • Role: Client - VersaTag Agency
Was this article helpful?
4 out of 4 found this helpful
Have more questions? Submit a request

Comments