Learning Center
Plans & pricing Sign in
Sign Out

Offermatica Implementation

VIEWS: 147 PAGES: 40

									Offermatica Framework
Architecture Analysis

June 14, 2007Implementation Tactics
Offermatica Overview

Offermatica is a hosted software platform that specializes in:

 – Website Personalization - The delivery of a customized visitor experience
     based upon attributes and behaviors of a site visitor as a means to drive
     improvements to conversion rates and revenue.

 – Campaign/Content Delivery – Dynamic delivery of HTML / Presentation Layer
     Assets specifically related to Promotional & Personalization Campaigns.

 –    Conversion Enhancement - The practice of testing different attributes of
     visitor experience in the attempt to increase conversion rates usually by
     deploying multivariate optimization tests, viewing the visitor and his/her
     relationship throughout the entire customer lifecycle, from demand
     generation through purchase.

Offermatica’s many features roll up into these 3 functions.
Offermatica Overview

Offermatica’s features include:

 – 1. Content Delivery — Campaign HTML / Presentation Layer Assets delivery.
 – 2. Category Affiliation — Dynamic Product / Service / Support featuring based on
     customer's behavior or profile.
 –   3. Automated Product Suggestions — Automatically features top selling or most viewed
     product / service item (FAQ’s, User Guides, Phones etc).
 –   4. Customer Profiling Targeting — Dynamic customer profiling (such as Residential vs.
     Business, etc.) for targeted content and behavior driven personalization.
 –   5. Geo Targeting — Dynamic promotions or messages based on customer's location.
 –   6. Behavioral Targeting — Dynamic promotions or messages based on customer's
     interaction with the website.
 –   7. Source Targeting — Dynamic promotions or messages based on customer's referring
 –   8. Time Targeting — Dynamic promotions or messages based on time of day or day of
     week (i.e. work week vs. week end).
 –   9. Multivariate Testing — Optimization test to streamlining campaign conversion rates.
 –   10. External Banner / Ad Testing — Optimization tests on EXTERNALLY hosted ads on
     affiliate networks via Adbox functionality.
 –   11. Email Multivariate Testing — Optimization tests on EXTERNALLY delivered email
Offermatica Adoption

There are four levels of Offermatica Adoption
Promotional vs. Personalization:
 – Promotional -– Minor implementation of Offermatica to deliver promotions
     such as banners or ad campaigns.
 –   Personalization –- Integrating Offermatica functionality directly into the
     website skeletal framework as a presentation layer framework.

A/B Testing vs. Multivariate Testing:
 – A/B Testing -- Sometimes referred to as "split tests," an A|B (|C|D)
     optimization test is black-and-white comparison that attempts to determine
     the impact that one site element, e.g. design or content, has over another
 –   Multivariate Testing -- Where A|B tests compare black and white
     differences, multivariate tests look at the varying shades of gray. Typical
     multivariate tests are designed to look at a larger number of placeholders on
     a page, and test variants of each, the potential number of permutations to be
     tested can grow very quickly.
Offermatica Adoption Analysis

So, where are we?    A/B      Multivariate
                    Testing     Testing

    Promotional      Mostly      Not yet

 Personalization     Barely      Not yet
Offermatica Adoption Analysis

What this means is that our Offermatica Implementation is not
yet complete, or at least, it is not using the tool to its full
potential, where it is most valuable.

 – The bulk of our tests are related to swapping out promo banners, occasionally
    with accompanying changes in website.

Recently, however, we have started to work with Customer
Profiling and Geo Targeting.

 – This is very promising. Our implementation of these advanced techniques is
    in its infancy, however, we are already aware of Portal implementation
    shortcomings, and although a more complete implementation strategy is
    currently being developed, we have solidified our technical implementation
    tactics for what is in use today. Going over those implementation tactics is
    the primary focus of this presentation.
Offermatica Promotional Adoption


                                   Dynamic Banner Delivery, A/B/C/D Testing
               Promo Banner mbox   Ultimately leads to Campaign Conversion

   nav             body


          Example of Today’s Implementation
Offermatica Personalization Adoption

               header                     “You searched for High Speed Internet on
               Source Targeting mbox
                                                “Welcome back, John Smith”
             Welcome $ mbox

                                          Residential Customer links / action region

              Category Affiliation mbox

   left                                     Multivariate Intelligent Offer based on
                            Automated        customers existing products, etc.
   nav        Intelligent    Product
              Offer mbox    Suggestion
                                          Automated “Top Selling” Product Offer or
                                mbox           “Most Viewed” FAQ link, etc.
                Recently Viewed mbox
                                          Recently Viewed Categories or Products
                 Geo Targeting mbox

                                            “A new store has opened near you!”


          Example of Implementation Potential
