
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.
One record drives the calendar, the redirects, and the modules.
Role: Front-end
Context: Simpler Trading. 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.
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.
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.
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.
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.