Role: Front-end and CRO

Context: A sample page, built to show a second landing-page pattern beside the sales page. It opens on its own, the way the other previews in /iframes/ do.

The decision

The page asks for an email before the rest of the pitch. After that address, it asks for an SMS 30 minutes before the session. The session time sits in the form card, and the same form returns at the bottom.

What I owned

• The layout: a split hero, the promise, what the session covers, the agenda, who it is for, questions, and the form again.
• The registration path on that form. Source, medium, and campaign stay on the confirmation. The dataLayer records the view, the first focus, the signup, and the reminder choice. The phone number is not on that record.
• The campaign record in campaign.js. The headline, the time, the button, the agenda, and the calendar links are fields on that object.

How someone else reuses it

Copy the registration folder. Edit campaign.js. Leave the layout. A new session is a new record, on the same page. The signup inside the site, on the registration path and the campaign launch kit, reads a record the same way.

In React and Next.js

The page above is the standalone template. SignupLanding is the same kind of record rendered inside the site. Both keep the address in the browser. track() writes signup_view, signup_start, signup_complete, then reminder_view and either reminder_optin or reminder_skip. The visit stays attached. The phone number does not.