50 Cubes Unique namespace for PSF

new SocialViews implementation: http://apps.facebook.com/mwstage/

You will need to use one of our accounts to see this testing page. nathan.drake2006@gmail.com PW: interactive

http://ad.doubleclick.net/clk;260061084;84234886;j;pc=[TPAS_ID]

Lee's QA Ad: #261138769

Hi Cole,

The problem here is that you have the regular PSF deployment(TDP/Tmobile) mixed with the new multi-ad deployment (MTV). Both placements should use the new multi-ad deployment.

Remove references to the socialflex.js script and the socialflex.html iframe
Invoke SocialViews from the TDP placement the same way you do for the MTV placement
- mediabrix.newAd('MyAdName', socialVars);
- This will create a new instance of SocialViews with the name and socialVars you specify.

50 Cubes is currently using 2 deployment types:
- Multiple Ads Tag: MediaBrix PSF deployment for SocialFlex and SocialViews with unique JS namespacing and support for multiple tags on the same page. This is in use on the mbrix.50cubes/mallworld_adrail placement.
- Single Ad Tag: MediaBrix PSF deployment for SocialFlex and SocialViews with global socialVars. This Single ad Tag deployment is in use on all other SocialFlex and SocialViews placements on 50 Cubes' properties. Only one Single Ad Tag deployment can be used on a page at the same time, but it can be used with any number of ads the Multiple Ads Tag deployment.
MediaBrix will be releasing an update to the Multiple Ads Tag deployment in the latter part of Q3, at which point it will become our primary deployment type. It is recommended that 50 Cubes maintain their current mix of Multiple and Single Ad Tag deployment until the new primary deployment is ready for production. This will save the effort of having to retag and retraffic all 50 Cubes ad placements twice in a short period of time.