Campaign Launch Kit

Shipped
Web System

One campaign record drives the calendar invite, the timed redirects, and the modules on the page. A new live event is a new record. Shown here with a sample record.

Problem
The confirmation, the live URL, and the next webinar could disagree.
Role
Frontend
Built
One campaign record for the invite, the redirects, and the modules
Tracking
The record drives the page. Live offer URLs stay off this page.
Result
Shipped behavior. This page uses a sample record.

One record drives the calendar, the redirects, and the modules.

Role

Frontend

Employer

Simpler Trading

Stack

React

Focus

Campaign launch kit

Status

Production behavior, sample record
Case study

After someone registers, the confirmation, the live URL, and the next webinar have to stay in agreement. This is that production behavior, rebuilt here with a sample record. Live offer URLs and internal campaign codes stay off this page.

The decision

One campaign record is the source of truth. The calendar invite, the moment the URL becomes the replay, and the moment the next webinar takes that URL all come from that record. A date that is not in the spec does not go on the page. A member who already owns a product can have that tier hidden.

What I owned
  • The campaign spec as the source of truth. A date, a slug, or a URL that is not in the spec does not go on the page.
  • The redirect. Before the event, the URL is the registration page. After the replay time, that same URL sends people to the replay. At the handoff time, it sends them to the next webinar. A query flag holds the page for QA, and a tab left open rechecks the clock.
  • The confirmation calendar. One config builds the Google Calendar link and the .ics file from the title, the time, and the bullets.
  • The modules. The pricing matrix renders the desktop table and the phone cards from one object. The carousels fill from that campaign copy. A member who already owns a product can have that tier hidden.
  • The intake and the preflight. Marketing fills the record. The pages ship after that checklist.
Design system pieces

The live module uses the system this site ships from. The actions are the shared button. Type, accent, and the card surface come from the tokens. The preview uses a sample record. Live offer URLs and internal campaign codes stay off this page.

How someone else reuses it

Marketing fills the intake. The build copies the spec into one config block at the top of each script. The next webinar starts as a new spec. The visit itself is the registration path: the UTM survives the redirect, and the dataLayer records the view and the signup for that same campaign.

Shipped

CampaignKit holds that list. Open the kit opens the first card. Choosing an action marks it on the card and does not leave the page. Skip, Close, and Ship the page end the set. The first card has nowhere to go but forward.

Looking for this kind of work on your team?

I build websites, landing pages, and production interfaces that convert. I can own the frontend. Let's talk.
Contact© 2026 David N Allen. All rights reserved.
Developed with React Developed with Next.js