SiteCatalyst - Suppress initial page view and still set s_account

[tkoscinski]

I've been searching for the solution to this but have been having no luck.

I'm trying to use the SiteCatalyst tag within an iframe to pass data to omniture from a video player.  The video player fires two omniture beacons based on the utag_data object within the iframe.  The issue I'm having is that I need to suppress the initial page view within the iframe, while still having the ability to set the s_account value in the SiteCatalyst tag based on UDO variables set via extensions.

When I run the tag with the page view in place (default implementation), everything fires as expected and goes to the correct s_accounts assigned through Tealium.  The issue comes when I try to do one of the standard view suppressions I have tried - utag_cfg_ovrd = {noview : true} in the page source before utag.js, or return false on initialization of the SiteCatalyst tag.  When I do either of the the suppression techniques, the initial page view is suppressed, but the omniture beacons that fire from the player go to the default s_account set on the tag as opposed to the values I'm trying to assign via UDO variable. 

To sum it up - with no suppression, everything fires fine (mappings all work).  When suppressed - UDO variable mappings are ignored and beacons are mapped to default SC Report Suites.

Any insight into this use case would be appreciated

[tkoscinski · Accepted solution]

Ok, I actually solved this issue myself but I'll put the solution here for posterity

Basically what I needed to do was set the s.account value before setting the return false; value in an extension with the SiteCatalyst tag as the scope -

if(a == 'view'){
  s.account = b['_scAccount'];
  return false;
}

The above checks if there is a view fired and sets the s.account value to the _scAccount UDO variable value prior to suppressing the page view.

[kathleen_jo]

Great job @tkoscinski and thank you for sharing!