Preparing for a Website Relaunch: Preserving GA4 Historical Data and Event Integrity

A man in a brown blazer smiles while talking to another person across a table with laptops.
Table of Contents

A website redesign or CMS migration is an exciting milestone for any college or university. However, for digital analytics and enrollment teams, a relaunch is also high-risk. Without meticulous planning, web redesigns frequently wipe out custom event tracking, break cross-domain CRM connections, and destroy years of historical data continuity, leaving enrollment marketers blind right in the middle of a recruitment cycle.

To prevent data loss and ensure seamless reporting during a website relaunch, higher ed web teams must follow a rigorous pre- and post-launch analytics checklist.

Phase 1: Pre-Launch Audit & Inventory

The secret to a successful analytics migration is documenting what currently exists before a single line of code is moved to production. Analytics should also be part of the broader website migration strategy, alongside content audits, URL mapping, and redirects

1. Audit Existing Data Layer Parameters

Higher ed sites may use custom Data Layer objects to push rich context into Google Tag Manager such as student type (undergraduate vs. graduate), campus location, degree program, and degree level. This advanced event tracking can enhance your GA4 event reporting. If the new CMS theme launches without these underlying JavaScript data layers, your custom GTM triggers will immediately fail.

  • Document every dataLayer.push() event currently active on the live site.
  • Share exact Data Layer specifications and variable naming conventions with your new web development agency or internal IT team well ahead of development.

2. Map Custom Dimensions and Event Definitions

In GA4, custom event parameters must be mapped to Custom Dimensions and Custom Metrics within the GA4 user interface to be accessible in reports. Review your GA4 property and event settings and create a master spreadsheet containing:

  • Event Names (e.g., RFI_form_submit, brochure_download, campus_tour_click)
  • Associated Parameters (e.g., program_name, degree_level, campus_location)

3. Review Cross-Domain & CRM Integrations

If your institution is migrating domain structures or launching a new application portal (e.g., moving from a third-party host back to a university subdomain), verify that your GA4 Cross-Domain measurement rules are configured properly. Ensure that linker parameters are preserved so prospective students moving from the main site to an application form do not lose their original campaign attribution.

4. Verify GA4 Enhanced Measurement & Site Search Settings

Modern CMS builds often alter URL structures for search result pages, which can break site search tracking in GA4 if not configured correctly during a redesign.

  • view_search_results Query Parameters: Check whether your new CMS uses non-standard URL query parameters for internal site searches (e.g., changing from ?s=nursing to ?search_term=nursing or ?query=nursing). If the parameter changes, update the Search Term Query Parameter field under GA4 Enhanced Measurement settings so internal search terms continue tracking without interruption.


Review your Enhanced Measurement settings to ensure tracking stays accurate once the new site is live.

  • Deactivate Overlapping Enhanced Measurement Events: If you deploy custom GTM tags to track form completions, video interactions, or scroll depth, audit your GA4 Data Stream > Enhanced Measurement toggles. Disable duplicate native tracking in GA4 to avoid double-counting user interactions.

5. Audit GTM Triggers and Variable Configurations

A website redesign frequently changes multiple web page URLs and page structure. Review your GTM tags, triggers, and variables before launch:

  • GTM Variable Settings: Redesigns can break DOM Element, Click Element, or CSS class-based variable settings. Update trigger conditions for CSS classes (e.g., .btn-submit-v2), static Data Layer variables or custom data HTML attributes assigned by developers.
  • Centralize Measurement IDs via GTM Constants: Replace hardcoded GA4 Measurement IDs (`G-XXXXXXXXXX`) in individual event tags with a GTM Constant Variable. This allows your team to easily swap tracking destination IDs when moving from staging to production.
  • Clean Up Legacy Tags, Triggers, and Scripts: Use the redesign as an opportunity to audit and purge legacy Universal Analytics tags, obsolete ad pixels, and outdated Custom HTML scripts that can slow down page loads and degrade Core Web Vitals.

6. Configure Privacy, Consent Mode, and Traffic Filters