Offermatica Basic Implementation

So how does it work?
STEP 1: Include “mbox.js” file into our website.
 – This javascript file is the engine that powers Offermatica on our website.
STEP 2: Insert an “mbox” into our page around default content.
 – The mbox is the region on your web page where we can swap content for
    visitors, it is also a means of logging visitor behavior in real-time.

STEP 3: Upload an HTML “offer” into the Offermatica online
 – These offers are merely a snippet of HTML code that will replace the default
    content in the mbox.

STEP 4: A “campaign” needs to be created with a “recipe” that
will use our uploaded “offer”.
 – Offermatica campaigns can contain multiple recipes that utilize different
    offers—that’s where the A/B and Multivariate Testing begins.

That’s It! But let’s see that in more detail...
Offermatica Basic Implementation

  STEP 1: mbox.js is a standard javascript file that is already
  installed on our website. There is now an updated version that
  we will soon test and deploy which provides new functionality.
 Offermatica Basic Implementation
STEP 2: An mbox is just an (1) HTML <div> with a unique id and a
class=“mboxDefault” followed by a (2) <script> that calls the function
“mboxCreate(uniqueID)” passing along the unique id.
 – The <script> tag must immediately follow the mbox </div> tag and the <div> tag’s unique id
    should match the unique id being passed in the mboxCreate() function—that becomes the
    mbox’s name. In addition, we can also insert HTML comments before and after the mbox
    for extra documentation.

                  Before                    After
                  <head>                    <head>
                  </head>                   <body>
                  <body>                    <script src=“"
                  My existing page.         type=“text/javascript”></script>
                  Part that I'd like to     My existing page.
                  overlay during a        1 <div id=‘myMbox’ class="mboxDefault">
                  campaign or test.            Default content that will be replaced.
                  </body>                   </div>                                    mbox
                                          2 <script type=“text/javascript">
Offermatica Basic Implementation

  STEP 3: An Offermatica “offer” is just a snippet of HTML
  code that will replace the default content in the mbox. This
  must be entered into the Offermatica online application as a
  new “offer” under the Offers tab.

                      HTML offer code
    Offermatica Basic Implementation
         STEP 4: A “campaign” needs to be created with a “recipe”
         that will use our uploaded “offer”.
          – Only one recipe is needed for a campaign to run and for an offer to be
             delivered, however, for a Multivariate Test to run, multiple recipes are
             required, each mapped to a different offer.


Recipe                                                                                  Offer
                                       mbox to deliver offer
 Offermatica Basic Implementation

Before: Instead of
seeing the default
content here…

After: The Offermatica
campaign offer content
is displayed.
The DOM Swizzler Technique

 Think “Outside the Box”…Introducing the DOM Swizzler
  – The Offermatica Basic Implementation can also deliver Advanced Offers such as the
     DOM Swizzler.

 DOM Swizzler is just Javascript.
  – As previously stated, “offers” are HTML code or Presentation Layer Assets—this also
     includes Javascript and CSS. Using Javascript and accessing the Document Object
     Model (DOM—the open document API inherent in all browsers), offers can deliver
     javascript code via an mbox that can deliver campaign related content outside of the
     mbox. Offermatica calls this technique the “DOM Swizzler”.

  – DOM Swizzler offers and content changes only happen in a customer’s browser at the
     presentation layer only—no back end systems nor server sided code are capable of
     being affected. However, to the customer, the experience has changed and a
     campaign offer has been dynamically delivered.
The DOM Swizzler Technique
 To Implement a DOM Swizzler offer, directly enter the javascript into
 the “offer” section of the Offermatica online application and run as a
 normal campaign. Here’s an example DOM Swizzler offer:
Offermatica Advanced Implementation

 Offermatica has many additional features that we are just beginning to
 tap into, and sometimes even our basic implementation offers must
 utilize a more dynamic approach.

 Our current Advanced Implementation can be summarized into two
 basic categories:

  – Advanced mbox implementation – Special mboxes used for specific functions of a
     campaign as well as mboxes implemented using different tactics.

  – Customer Profiling – whereas our customer profiling strategy is still being developed,
     our customer profiling tactics are a category in their own right.

 “Automated Product Suggestion” functionality as well as other
 Personalization-related functionality are also considered Advanced
 Implementations, however, since we have not yet implemented these
 functionalities, this will require further research and implementation
 testing before this can be added to our list.
