We’ve been doing some sole searching 👞
Original publication date: October 21, 2020
Hey smartx-ers,
You’re probably wondering how we have managed to do two releases in one week. Well, the truth is, all this time at home has allowed us more time to focus on tech and less on fashion. That’s right, we’ve been wearing Birkenstocks all summer and just whipped out the Uggs for the winter. Comfy shoes are our go-to when working from home (with an iron-pressed shirt for video calls, of course).
So, what’s your go-to non-fashionable shoewear for working from home?
We know the Dutch office’s choice 😉…
To clog or not to clog 🤔
Broadcasters who run sponsored content need to make sure that conflicting advertisements do not run on the sponsored inventory. We basically don’t want to see a Crocs Clogs pre-roll when we’re watching a documentary about how Klaas’ Klompen (a local Dutch shoe shop) is bringing wooden clogs back to the mainstream with their orthopedic wooden design.
We originally addressed this potential situation in smartx by excluding different IAB categories such as Style & Fashion via the Supply tab (if we’re allowed to consider clogs fashion 😳). We’re taking this a step further to allow for more specificity by whitelisting the sponsor itself. This means they can exclude the IAB category Style & Fashion and whitelist the Klaas’ Klompen domain to override the settings so that they are the only fashionable footwear allowed to advertise during that segment.
Users can whitelist a domain under Master Advertiser in the Exclusion tab when adding/editing Publishers, Sites & Apps, and Placement Groups.
Overriding exclusions is only necessary if there are Master Advertisers, Brands, or Category exclusions selected as well. If this isn’t the case, you can simply switch to Inclusion mode and whitelist an adomain.
Bug Fixes 🐛
- We used our new clogs to squish a bug in the Supply Business Rules edit dialogue that sometimes caused more sites to be selected than intended when using the Move to Selected button.
- A little worm was causing macros for Companion creatives with the iFrame Code type to not be replaced or sent correctly. Squishing this guy felt a bit vulgar so we gently moved him to a new plot of dirt far, far away from smartx. (If you hear someone complaining about nibbled macros out there, that’s him. We named him Jeremy before we let him go.) Additionally, we added Width and Height fields to the iFrame URL in order to make sure all measurements are accurate.
Yours in smartx updates and trying to find the fine line between which bugs are acceptable to squish and which ones you should relocate,
smartclip Product Marketing Team
