Web Analytics

Become the Web Analytics OFFICE HERO with Omniture's Site Catalyst Form Analysis Plug-in

Confusion around this Plug-in stops

where the rubber hits Conversion Road.

Darcy’s recipe for OFFICE HERO success may be all the rage, but this is the plug-in you want on your SUPER hero utility belt.

The Form Analysis Plug-in (“The Plug-in”) is a piece of JavaScript code that is inserted into the core Site Catalyst JavaScript File, s_code.js. This little baby is the BIG BROTHER of the forms on your site, watching your visitors take the tentative steps towards conversion or oblivion.

Although one of the more complex of the plug-ins, implementing The Plug-in can be as easy as 1, 2, 3, 4, 5

(Note: This post assumes that at least one other plug-in is implemented in your copy of s_code.js.
If not, Contact Us)

  1. Acquire the version of the Form Analysis Plug-in code (that is compatible with your implementation of SiteCatalyst) from your friendly Omniture Implementation Consultant.
  2. Insert the code into s_code.js in the designated “PLUGINS SECTION”
  3. Make the call to s.setupFormAnalysis() in function s_doPlugins()
  4. Set The Plug-in’s configuration parameters
  5. Insert “on-page” JavaScript code to send event data to Site Catalyst:
  • Success events in the form’s onSubmit event handler,
  • Error events as part of your client-side and/or server-side validation code.

… and then start watching your reports to see where your visitors are almost converting…

Steps 1 and 2 need no further explanation.

Step 3 looks something like this, depending on your pre-existing plug-ins:

function s_doPlugins(s) {
       // calls to other plug-in functions may already exist here
       // Form Analysis Plugin v.2.0
    s.setupFormAnalysis();
}
s.doPlugins=s_doPlugins;

NOTE: Suppress the urge to ask if strings are case-sensitive – they almost always are.

Step 4. Insert the configuration code in the “CONFIG SECTION”

This is where the business rules become JavaScript.
Today I deal only with the “how” of Form Analysis.
In a following post I will discuss the “why” of various configurations.

Which forms?

A comma-separated list of forms to be tracked by The Plug-in. Form names are those defined in the name attribute of the forms’

Cardinal Path

Share
Published by
Cardinal Path

Recent Posts

GA4 and BigQuery: why might data not match?

One of the most common questions we get about GA4 isn’t really about GA4, itself.…

3 weeks ago

GA4 + Optimizely: Integration Overview

Using engagement data to improve website performance is a near-universal use-case for users of Google…

2 months ago

Google Delays Third-Party Cookie Deprecation to 2025

Google announced on April 23 that it will again delay third-party cookie deprecation (3PCD) in…

3 months ago

This website uses cookies.