01
Connecting an education platform, lead journeys and server-side measurement
An ongoing technical collaboration connecting a complex WordPress education platform with admissions journeys, attribution data, consent management and first-party server-side measurement.
- Industry
- Higher education and creative arts
- Role
- Web developer and measurement implementation partner
- Scope
- WordPress development, lead attribution, consent and server-side analytics
- Status
- Ongoing technical collaboration
- Client
- TAIARTS
01 / Context & challenge
Understanding the operational problem
TAIARTS manages a broad catalogue of creative-arts programmes on a complex WordPress platform. Programme pages need to support detailed academic content, reusable sections and interactive navigation while remaining manageable for the internal team.
The admissions journey crosses the main website, a dedicated form subdomain and Salesforce. Campaign context, consent choices and analytics identifiers need to remain coherent as prospective students move between those systems.
Measurement also had to become more reliable and privacy-aware. The implementation needed to align Didomi, Google Tag Manager and Consent Mode before introducing a first-party server-side collection flow.
02 / My role
Where I was responsible
- Development and maintenance of dynamic WordPress and ACF programme templates.
- Interactive programme navigation, reusable content sections and responsive admissions components.
- Cross-domain preservation of campaign attribution across the main website and forms.
- Review and correction of Didomi, Google Tag Manager and Consent Mode behaviour.
- Implementation and validation of a first-party server-side GA4 flow.
- Debugging, documentation and coordination across web, forms and measurement infrastructure.
03 / Solution
Building a maintainable system
02
Cross-domain lead attribution
03
Consent and analytics governance
04
Server-side measurement infrastructure
04 / System view
How the main parts connect
A simplified view of the platform and its main operational areas.
05 / Outcome
What changed
- A maintainable programme-page system supports complex educational content.
- Attribution context can continue across the main website and admissions forms.
- Duplicate page-view behaviour was identified and corrected.
- GA4 events were successfully routed and validated through the server-side measurement flow.
- The implementation provides a foundation for future advertising and CRM measurement without coupling those later phases to the current platform.
Technology
- WordPress
- ACF
- JavaScript
- Google Tag Manager
- Server-side GTM
- Google Analytics 4
- Didomi
- Stape
Facing a similar challenge?