search
top

Adobe SiteCatalyst extension is back and is.. simple.

The latest version (1.2) of Adobe SiteCatalyst extension for Flash Pro was just released. The first major change that can be seen form the beginning is a new screen just after the login.

Simple Tracking

Simple Tracking

This first screen will present two options: Simple Tracking and Custom Tracking. The Custom Tracking is the previously available way to track Flash applications. This version of the extension, adds a new simpler way for those that just want to track something fast and do not need customization.

This Simple Tracking will allow for three simple tagging workflows.

1. Tagging the widget

Track widget view

Track widget view

Just after logging in and selecting Simple Tracking from the previous screen all that needs to be done to track every displaying of a SWF is to select the report suite you need your data to be sent and check the “Track widget views” checkbox. If you enable debugging (conveniently placed on the left bottom side of the panel) you can see the following call being made by the SWF just at the beginning.

AppMeasurement Debug: http://a……m.112.2o7.net/b/ss/acralexqe/0/FAS-3.1.2-AS3C/s31989403446204?AQB=1&ndh=1&t=17/11/2010%2011%3A36%3A55%205%20-120&ce=ASCII&ns=a……m&cdp=2&pageName=Simple%20application&g=file%3A///C%7C/demo/Simple%2520application.swf&cc=USD&s=1680×1050&AQE=1
http://a……m.112.2o7.net/b/ss/acralexqe/0/FAS-3.1.2-AS3C/s31989403446204?AQB=1
ndh=1
t=17/11/2010 11:36:55 5 -120
ce=ASCII
ns=a……m
cdp=2
pageName=Simple application
g=file:///C|/demo/Simple%20application.swf
cc=USD
s=1680×1050
AQE=1

So, this was very easy. I have now a way to be notified each time somebody views my application. And of course not only this. SiteCatalyst infers a lot of other useful information out of this request.

As it can be seen, the pageName parameter is automatically filled with the widget name.

2. Tagging a frame

Tagging a frame

Tagging a frame

Two steps are required to tag a frame view: select the frame from the timeline and click the “Add tracking” button. To have more relevant information in the SiteCatalyst reports, you can specify a label for that tag and you will know how many users reached that frame. The generated call looks like this:

AppMeasurement Debug: http://a……m.112.2o7.net/b/ss/acralexqe/0/FAS-3.1.2-AS3C/s36277548735961?AQB=1&ndh=1&t=17/11/2010%2011%3A48%3A32%205%20-120&ce=ASCII&ns=a……m&cdp=2&pageName=Simple%20application%3A%3Ashow%20model&g=file%3A///C%7C/demo/Simple%2520application.swf&cc=USD&s=1680×1050&AQE=1

http://a……m.112.2o7.net/b/ss/acralexqe/0/FAS-3.1.2-AS3C/s36277548735961?AQB=1

ndh=1
t=17/11/2010 11:48:32 5 -120
ce=ASCII
ns=a……m
cdp=2
pageName=Simple application::show model
g=file:///C|/demo/Simple%20application.swf
cc=USD
s=1680×1050
AQE=1

You may notice that the pageName parameter now contains both the widget name and the frame name.

3. Tagging and object

Tagging an object

Tagging an object

Tagging an object is as simple as tagging a frame. There are however two differences. For an object, it’s instance name (in this case Cancel) will be used to identify the tag. Also for objects, a trigger event can be selected. By default the click event is selected.

Running the application and pressing the Cancel button that becomes visible on frame 31 will generate the following call to SiteCatalyst.

AppMeasurement Debug: http://a……m.112.2o7.net/b/ss/acralexqe/0/FAS-3.1.2-AS3C/s38168986542150?AQB=1&ndh=1&t=17/11/2010%2011%3A56%3A21%205%20-120&ce=ASCII&ns=a……m&cdp=2&pageName=Simple%20application%3A%3ACancel&cc=USD&pe=lnk_o&pev1=Simple%20application%3A%3ACancel&pev2=Simple%20application%3A%3ACancel&s=1680×1050&AQE=1

http://a……m.112.2o7.net/b/ss/acralexqe/0/FAS-3.1.2-AS3C/s38168986542150?AQB=1

ndh=1
t=17/11/2010 11:56:21 5 -120
ce=ASCII
ns=a……m
cdp=2
pageName=Simple application::Cancel
cc=USD
pe=lnk_o
pev1=Simple application::Cancel
pev2=Simple application::Cancel
s=1680×1050
AQE=1

The pageName parameter now contains a combination of the widget name and the button name. Also two other parameters are sent now: pev1 and pev2. This are the URL and the URL Name that are sent because this object related calls are sent as Custom Links.

This simple way of tagging a SWF will be most of the time sufficient. If this is not the case, you can always go to the Custom Tracking to benefit from the full power of SiteCatalyst customizations.

Leave a Reply

*

top