Advanced mbox Implementation
 Mboxes can be classified in two ways:
  – Different mbox functions -- the way an mbox is used in a campaign
  – Different mbox implementations -- the way an mbox is implemented into a

 The different mbox types by function are:
  –   Static mbox
  –   Conversion mbox                                             mbox2
  –   DOM Controller mbox                                 mbox1
  –   Asynchronous mbox
  –   Recorder mbox
  –   Profile mbox

 The different mbox types by implementation are:
  –   Static mbox
  –   Dynamic mbox
  –   Nested mbox
  –   Injected mbox
                Advanced mbox Matrix
                                       Implementation Type
                                  Static Dynamic Nested Injected

Function Type


                DOM Controller



Advanced mbox Naming Conventions
 There are so many different types of mboxes that we needed to
 establish a naming convention in order to easily understand and
 communicate our implementation.
 Based on the Advanced mbox Matrix, the naming convention that we
 use is “{Implementation type},{Function type} mbox”. Such as:

  – A “Dynamic, Conversion mbox” or
  – An “Injected, DOM Controller mbox”

 “Static” refers to a non-dynamic, non-specific mbox—it’s a standard,
 regular mbox, and since it is listed as both a function and an
 implementation type, it can effectively be omitted and simply implied,
 as seen here in:

  – “Recorder mbox” (ie. a “Static, Recorder mbox”)
  – “Nested mbox” (ie. a “Nested, Static mbox”)
  – “Conversion mbox” (ie. a “Static, Conversion mbox”)

 But enough about the names, let’s find out more about the different
