The short version
A Campaign Microsite is a site with something to do inside it: a quiz that recommends, a calculator, a configurator, a promo game. The mechanic is why people stay, answer, share and leave their details. The rest of the site exists to make that one thing work.
Built in 1 to 2 weeks from brief and materials. Fixed fee, quoted within 24 hours. Data capture with consent, CRM and email wired in, analytics, schema, copy in English and Spanish, two rounds of revisions. You own the code, the accounts and the data.
If the campaign only needs a message and a form, that is the Launch Page, 72 hours. The microsite is for when the campaign needs an action from the visitor, not just their attention.
Four mechanics, and what each one is for
The quiz that recommends
What it is. A short set of questions, a result, a recommendation. The person answers about themselves and gets back something that is about them: a product, a plan, a score, a next step. The one on our home page has five questions and takes a minute.
Which goal it serves. Qualification first: whoever finishes has told you their situation, priority and budget bracket. Lead capture second, if the result is worth an email. Awareness when the result is something people want to share.
Data and consent. The answers: preferences given on purpose. Answers alone are not personal data until you attach them to a person, so a quiz can run with no form at all. Ask for an email to send the result, and the form says in plain words what you will send, links the privacy policy and uses a separate, unticked box for marketing. That is the consent part of GDPR for a quiz, done properly.
Build time. The one-week end of the package, if the products or plans it recommends already exist in a list with clear rules.
Example. A skincare brand's routine quiz: skin type, main concern, steps you will realistically do, budget. Result: a three-product routine with the reason for each, an option to email it, and a CRM tag by skin type so the follow-up speaks to dry skin and oily skin differently.
The calculator
What it is. Inputs in, a number out: savings, cost, payback, time, emissions. The visitor does the maths on their own numbers and trusts the result more than any claim on the page.
Which goal it serves. Lead capture, because the full breakdown is a natural thing to send by email. Qualification, because the inputs (company size, current spend, volume) size the opportunity before anyone calls.
Data and consent. The inputs, the result, and the contact if the person wants the breakdown. Same rule as the quiz. If an input is about a person rather than a company (age, income, health), we say why we ask, keep it out of the CRM unless the follow-up needs it, and set a retention period.
Build time. If the formula already lives in a spreadsheet, the one-week end. If we build the model with you, plan for the two weeks.
Example. A solar installer's savings calculator: province, roof orientation, monthly bill. Result: yearly saving and payback, a PDF by email with the assumptions shown, and the bill size as a CRM field so sales calls the biggest roofs first.
The configurator
What it is. Build your own: options, colours, modules, a live preview and a price or a summary at the end. It turns browsing into deciding.
Which goal it serves. Qualification, since a finished configuration is a precise expression of intent. Retention, because a saved configuration is a reason to come back and finish. Lead capture at the end, with "save my configuration" as the ask.
Data and consent. The configuration, anonymous until saved. Saving needs a contact, and from then on it is personal data: we state how long it is kept and let the person delete it. If it goes to a dealer or a sales rep, the form says so before the button, not after.
Build time. The two-week end. The product data must exist as a clean list: options, the rules for which go together, images, prices. Cleaning that list is where the time goes.
Example. A furniture brand's sofa configurator: shape, fabric, legs, cushions, price updating live. The saved configuration goes to the person and to the nearest showroom, with a link that reopens it as it was left.
The promo game
What it is. A scratch card, a wheel, a memory game, a daily prediction, a quiz with a prize. Quick, with a reason to come back tomorrow.
Which goal it serves. Awareness, because a game with a prize gets shared and repeated. Retention, when entries are daily or weekly. It grows an email list fast; whether the list is any good depends on how close the prize is to what you sell.
Data and consent. Name and email to enter, sometimes a proof of purchase, sometimes a date of birth if the category is age-restricted. Two separate consents: one to take part (the promotion's terms, published on the site and linked from the form) and one, unticked, for marketing afterwards. Winning a prize is not permission to email someone for a year.
Build time. The full two weeks. Prize logic, entry limits, basic fraud checks and the terms take time to get right.
Example. A sports retailer's daily prediction game during a tournament: one entry a day, a leaderboard, a weekly prize and a discount code for anyone who played three days running. The list it builds is people who care about the sport the retailer sells.
Which mechanic for which goal
| Campaign goal | First choice | Also works | What lands in the CRM |
|---|---|---|---|
| Awareness | Promo game | Quiz with a shareable result | Contacts with marketing consent and a source tag |
| Lead capture | Calculator | Quiz, promo game | Contact plus the inputs that size the deal |
| Qualification | Quiz that recommends | Calculator, configurator | Contact plus answers, tagged by segment |
| Retention | Configurator | Game with daily or weekly entries | Contact plus a saved state |
Two mechanics can share one microsite (a quiz that ends in a calculator is common). It costs more and needs the two weeks; we quote both so you see the difference.
What is included
- The mechanic, designed and built: logic, results, edge cases, mobile first.
- The site around it: story, form, thank-you page and legal pages, in English and Spanish, written natively in each.
- Data capture with consent done properly: plain-word forms, unticked marketing boxes, retention periods.
- CRM and email wired in: leads arrive where your team works, tagged by result, and the follow-up email goes out on its own.
- Analytics with events on every step.
- Schema and entity data so ChatGPT, Gemini, Perplexity and Google AI understand the site. Organic search's share of traffic to Spanish sites fell from 52% to 41% in a year (SE Ranking); a campaign site assistants cannot read is one fewer people find.
- Two rounds of revisions, then launch on your domain or subdomain with the repository, the accounts and a one-page manual.
Microsite, landing page, or a page on the main site
| Campaign Microsite | Launch Page | Page on the main site | |
|---|---|---|---|
| Best for | A campaign that needs an action | A moment that needs a message and one form | Something permanent |
| Time | 1 to 2 weeks | 72 hours | Your site team's calendar |
| Own domain or subdomain | Usually | Yes, or a path on your domain | No |
| Data capture | Built around it, CRM and email included | A form, routed to your CRM | Whatever the site supports |
| After the campaign | Redirect, keep the data | Redirect or archive | Content and maintenance stay |
| SEO and AI visibility | Built for the campaign's questions, links to the brand | Built for the moment, cited if the release gets coverage | Inherits the main domain's authority |
The rule: if the mechanic will still be useful in a year, it belongs on the main site, and we build it to embed there. If it belongs to a campaign with a start and an end, a microsite is faster to launch and cleaner to measure.
A live example, on this site
The AI visibility quick check on the home page is the quiz mechanic as we build it into campaign sites: five questions, a score, a recommendation, a next step. No email gate; the result is only for you. It is also a real quick check: sixty seconds of honest answers, a score out of ten and the first thing to fix. What the assistants actually say about your brand is what the AI Visibility Audit measures, in five days.
Who it is for
Brands with a campaign that needs more than a message: a launch with a product finder, a promotion with a game, a service with a calculator that turns "how much would it cost me" into a lead. Regular ChatGPT use in Spain went from 4% to 28% between 2023 and 2025 (Funcas), so the site is built to be found by assistants too, not only by people who click the ad.
Event and PR agencies whose clients have moments with dates: check-in with a QR ticket and session selection for events, a launch quiz for a product push, a prediction game for a sponsorship. Referral, co-branded or white-label, with a free AI Visibility Audit for one client to start. Details on the partners page.
Where to go next
- A message and a form, no mechanic: the Launch Page, 72 hours.
- An assistant that answers open questions: the Brand AI Tool, 2 to 4 weeks.
- Where your brand stands in AI answers first: the AI Visibility Audit, 5 days.
- All packages on the home page. This page in Spanish: Microsite de campaña.
Tell me the campaign goal and what you already have. You will have a fixed fee and a written scope within 24 hours.