Data privacy regulations and ad network requirements make pre-launch privacy and filtering configuration essential:

  • Consent Mode v2 Integration: If the redesign launches a new Cookie Consent Banner or Management Platform (e.g., OneTrust, Cookiebot), ensure Google Consent Mode v2 signals are integrated into GTM so modeling and ad attribution fire appropriately based on user consent.
  • Internal Traffic & Unwanted Referral Filters: Define internal developer and staging IP addresses under Configure Tag Settings > Define Internal Traffic. Additionally, add third-party payment gateways, event ticketing platforms, or portal login screens to the List Unwanted Referrals setting so they don’t overwrite original user acquisition sources.

Phase 2: Staging Environment Validation

Never wait for the production go-live date to test your analytics setup. All event tracking must be thoroughly tested in a staging or preview environment.

The Staging Audit Checklist

  1. Deploy GTM Container to Staging: Verify that the production Google Tag Manager container (or an identical staging container) is present on all staging page templates.
  2. Test Triggers in GTM Preview Mode: Click through key prospective student journeys (submitting an inquiry form, booking a campus visit, downloading a viewbook) in GTM Debug/Preview mode to confirm triggers fire cleanly.
  3. Validate GA4 DebugView: Use the GA4 DebugView tool to verify that real-time events, custom parameters, and Key Events (formerly Conversions) are registering with accurate parameters.
  4. Verify Form Listeners: New CMS form builds can use AJAX or embedded iFrames that bypass standard form submission triggers. Test whether GTM can native-listen to form completions or if custom DOM element/event listeners are required.

Phase 3: Post-Launch Audit & QA

Once DNS records update and the new site goes live, immediate QA is required to ensure data flow remains unbroken.

Post-Relaunch Verification Checklist

  • Real-Time Data Flow: Check the GA4 Realtime Report to ensure active users and pageview events are registering immediately upon launch.
  • Key Event Tracking: Submit test inquiries on the live site to confirm form submissions fire correct custom events and populate parameter values in GA4.
  • Custom Dimension Health: Review the GA4 Custom Definitions panel to confirm there are no missing parameters or unmapped custom dimension warnings.
  • Site Search Query Parameters: Perform an internal search on the new CMS to confirm the view_search_results event fires with the correct search_term parameter.
  • Dynamic Pageview Tracking: Test interactive program finders or SPAs to verify History Change triggers record pageviews cleanly without double-counting.
  • Consent Mode & Filtering: Inspect network requests and referral sources to ensure consent signals fire properly.

By treating GA4 tracking as a core architectural requirement rather than a post-launch afterthought, higher ed digital strategy teams can safeguard historical trends, maintain reporting integrity, and continuously track enrollment impact throughout a website redesign. 

Once tracking has been validated, institutions should establish clear ownership of ongoing analytics monitoring and reporting as part of their broader website governance strategy.

Need help protecting your analytics through a website relaunch? Carnegie’s Google Analytics team can help your institution plan, validate, and optimize GA4 tracking to maintain reporting continuity and measure enrollment performance.

Start a conversation to learn more.

Protecting Your Analytics Before and After a Website Relaunch

Does redesigning a website erase historical GA4 data?

No. A website redesign or CMS migration does not automatically erase historical data stored in an existing GA4 property. However, switching to a new property or changing tracking configurations can disrupt reporting continuity. Institutions should confirm their GA4 property and data stream strategy before launch and document important baseline metrics to support accurate comparisons.

What GA4 tracking should colleges and universities test before a website relaunch?

Higher education institutions should validate key enrollment events, custom dimensions, Google Tag Manager triggers, cross-domain measurement, internal site search tracking, and consent configurations. Testing should include critical student journeys, such as submitting an inquiry form, registering for a campus visit, or navigating to an application portal.

How can higher education institutions verify GA4 tracking after a website launch?

Teams should use GA4 Realtime and DebugView alongside Google Tag Manager Preview mode to confirm that events and parameters are being collected correctly. They should also verify that inquiry submissions, application-related actions, internal searches, and cross-domain interactions continue to register accurately. Once reports have processed, institutions should compare post-launch results against documented pre-launch baselines.


Let’s Talk about What Comes Next.