mbox Types by Implementation

 Static mbox
  – Description: Simply referred to as an “mbox”, this is the same type implemented in
      the Basic Implementation example previously.
  –   When to use: This mbox is used whenever an mbox can be manually implemented
      into a page using a hardcoded unique id (mbox name).
  –   Implementation: Since we’ve already discussed this previously, the only additional
      aspect worth mentioning is the naming convention. When implementing multiple
      mboxes into a page, we use a unique abbreviation for that page, like “UHP_” for the
      Universal Home Page, followed by “res” for Residential or “bus” for Business if
      appropriate and then a camel cased or capital unique identifying section such as
      “Links” or “Hidden” or “bottomContent”.
        •   EXAMPLE: “{abbreviation}_{‘res’/’bus’}{‘links’/’bottomContent’}” (ie. “UHP_resLinks”)

  – For implementing mboxes for promo banners we start with “pb_”, followed by “res”
      or “bus”, followed by a page description such as “specialoffers”, “listing”, or
      “landing”, followed by “pos” and then a number incrementing from 1++ for each mbox
      on the page.
        •   EXAMPLE: “{pb}_{‘res’/’bus’}{‘SpecialOffer’}_{‘pos’}{‘1’}” (ie.
     mbox Types by Implementation

          Dynamic mbox
           – Description: a Dynamic mbox is an mbox with a dynamic name, meaning the
               name is determined dynamically.
           –   When to use: This mbox is used whenever an mbox must be implemented into a
               template page that multiple products use (such as the product detail template
               that results in many pages to a customer all from the same template shell).
           –   Implementation: The idea here is to hardcode the mbox as much as possible, but
               before the “mboxCreate()” function is called, we dynamically rename the mbox
               based on a unique parameter in the page such as the “pageLabel” that Omniture
               uses as a unique page name. Here is sample code:

   Create unique id
from dynamic variable

Output a generic mbox
 with a generic name

Rename the mbox and
 mboxCreate() using
the dynamic unique id
       mbox Types by Implementation

            Nested mbox
              – Description: a Nested mbox syntax is the same as a static mbox, but it is
                  delivered as part of the offer content of another mbox.
              –   When to use: Offermatica campaigns are limited to ONE campaign per mbox,
                  however, we often have multiple campaigns running on the same page due to
                  overlapping promotions while only one mbox on a page—the nested mbox
                  implementation addresses this issue.
              –   Implementation: The nested mbox is identical to a static mbox, but it must be
                  delivered in the offer code from within the Offermatica online application. Here
                  is sample code:
The “Parent” mbox offer
  delivers only Nested
   mbox “Children”                                              mbox

 The Nested mbox first
child delivers a campaign                                Nested mbox

The Nested mbox second
 child delivers a different
                                                         Nested mbox
      campaign offer
     mbox Types by Implementation

          Injected mbox
           – Description: an Injected mbox is an mbox that is injected into the page using
               DOM Swizzler code / javascript.
           –   When to use: This is used when an mbox is required in a page where one is not
               present or when an mbox needs to be fully dynamic such as with a profile mbox or
               DOM Controller mbox and can be delivered via a javascript file.
           –   Implementation: The code for an Injected mbox is regular javascript using the
               DOM. Here is sample code:

  Create unique id

Create the mbox <Div>

  Create the mbox

 Inject the mbox into
 the page DOM in the
     proper order
mbox Types by Function
 Static mbox
  – Description: a regular mbox used for swapping out offer content.
  – When to use: Use a static mbox wherever possible, hardcoding the mbox directly
      into the page, especially when swapping out promobanners or entire blocks of
  –   Implementation: The code has already been covered previously, but it is worth
      noting that the static mbox implementation is quite flexible; you can insert a
      single mbox around a content block or table, multiple mboxes in one page or an
      mbox around an entire page.
 mbox Types by Function
     Conversion mbox
      – Description: any mbox typically at an order or process confirmation page used to
          track completions of a task or conversions.
      –   When to use: Any mbox can be set as the conversion mbox depending on the
          campaign such as at form completion pages, order confirmation pages, or sign-up
          confirmation pages.
      –   Implementation: Any implementation will work since any mbox can be set to be
          the conversion mbox of a campaign from within the Offermatica online


landing page                        other pages                              confirmation
     mbox Types by Function
         DOM Controller mbox
           – Description: a static, dynamic, or injected mbox used solely for the purpose of
               delivering Nested mboxes for multiple DOM Swizzler campaigns.
           –   When to use: Use a DOM Controller mbox on any page where a DOM Swizzler
               campaign needs to run, especially on high profile pages or pages with multiple
               campaigns running simultaneously.
           –   Implementation: Any mbox can be a DOM Controller mbox, but in order to avoid
               conflicting campaigns and confusion, it is best if it is a standalone mbox that does
               not deliver campaigns itself but rather is charged only with delivering the number
               of Nested mboxes for that a page requires, so long as all the Nested mboxes are
               running DOM Swizzler campaigns / offers.

  The DOM Controller
  mbox offer delivers
  only Nested mboxes                              DOM Controller mbox

 The first Nested mbox
delivers a DOM Swizzler                                   Nested mbox
     campaign offer

The second Nested mbox
 delivers a DOM Swizzler
                                                          Nested mbox
      campaign offer
  mbox Types by Function
     Asynchronous mbox
      – Description: any mbox used for swapping out offer content driven by events or
          customer interaction.
      –   When to use: We won’t be able to implement this functionality until we upgrade to
          the latest mbox.js file, but basically, an Asynchronous mbox simply doesn’t load
          until after a customer has performed some action on the page, reacting to customer
          interaction. With that in mind, we could potentially use Asynchronous mbox
          functionality to set Customer Profile data dynamically based on customer behavior
          within a page.
      –   Implementation: Any mbox code will do since any mbox is capable of this function
          (with the new mbox.js file). The key to this functionality is due to a the new
          “mboxUpdate()” function (vs. “mboxCreate()”).

Any mbox is eligible                  Triggered by onclick           The mboxUpdate() function
                                      event—event driven             passes the mbox unique id
                                         and interactive            and “active=1” as parameters
                                                                    to activate the Asynchronous
                                                                    loading of the targeted mbox
  mbox Types by Function
       Recorder mbox
         – Description: also known as a “reserved name” mbox, it is a special mbox that
             MUST follow a specific syntax for Advanced Functionality such as “Automatic
             Product Suggestions”. They records details about your products and categories,
             permitting reports on sales data, orders, and Automated Product Suggestion
         –   When to use: Use whenever implementing “Automatic Product Suggestions” or
             other similar Advanced Functionality.
         –   Implementation: The code must follow Offermatica’s examples exactly. More
             information can be found at, and we’ll dive deeper into this
             as we begin implementing more customer personalization features, but here’s a
             sample of a “orderConfirmPage” Recorder mbox:

Essentially a Static                   Recorder passes order
      mbox                                data as mbox
                                      parameters; syntax must
                                             be exact
                                                                      Products are comma dilemited
      mbox Types by Function
        Profile mbox
          – Description: a dynamic, nested, or injected mbox used solely for setting Customer
              Profile data.
          –   When to use: Use on any key page where Customer Profile data can be set—home page,
              MyAccount Landing page, Customer Behavior tracking pages possibly in combination with
              Asynchronous mbox loading functionality, etc.
          –   Implementation: The code is basically the same as any dynamic, nested, or injected
              mbox, however, the mboxCreate function sends additional mbox parameters—profile
              parameters—that are saved to a customers Offermatica profile. We can create and
              utilize any profile parameters we want, but we must follow specific syntax. The
              profiling strategy is still being finalized, but for instance, we can capture any customer
              session data or Omniture variable data that would be relevant to segmentation:

Portal accesses User                    Portal outputs session
    Session Data                          data to javascript

                                                                              Customer Profile parameters
                                                                             are passed as mbox parameters
Customer Profiling

  Customer Profiling is done through setting Profile parameters.
  Profile parameters are specific to the visitor and are passed to the
  visitor's cookie. As the visitor continues to browse, or returns for
  another session, with Offermatica we can use the saved profile
  parameter values to deliver targeted content, increase relevancy,
  and ultimately lead to a higher conversion rate.
   – “Returning visitor” and “Category Affinity” are examples of profile parameters

  At this time, the only Profile parameters that we have set are a
  customer’s “city”, “state”, and “country” due to a GEO Targeting

  Once a Profile parameter has been set, we can also use the actual
  profile values that have been set per customer for personalized
  content or to drive dynamic logic.
     Customer Profiling – GEO Targeting

         GEO Targeting
           – Description: delivering targeted content relevant to a customer’s physical location
               as determined by a reverse IP lookup.
           –   When to use: We’re already using this to tell customers when a new store has
               opened in their areas—with our diverse territorial regions, GEO Targeting opens up
               many possibilities.
           –   Implementation: The IP lookup is done via outputting a <script> that points to an
               Offermatica server. The server runs the IP lookup service and automatically sets
               the customer’s “zip”, “city”, “state”, and “country” Profile parameters (however,
               we were not as of yet seeing data at the zip code level—we are still researching).
               The following code is delivered via a Profile mbox offer and then an Offermatica
               campaign uses the Profile parameters for conditional logic:

GEO Targeting <script>
 dynamically delivered
 via Profile mbox offer
                                                                            NOTE: This script is
                                                                            actually on one line
         Customer Profiling – GEO Targeting
      Although GEO Target Profiling has now been moved to the Home Page, originally the
   “pb_storeLocations_pos1” mbox delivered the GEO Targeting <script> with a Nested mbox
        called “GEO_whatever” that was instantly able to use the customer’s location to
                   dynamically output a GEO Targeted message (in purple)

NOTE: This was the first implementation—since then,
    the implementation tactic has improved to
become more long-term and useful via a Profile mbox
Customer Profiling – Token Replace
    Profile Token Replace
     – Description: a method to retrieve every Profile parameter value that has been
         set for each customer to output the Profile parameter values directly into our
         page content or to be used in DOM Swizzler code.
     –   When to use: We have not used this functionality yet, but potentially we can
         output personalized messages for a customer such as “Welcome back, John
         Smith” or to provide a personalized user experience such as redirecting customers
         directly to “” if we know they are a Business customer, etc.
     –   Implementation: The Token Replace is a simple syntax that must be followed for
         it to work properly, and the Profile parameter you are looking for must already
         exist or else your token will be replaced with a blank “nothing”. Enter the profile
         token in the offer code and Offermatica’s servers will replace it with the
         appropriate customer’s data by the time the offer is delivered to the customer in
         the mbox. Here’s the example:

Before – in the offer code             After – in the mbox

                                                  Welcome back, John Smith.
Welcome back, ${}.
Offermatica & the “Metrix Toolkit”

  All this dynamic functionality can be difficult to test and
  troubleshoot. Fortunately, it all runs on front-end, presentation
  layer code, and is therefore quite open to us with the right tools.

  Offermatica has provided a very robust “Preview” tool and other
  dynamic parameter commands that are quite impressive. I’ve built
  a few tools on my own and have expanded upon what they’ve

  For anyone who involved with Offermatica, whether on the code
  side or the campaign side, I recommend the “Metrix Toolkit”
  located here:
Offermatica & the “Metrix Toolkit”

  metrixTools is a bookmarklet.
   – A bookmarklet is a small JavaScript program that can be stored as a URL within a
      bookmark in most popular web browsers, or within hyperlinks on a web page.
      Bookmarklets can be saved and used like normal web page bookmarks. Therefore,
      they are simple "one-click" tools that can add substantial functionality to the

   – In order to add the metrixTools bookmarklet to your browser, in Internet Explorer,
      simply "right-click>Add to Favorites" or, in Firefox, "right-click>Bookmark This
      Link". If asked to confirm, click "Yes", and save these bookmarklets in your
      "favorites" folder for easy access.

  What does the metrixTools do?
   – This bookmarklet launches a mini popup window
       with a select box that contains the other metrix
       bookmarklets--this is the only one you need.
       metrixTools launches in a popup window, so be
       sure to allow the popup for the domain you are
       working in.
Offermatica & the “Metrix Toolkit”

  –   This bookmarklet allows you to test websites for Offermatica mboxes. When clicked, this
      bookmarklet shows you the Offermatica mboxes installed on the current page you are viewing
      along with the mbox name all in bright "red". Clicking on the mbox name alerts the content
      contained within. This helps you research mbox names and locations when planning new
      campaigns or editing existing Offermatica content.

  –   This bookmarklet allows you to "see Recipes" in order to test recipe offers in an Offermatica
      campaign. When clicked, this bookmarklet shows you the Offermatica mboxes that are currently
      running an active campaign that has multiple recipes--it highlights the mboxes in bright red with
      the word "Recipe" inside that, when clicked, launches the Offermatica Preview Console. Using
      the Preview Console you can select the recipe you want to view in the active campaign that you
      clicked to verify its offer content.

  –   This bookmarklet turns on the Offermatica "Debug Mode", launching a popup which shows you
      the mbox campaign data returned from Offermatica for the current page you are viewing. To
      exit the debug mode, simply "click" the bookmarklet again.

  –   This bookmarklet toggles Offermatica "ON" or "OFF". In the "OFF" mode all campaign offers and
      dynamic content are disabled so you see only the default content. To turn Offermatica back on,
      simply "click" the bookmarklet again. NOTE: Due to the configuration of the Portal for SEO,
      the Portal now strips away this parameter keeping it from running. I have logged that as a
      defect to address with IT and have this corrected as soon as possible.
Offermatica & the “Metrix Toolkit”

  –   Tired of having to delete your cookies, clear your cache, and open a new browser to view a
      different mbox campaign recipe? With a simple "click", this bookmarklet deletes all your mbox
      session cookies and reloads the page for you allowing you to be treated as a "first time" guest
      and possibly recieving different Offermatica campaign data--provided that you qualify as being
      one of the appropriate random percent. Roll the dice!

  –   This bookmarklet is just a link to where you can find much more
      documentation and useful implementation advise.

  –   This bookmarklet launches my very own DOM Swizzler Console that is a must for any developer
      charged with developing DOM Swizzler code for Offermatica campaigns. The DOM Swizzler
      Console launches in a popup window, so be sure to allow the popup for the domain you are
      working in—there are a lot of useful resources there to help speed up your DOM Swizzler
      development or to simply troubleshoot your campaigns.

  –   This bookmarklet launches a popup that will tell you if the Embarq Metrics Resource Script (MRS)
      is installed on the page you are viewing. If MRS is installed, it will list out the MRS dynamically
      installed javascript files as hyperlinks to be downloaded for further research. It also contains a
      link to the MRS file directory in Production to quickly reference MRS entries for vendors and
      Embarq platforms.
Offermatica & the “Metrix Toolkit”
   –   Although not directly related to Offermatica, This bookmarklet launches the "Omniture
       Debugger", a popup which shows you the Omniture data that is being tracked on the page you
       are viewing at that time. If you launch an Omniture Event by clicking on a tagged link or button
       on the page, the Omniture tracking data will change and you will have to re-launch the debugger
       to see the results.

   –   This bookmarklet lets you decode an Omniture Image Request string (mostly for testers),
       showing you what data is being sent back to Omniture to be tracked. This is especially helpful
       when trying to debug Omniture onClick Events. Just copy the Image Request from Charles or
       Firebug (packet sniffers) and paste it into the prompt generated when you run this bookmarklet
       and it will decode the URL Image Request data for you.

   –   This bookmarklet launches an alert box that displays all the cookies you have set at that current
       website domain. This is helpful when troubleshooting Offermatica campaigns as well.

   –   This bookmarklet will ask you to confirm and then delete all the cookies that you have set at
       that website domain. This same functionality can be found in your browser at "Tools>Internet
       Options>Delete Cookies" for Internet Explorer, "Tools>Options>Cookies>Clear Cookies Now" for
       Firefox. Please Note: If you are logged in and you delete your cookies, you will have to log in

To top