99 Francs
sales@99francs.agency

HQ Paphos, Cyprus · worldwide

Case study · Campaign landing page

Vines Estate: a campaign page the site was never built to hold.

A ten-home development in Swanson, Auckland ran a promotion with a deadline: buy one of the homes and get a one in ten chance to win the purchase price back. The landing page had to be live quickly, and it had to live inside the WordPress and Divi site they already had.

Vines Estate campaign landing page — Buy a home, Win it back, with the promotion countdown and availability bar
ClientVines Estate
IndustryReal estate
ServicesWeb design, Web development
FocusWordPress, Divi, Shadow DOM, Swanson NZ
Direct answer

A full custom landing page, shipped as one Divi module inside a live WordPress site — and sealed off from the theme that would otherwise have broken it.

Hero, availability grid, amenities, countdown and enquiry form in a single Code module. Shadow DOM keeps the theme out. The enquiry form is designed as part of the page but submits through the forms plugin the site already ran, so entries and notifications land exactly where the client’s team already looks.

Challenge

A deadline campaign on a site that could not be rebuilt.

The promotion had a fixed closing date and a prize worth up to $669,000. The page had to explain an unusual offer clearly enough to be trusted, show which of the ten homes were still available, and carry every enquiry — all inside a WordPress site built on a page builder, without touching the theme.

A rebuild was not on the table

The developer needed the campaign live quickly on the site they already had. Replatforming for one page would have cost more time than the promotion had, so the constraint was to fit inside WordPress and Divi as they were.

Theme CSS is the enemy of a campaign page

A page builder site accumulates global styles that will eventually reach into anything you add. Shadow DOM ends the argument: the campaign page cannot be restyled by the theme, and cannot break the rest of the site either.

The form had to look bespoke and behave native

A campaign form posting to its own endpoint means someone has to maintain it, and the sales team loses the entry list and notifications they already know. Designing the form freely while submitting through the existing plugin keeps both.

Vines Estate availability grid — ten homes with sold, under contract and available statuses and per-home enquiry buttons
Availability

Scarcity only works when it is true and visible.

Every home carries its real status — sold, under contract or available — and the bar in the hero counts them. Enquire on a home and the page scrolls to the form with that home already selected, so the sales team knows which one the enquiry is about without asking. It has been kept accurate since launch: nine of the ten are now gone.

The enquiry form

Designed from scratch, delivered by the plugin they already had.

The form is part of the page rather than an embed dropped into it — the campaign’s palette and typography, and a home selector the page fills in for you when you click Enquire on a specific home. Underneath, it submits through the WPForms setup the site already ran, so entries, notifications and the sales team’s workflow stay exactly where they were. No new plugin, no custom endpoint, and nothing extra to maintain once the promotion closes. Making that relay pass the plugin’s own bot checks took some working out — that part is in the FAQ.

Vines Estate enquiry form — name, email, phone and a which-home selector that the page pre-fills
Process

Building a modern page inside a page builder.

The constraint was the brief: whatever we built had to be droppable into the existing site, removable when the promotion ends, and impossible for the theme to break in the meantime.

01

Ship inside Divi, not around it

The site is a live WordPress build on Divi and could not be rebuilt for one campaign. So the page had to be something Divi could hold: one Code module dropped onto an existing page.

02

Isolate the page from the theme

The markup mounts inside a Shadow DOM host, so no theme or plugin stylesheet can reach it and nothing it does leaks back out. We proved it first against a deliberately hostile stylesheet.

03

Relay the form into WordPress

Rather than posting to our own endpoint, the custom form relays into a hidden WPForms form, so entries, notifications and nonces behave exactly as the client's team already expects.

04

Keep it current as homes sell

Statuses, the countdown and the availability bar are updated as the client reports sales — the page has been revised repeatedly since launch rather than left to go stale.

Outcome

One home left, and a form that actually delivers.

The page has been revised repeatedly since launch as homes sold — a campaign page is only useful while what it says is still true.

9 of 10

homes sold or under contract

As of 1 September 2026 one home is left from the ten in the draw. The page is the campaign's enquiry surface, not its only sales channel — but it carried the offer, the countdown and every enquiry.

1

module holds the whole page

Hero, homes grid, amenities, countdown and enquiry form all ship as a single Divi Code module dropped onto an existing page — nothing else on the site had to move.

0

new plugins, endpoints or theme edits

The page uses the forms plugin, media library and page builder the site already had. When the promotion ends the module can be deleted and nothing else on the site changes.

WordPress support

Need something built inside your WordPress site this week?

Tell us what you need. We estimate it in hours, start straight away, and you pay at the end — no deposit.

WordPress · Divi · Campaign landing pages · Auckland, New Zealand
Case study FAQ

Questions about the Vines Estate campaign page.

99 Francs designed and built the Buy a home, Win it back campaign landing page for Vines Estate, a ten-home development in Swanson, Auckland, New Zealand. It runs inside the client's existing WordPress and Divi site as a single Code module, with a countdown, a per-home availability grid and an enquiry form that pre-selects the home a visitor came from.

Because the submission was relayed into a hidden WPForms form, and two of its protections treat that as bot behaviour: modern anti-spam protection and minimum time to submit. When either trips, WPForms deliberately returns a success response and shows the confirmation while discarding the submission — a fake success designed to stop bots learning they were caught. Turning both off for that form fixed it. This is the same class of silent failure we found on another WordPress site, from a different plugin.

Yes. A full custom page can ship as a single Divi Code module on an existing page, with no theme edits, no child theme and no new plugins — the approach we use for WordPress support and web design work on sites we did not originally build.

By mounting the markup inside a Shadow DOM host. Styles inside the shadow root are sealed off from the page, so theme and plugin CSS cannot reach in and the campaign styles cannot leak out. Web fonts are the exception and are loaded at document level, where the font-face declaration still applies inside the shadow root.
Availability, statuses and the countdown are values in the module rather than hard-coded markup, and the page has been revised repeatedly as homes moved from available to under contract to sold. For a fixed-length promotion this was faster and safer than building a CMS layer that would be thrown away at the end.
Yes. Vines Estate is in Swanson, West Auckland, and 99 Francs has delivered property and real estate websites for the New Zealand market including 4 Madeira Place in Grafton, The Pacifica Penthouse in Auckland CBD and Trivelle Gardens in Hobsonville.