Rich Media and Interactive Units, Built Traffic-Ready

Rich media is worth building when there is something to interact with that a static frame cannot hold: a date-and-price check against your availability feed, a floorplan the viewer can page through, eleven properties placed on a map. If the interaction is a mouse-over that plays the animation everyone gets anyway, that is an HTML5 banner with a rich media invoice attached, and I will say so before quoting rather than after. What gets built: Expandable and interscroller units for desktop and in-app, built to MRAID 3.0 and wired for Open Measurement so viewability and invalid traffic are reported by the SDK instead of argued about after the flight. Delivery through Celtra, Flashtalking, Adform, Studio inside Campaign Manager 360, or a raw ZIP where the publisher insists. The ad server is settled in the first call, because a unit authored against Celtra templates and later moved to a hand-built DV360 ZIP is a rebuild, not an export. Weight and behaviour: The first 150KB is a complete, clickable ad. Everything beyond that subloads once the host page has finished its own work. A unit reaching 2.4MB in total is acceptable; a unit whose first frame weighs 900KB is not, whatever the publisher's stated cap allows. Animation stops. Sound stays off until the user asks for it. Nothing polls a third-party endpoint on a timer. The interaction is then designed against a failure list: what the unit does when the feed returns nothing, when the connection is a hotel lobby on 3G, when the publisher's page already sits at 90 percent CPU, when the panel opens hard against the viewport edge. Those four states are the work. The idea itself takes an afternoon. Feeds and dynamic content: Where price, availability or listing data drive the creative, I build against your feed spec: Studio dynamic profiles, Flashtalking FTC feeds, or a flat file you refresh on a schedule. Fallback copy is written for every field that can come back empty, and the unit ships with the feed deliberately broken in QA so you can watch what a bad Tuesday looks like before it happens live. What you receive: Source project, published units per placement, a QA sheet recording each build against the publisher's own spec, trafficking support with your ad ops team or agency, and a written record of every point where the design gave way. That last document is the one you will want six weeks in, when someone asks why the panel behaves differently on iOS Safari. Not included: Media buying and publisher negotiation. Film production; if the unit needs a fifteen-second cut, that is a separate commission with its own budget. Landing pages. Consent and CMP integration on your own property. Work in languages I cannot read, which means English and Dutch only, because I will not sign off on a headline I am unable to judge. Who this is not for: Anyone needing a unit certified against a publisher spec I have not seen, with a live date under three weeks away. Brands whose legal review has not started. Teams who want a showcase piece for an awards entry; that work is legitimate and it is not this. These units are judged on whether ad ops can traffic them without emailing me. Units that already exist: A unit failing QA at a publisher is a defined repair, not a rebuild, and it is quoted that way once I have opened the source.