50 Cubes TDP

1.7 rollout :
- unique JS namespace
- callbacks for social flex
- multiple sets of socialvars in the same scope
- more robust Youtube integration
Placements:
- TDP - 1.5
- ad_rail - custom views (early 1.6)
- FashionShow Energy - views
- FashionShow Post - flex
New package (1.7) over for assessment
- Supported Browser matrix from RC
50 Cube's next sprint starts Monday!!
No frequency caps on ZZ TDP

After reviewing 50 Cube's TDP placement last week and this week, our tech team have hit a wall as to why this error is occurring. We've ruled out problems with our ad code and believe the issue is with the complexity of the TDP placement, namely the dynamic swapping of socialVars during gameplay. At present, we cannot consider the TDP placement to be certified to run SocialViews ads.

Our tech team is immediately available to work with 50 Cubes' dev team to correct the issue with the TDP placement. As a temporary solution, our Ad Ops team will try to work with 50 Cubes' team to traffic SocialViews ads to alternate placements.

To recap, the error we are seeing occurs if the rewardConfirmation callback or the UID is not defined. It was reported by Ad Ops on Dec 2. After taking a look at the MallWorld TDP, Darren and I noticed that it is one of the placements where 50 Cubes is swapping socialVars during game play. This is 50's solution for having SocialFlex and SocialViews on the same page without upgrading to our new tag structure. TCS reached out to 50 Cube's to have one of their devs look into it last week but they didn't find anything. I don't know how exhaustive the investigation has been on 50's side. This landed back on my plate on Monday and I've spent close to 7 hours trying to suss out what's going on since. My recommendation is that we proceed with re-onboarding 50 Cubes to the 1.7 tags. That should allow us to have a consistent experience across all of their placements.