Website Analytics and Ads Setup

You can have a clean migration plan, solid design, and fully tested templates, then still lose money on launch day. The reason is simple. If website analytics and ads setup are not checked before launch, you can lose tracking, miss ad impressions, and create reporting gaps that are hard to fix later.

This is one of the last steps in a safe website migration process, and it deserves real attention. For publishers, it matters even more because traffic, ad revenue, and editorial decisions all depend on clean data.

Part 5: Setting Up Analytics and Gathering Data

At this stage, your content is moved, the design is approved, and core features have been tested. Before you switch the new site live, make sure your analytics and ad tools are installed correctly. If this step is missed, you can end up with broken reports, lower revenue, and a messy launch week.

Integrate Analytics

If you do not know how people use your site, every UX or content decision becomes a guess. Publishers need data to track traffic, content performance, and revenue trends. For most teams, that means setting up GA4 and checking that pageviews, events, and referral data are all recording properly.

GA4 for WordPress Websites

WordPress gives you a few ways to add GA4 tracking. The right option depends on how much control you need and how comfortable you are working in the admin.

Use the Theme Editor

If you are comfortable editing code, you can add the tracking snippet directly to your theme header.

1. Log in to your WordPress admin dashboard.
2. Go to Appearance > Theme Editor.
3. Select the header.php file.
4. Find the closing </head> tag.
5. Paste your GA4 tracking code right before that tag.
6. Save the file.

Be careful: direct theme edits can be lost during updates. If you take this route, use a child theme and create a full backup first.

Use a Plugin

For most teams, plugins are the safer choice. They reduce the chance of code being removed during a theme update and are easier for editors or marketers to manage later. If your team needs deeper help with setup or cleanup, it may be worth getting WordPress development support.

Common plugin options include:

• Site Kit by Google: connects Analytics and other Google tools inside WordPress.
• MonsterInsights: adds analytics tracking and dashboard reporting.
• Insert Headers and Footers: lets you place tracking code without editing theme files.

No matter which option you choose, test the install after setup. Open the site, visit a few pages, and confirm the traffic appears in your analytics property.

GA4 for Non-WordPress Websites

If your site is not on WordPress, you can still add GA4 in a few simple ways.

Custom HTML Websites

1. Open your website files in a code editor.
2. Find the closing </head> tag in the main template or page files.
3. Paste the GA4 snippet above that tag.
4. Upload the updated files to your server.
5. Clear cache and confirm the code is firing.

Shopify

1. Log in to your Shopify admin.
2. Go to Online Store > Themes.
3. Select your live theme and choose Actions > Edit Code.
4. Open the theme.liquid file.
5. Paste the GA4 code above the closing </head> tag.
6. Save and test the storefront.

GA4 Using Google Tag Manager

If you already use Google Tag Manager, it is often the cleanest way to manage tracking and ad scripts in one place.

1. Create a Tag Manager container for the site.
2. Install the container on the website.
3. Add a new GA4 configuration tag.
4. Enter your Measurement ID.
5. Set the trigger to All Pages.
6. Publish the container and test the install.

Verify Your Ads Are Running Correctly

For many publishers, ads are the main revenue source. A small mistake in setup can mean a major drop in earnings. This is why ad QA should be part of every launch checklist, especially for teams doing web development for publishers.

Update Ad Tags

Make sure every ad tag on the new site is current and placed in the right location.

1. Retrieve ad codes: pull the latest tags from Google Ad Manager or your ad network.
2. Place them correctly: install tags in the header, sidebar, or in-content areas where they belong.
3. Manage them centrally: if possible, use Tag Manager so future updates are easier.

Test Ad Serving

After implementation, confirm that ads load and behave as expected.

• Use preview tools: publisher console tools can help identify delivery issues.
• Check multiple devices: test desktop, tablet, and mobile layouts.
• Review formats: confirm banner, native, and video placements all work.

Other Ad Solutions

Google tools are common, but they are not the whole picture. Many publishers also rely on Outbrain, Taboola, affiliate placements, sponsorship units, or direct sold campaigns.

• List every ad network and partner before launch.
• Check that each third-party script still loads on the new site.
• Tell partners about the migration so they can help catch issues early.

Keep Ad Inventory Consistent

Try to keep ad inventory the same right before and right after launch. That makes it easier to tell whether a revenue shift came from the migration itself or from a change in ad setup. In most cases, we suggest waiting about 60 days before making major ad layout changes, unless there is a strong business reason to move sooner.

Audit Your Ad Placements

1. Compare old and new pages: use screenshots or documentation to match placements.
2. Check for missing units: make sure nothing was dropped or duplicated.
3. Review ad density: avoid layouts that create policy risk or hurt the reading experience.

When You Do Plan Changes

• Measure the impact: understand the likely effect on both revenue and UX.
• Test in stages: roll out changes carefully instead of changing everything at once.
• Check compliance: confirm the new setup follows ad network rules and privacy requirements.

Bonus: Minimize Downtime During Migration

Downtime hurts user trust, ad delivery, and data continuity. The goal is not always zero downtime, but it should be short and controlled.

Choose the Right Launch Window

Plan the switch during a lower traffic period.

• Review time zones: if your audience is spread out, find the true low point in traffic.
• Compare weekdays and weekends: the right window depends on your audience habits.

Coordinate the Team

A launch runs better when everyone knows their role.

• Create a clear timeline: assign each step and owner.
• Share the plan: keep editors, marketers, developers, and partners informed.
• Prepare a rollback plan: know what happens if something breaks.
• Monitor the site: review performance before, during, and after launch.
• Notify your host: let them know the migration is happening and ask what support is available.

Need Expert Advice?

Migrating a publisher site takes more than moving templates and content. You also need clean tracking, stable ad delivery, and a launch process that protects revenue. Refact has helped content-heavy teams plan safer launches with less guesswork and stronger handoff between strategy, design, and engineering.

If you want help validating your analytics, ad setup, or launch checklist, talk with Refact.