Multi-Country Campaign Websites — Case Study | brdz.net
Case study

Campaign websites for several countries — one production line

Performance marketing

Confidential 3–6 weeks per market, then reuse TypeScript Next.js FastAPI PostgreSQL

Challenge

A team needed many campaign pages, each feeling local to its country, live on its own domain, and able to tell which visit came from which ad. Doing that by hand meant copy-paste, broken tracking, and a new mess every time a market opened.

Solution

We set up a repeatable line: unique sites per market (not one template with a flag swap), a small private tracker for visits and clicks, and a “post office” that forwards conversion events to the right site even if a partner retries. Editors get a catalog pipeline so they are not copying hundreds of cards by hand. Each site keeps its own language and legal page.

Results

New markets stopped being a from-scratch project. A marketer sees clicks in one admin instead of ten spreadsheets. If a partner sends the same event twice, it is not counted twice. Time to stand up the next country dropped from weeks of glue-work to a known checklist.

Several countries, separate domains Shared click tracker Retry-safe conversion events