242/102/49 0/51/59 181/172/166 Primary colors 248/152/29 PMS 172 PMS 137 PMS 546 PMS /206/ /227/ /129/123 Secondary colors 114/181/204 PMS 148 PMS 7458 PMS 7457 PMS /79/75 PMS /166/143 PMS 487 © 2010 MediaMind Technologies Inc. | All rights reserved Group M Accounts Xaxis Integration

© 2010 MediaMind Technologies Inc. | All rights reserved Steps for Setup ▸ Once the Xaxis bring an advertiser onboard they’ll ask us to add this advertiser to the integration. ▸ We can do this by adding the advertiser onto their API login. ▸ The Xaxis account is Xaxis API Testing (34075) ▸ Get Tier 2 to add the Media Agency Account as a child account to the Xaxis account if it has not been added already. See next slide for correct way to submit a Case to Tier 2. ▸ Add the new advertise to the Xaxis.API.User (see screen grab on next page) Example: Adding the LG advertiser to the MIG.API.User

© 2010 MediaMind Technologies Inc. | All rights reserved Submitting a Case to Tier 2 Please refer to Case Number: CAS N99CVD In case, state Advertiser Name, ID, Account Name, Account ID Ask to link to MIG Account ID: Give all user ID’s under the Account Name

© 2010 MediaMind Technologies Inc. | All rights reserved Steps for Setup ▸ Let the Xaxis know that the advertiser has been added to the integration. They will send us the ZAP impression and click tracking tags (mookie tags) example ZAP tag: Impression Tag Click Tag %]&migRandom=[ebRandom]&migTrackFmtExt=ad;pl&migUnencodedDest=Place encoded destination URL here ▸ Add the ZAP tag to the advertiser (use the part in red only):

© 2010 MediaMind Technologies Inc. | All rights reserved Out Put ▸ The Xaxis integration means that you no longer need to add any ZAP (mookie tags) on the ad level. The integration adds the pixels on the placement level for you – this is reflected on the actual Mediamind generated tag. ▸ The Zap pixels will only be added to campaigns/placements that have been setup after the ZAP pixels have been added to the advertiser. They will not be added retrospectively to campaigns before the integration took place. ▸ The integration does not work on tracking only placements. Example Tag var gEbBAd = new Object(); gEbBAd.AClickUrl = " gEbBAd.playRS = new Object(); gEbBAd.playRS.strAUrl = " Ext=ad;pl";

© 2010 MediaMind Technologies Inc. | All rights reserved Tagging 1x1 Tracking Placements ▸ All 1x1 placements need to be hardcoded by Xaxis before being sent to respective publishers ▸ MM AM needs to request a Zap click tag that can be appended to the click thru url on the 1x1 placement Example of tag used for Motorola from Xaxis: DataExt=[%tp_AdID%];[%tp_PlacementID%]&migTrackFmtExt=ad;pl&migUnencodedDesthttp://t.mookie1.com/t/v1/clk?migAgencyId=43&migSource=mmind&migRandom=[ebRandom]&migTrack DataExt=[%tp_AdID%];[%tp_PlacementID%]&migTrackFmtExt=ad;pl&migUnencodedDest= Example of Zap tag applied to Motorola Click thru URL – This full string is what should be applied into the Click Through URL field in our system (Zap tag in red, client click thru in green): DataExt=[%tp_AdID%];[%tp_PlacementID%]&migTrackFmtExt=ad;pl&migUnencodedDest= hopmotorola.ca/photon4g/?WT.mc_id=db_NA_US-EN_TicketMaster_Photon4G_Preregistration_ Jul_2011&WT.mc_ev=click

© 2010 MediaMind Technologies Inc. | All rights reserved Tagging 1x1 Tracking Placements ▸ Once click thru url is properly applied the AM needs to generate the 1x1 placements and send them to their Xaxis contact. ▸ Xaxis will hard code the 1x1 tags and test them. Once they pass the test then Xaxis will send them back to MM contact to then send to the sites

© 2010 MediaMind Technologies Inc. | All rights reserved Known Issues ▸ The Xaxis integration is not supported on Create I-Frame tags. R&D are looking into this at the moment. ▸ Some ad servers may change our token. If you come across this, please ask Global Support to look into this. B3 Network is one of the known sites that replaces our tokens. Please reach out to Global Support if this site is on the media pla ▸ Some sites do not allow 3 rd party pixels to be fired from our ads. We have asked Product to provide an ‘opt out’ option in the site account level.