Automotive Campaign Microsites

Problem

A car brand wanted to promote new models online whenever something new came out. Each campaign needed its own site that looked good, loaded fast and got people to take part. The sites also had to collect visitor details, with their consent, so the brand could follow up.

Approach

• I managed and coordinated the campaigns together with my team, and I built a large part of the sites myself.
• I worked with a designer who sent me the designs. At first they came as Photoshop and Illustrator files and later as Figma files.
• I cut the designs apart and built the pages in HTML, CSS3 and JavaScript. I kept them pixel perfect.
• Most campaigns had a small online game, and I wrote the game in JavaScript.
• I built the forms that collected visitor details, and visitors had to agree before they were saved.
• I did the same kind of work for other brands, such as a chocolate maker, using the same way of working.

Architecture and design decisions

• Each campaign was its own small site, built for one launch and one goal.
• The sites used plain HTML, CSS3 and JavaScript for the front end. The games ran in the browser.

Reliability and performance

• Search engine results mattered for these sites, so I paid close attention to loading times, performance and keywords.

Outcomes

• I delivered a series of campaign sites for new car launches.
• The sites collected visitor details with consent, as the brand wanted.
• I kept the pages true to the designers' work, down to the pixel.

Known gaps

• I have no numbers on visitors, game plays, sign ups or search rankings.
• I do not describe how the visitor details were stored or passed on to the brand.
• The page does not say how many campaigns I built or how long each one ran.
• I do not know if any of the sites are still online.