Multi-language campaign landing pages

High volume, hard deadlines

A large share of agency work is campaign landing pages: focused sites built to convert traffic for a specific enterprise marketing push. Individually they are small; collectively they are a discipline of their own. Launch dates are fixed by the client's media spend, not by engineering, and the page has to be right on day one because a campaign might only run for weeks. I have shipped many of these for enterprise technology clients, and the interesting work is in doing them repeatedly, quickly, and without the quality slipping.

One stack, five languages

The pages are built with Nuxt and Vue, generated as static sites and deployed with continuous delivery, so a push to the repository becomes a live deployment without a manual release step. Campaigns regularly run across European markets in English, French, German, Italian and Spanish. All copy flows through the i18n layer, and the layouts are designed to survive translation, because German headlines and French sentence lengths will break any design that only ever saw English. Localised copy arrives from the client through account managers, often close to launch, so the i18n structure has to make late copy changes cheap.

Security headers and measurement

Enterprise clients audit what ships under their brand, so these pages carry strict Content Security Policy headers, locked down to exactly the sources the page needs. That gets awkward precisely because of the other requirement: measurement. Campaign pages exist to convert, so they carry Google Tag Manager, LinkedIn Insight Tag for B2B conversion tracking, and Hotjar for behaviour analysis, and every one of those scripts has to be reconciled with the CSP rather than the policy quietly loosened. On the larger campaigns, Playwright end-to-end tests cover the critical paths.

The outcome is the cadence

There is no single hero metric for this work; the honest outcome is the delivery record. Campaign after campaign shipped to immovable dates, in up to five languages, with tracking that satisfied the marketing team and headers that satisfied security review. Most of these I shipped single-handed, from brief to deployment. The volume is also what built my instincts for scoping: after enough of these you can look at a brief and know where the risk lives, which is usually in the translations, the tracking requirements, or a third-party embed nobody mentioned until launch week. It is the kind of work that looks routine when it goes well, and only looks interesting when someone misses a launch. I didn't miss them.