The MAL Targeting Script MAL Targeting requirements

Why we use a targeting script MAL like to ensure that only an optimal HTML5 experience will be trafficked. If there are issues with this, for example the advert does not look good in certain browsers, or for certain versions then they usually prefer a static to display. To facilitate this, they supply us as well as publishers with a targeting matrix.

Before I forget…production requests Otherwise, I would probably forget  [Footer] [Date]

The Targeting Matrix they send may look like this… [Footer] [Date]

…or this (for non-combined formats, the DHTML column will be the same as the HTML column) [Footer] [Date]

The process this end When we receive the targeting matrix we will check the following We will need to clarify any ambiguous targeting and distinguish where the publisher is targeting away and where we will serve statics. If there is any requirement to target any sort of scripted advert experience to unsupported browsers –such as Opera Mac, then we will need to clarify where we may not be able to satisfy their targeting needs. We then choose an appropriate version of the script to use. Here are a few:- For serving only a static to iPad:- MAL_Targeting_iPad_static_v3.js For serving an HTML5 advert to iPad 5+:- MAL_Targeting_iOS5.js Asahi site – if the above does not work:- MAL_Targeting_iPad_static_v3_ASAHI.js [Footer] [Date]

Adding the Parameters Once the targeting script is applied, a static will be served- unless you use parameters to say otherwise You have to add a new parameter where you need to target (or even exclude your HTML5). A fairly minimal HTML5 targeting string may look a bit like this:- MAL_Targeting_iOS5.js?MD_F=GE30&WD_F=GE30&MD _S=GE5.1&MD_S=GE5.1&MD_C=GE35&WD_C=GE35& WD_E=GE9&H5=1 [Footer] [Date]

Some of the older parameters will be much longer in size They will have duplicate parameters in there MAL_Targeting_iPad_static_v3.js?MD_F=GE28&WD_F=G E28&MD_S=GE5.1&MD_C=GE33&WD_C=GE33&WD_E= GE9&MH_F=GE28&WH_F=GE28&MH_S=GE5.1&WDEE= EQ11&WH_E=EQ11&MH_C=GE33&WH_C=GE33&H5=1 [Footer] [Date]

What the parameters mean Let’s break down a parameter WD_F=GE28 [platform][advert type][_ or further logic such as exclusion][browser] =[logical operator][browser version] [Footer] [Date]

What the parameters mean Platforms: Windows, Mac Advert Type: HTML5, DHTML Browser: Chrome, Firefox, Explorer, Safari Logical operators: GT (Greater), GE (Greater or Equal to), L So a parameter might look like ..... WD_F=GE28 [Footer] [Date]

You can create parameters by hand… …but it might be preferable to use the targeting string generator http://demo.mediamind.com/MAL/MM_Targeting_String_G enerator [Footer] [Date]

The order of the parameters matters For example if I add a parameter to target HTML5 to Windows IE9, and follow this with a parameter to then exclude HTML5 for IE11 only then we will see HTML5 on IE9 and IE10, but not IE11…. However if I set this the other way around (exclude IE11 and target IE9 and above) the exclusion logic will not work. [Footer] [Date]

What the script does not cater for Opera (just yet- but this could be amended for Windows Opera only). Android Unsupported browsers You can create new versions of the script, if a campaign demands it. [Footer] [Date]

Filtering I recommend being familiar with how filtering works on the platform. There are plenty of scenarios where we have had to use filtering:- Targeting platforms not covered by the targeting script To filter to alternative ads (i.e. Gyao – the Yahoo house advert) As a workaround (1x1 pixel) [Footer] [Date]

Quirks I have discovered Trying to target Internet Explorer below 5.5 will not work as a parameter, and will stop the targeting logic working there. You only seem to need the DHTML parameters to make your targeting work, the HTML5 parameters only seem to be there for the combined format and add an ‘extra layer’ of targeting logic for this format. [Footer] [Date]