Registration Path
The path from a campaign visit to a signup, with the UTM intact through the redirect and the dataLayer events that record the view and the completion.
Case study
Role: Front-end and CRO
Context: Simpler Trading — membership and webinar registration
The decision
A visitor from a campaign has to reach the signup with the offer still clear, and the business has to know which campaign produced that signup.
What I owned
- The layout of the registration pages on that path.
- The JavaScript for the redirect and the UTM values, so source, medium, and campaign survive the hop to the next URL.
- The GTM dataLayer events for the page view, the start of the form, and the completed signup, with those campaign values still attached.
- The release, on the same weekly cadence as the rest of the frontend.
How someone else reuses it
A new webinar or membership offer uses the same path. Marketing changes the offer and the destination. The redirect, the parameter handoff, and the events stay put. The calendar invite, the timed handoff, and the modules on the page come from one campaign record, written up as the campaign launch kit.
In React and Next.js
The path is a few routes that share one campaign helper. The helper reads the UTM on arrival, writes it onto the next URL when the page redirects, and puts the same values on each dataLayer push. The form is a component. The events fire from the page view, the first field interaction, and the success state. A new offer is a new route and a new destination, on that same helper.