Ad Domain Migration Checklist: Keep Your PPC Campaigns Running Smoothly

Originally posted on April 12, 2024 @ 3:21 am

Somewhere right now, a paid search manager just got a Slack message: “We’re changing the domain. Should be straightforward.” Nothing about a domain migration with active ad spend is straightforward.

Your campaigns are built on accumulated machine-learning signal — every conversion that’s trained your smart bidding strategies, every Quality Score association tied to a specific landing page URL, every audience signal Google’s algorithms have learned to act on. All of it is anchored to your current domain. Change the domain without a disciplined protocol, and months of algorithmic optimization can reset in a single afternoon.

This ad domain migration checklist is for paid search specialists and marketing directors managing active ad spend through a domain change. It’s not an SEO migration guide — organic concerns appear only where they directly intersect paid performance. The focus is singular: protect your conversion data, maintain smart bidding continuity, and keep every dollar of ad spend tracking, attributing, and optimizing on the new domain exactly as it did on the old one.

Key Takeaways

• The real asset at risk is signal, not URLs. Smart bidding models, conversion history, and Quality Score associations are anchored to your current domain — protect continuity of that data above all else.
• A domain change alone doesn’t trigger a smart bidding learning period. The danger is a conversion data gap — even 24–48 hours of broken tracking can force recalibration requiring ~50 conversions or three conversion cycles.
• Your ad URL map is not your SEO redirect map. PPC landing pages include custom parameters, A/B variants, and tracking template overrides that standard sitemap crawls miss entirely.
• Query string preservation is the silent failure point. Redirects that strip GCLID and UTM parameters break attribution with zero visible errors — CDN platforms like Cloudflare strip query strings by default.
• Three phases, executed in sequence: Pre-Migration (audit and protect), Migration Execution (redirect, re-tag, relaunch), Post-Migration (monitor, validate, optimize). Skip a phase and recovery becomes exponentially harder.
• Plan for 2–4 weeks of intensive post-migration monitoring. Silent tracking failures can bleed budget for days before surfacing in standard reports.

Pre-Migration: Protect Your Data Before You Touch Anything

Everything in this phase happens before the migration window opens. This is your insurance policy — skip it, and there’s no safety net when something breaks at 2 AM on launch night.

Audit Every Active Campaign and Document Your Baseline

Before anything moves, capture a complete performance snapshot. This becomes the benchmark everything is measured against post-migration.

Export campaign data from Google Ads via the Reports tab. Pull performance at the ad group level minimum — CTR, CPC, CPA, ROAS, conversion volume, impression share, and Quality Score. Segment by conversion action so you can trace exactly which conversion streams feed which campaigns. Save as a dated CSV. Do the same for Microsoft Ads and Meta Ads if you’re running cross-platform.

Now identify your highest-risk campaigns: the ones with the largest budgets, the deepest conversion history feeding smart bidding, and any running Target ROAS or Target CPA strategies. Smart bidding calibrates using roughly 50 conversion events or three complete conversion cycles — campaigns with deep history have the most to lose if that signal gets disrupted, and they take the longest to recover.

Flag every Dynamic Search Ad campaign separately. DSAs pull landing pages dynamically from your site’s index, making them uniquely vulnerable to domain changes. Google needs to re-crawl and re-index the new domain before DSAs function correctly, and a new DSA domain can take 24–48 hours to start serving.

Map Every Ad URL to Its New Destination

The most tedious step — and arguably the most consequential. Your ad URL redirect strategy is not the same as your SEO URL map. PPC landing pages frequently include custom parameters, A/B test variants, tracking template overrides, or UTM-tagged versions that never appear in a standard sitemap crawl. If your redirect map only accounts for pages the SEO team identified, you’ve already missed URLs that are actively serving ads.

Pull every active final URL from Google Ads. Build a custom report with Campaign, Ad Group, Ad, and Final URL columns and export the full set. Cross-reference against the redirect map your development team has built. Every old ad URL needs a corresponding new URL with a verified 1:1 301 redirect.

Three rules, non-negotiable:

• No redirect chains. Every old URL must 301 directly to its new destination. A chain (old → intermediate → new) adds latency, risks dropping query string parameters, and can trigger Google Ads destination requirements policy flags. Google’s own documentation on URL changes reinforces that clean 1:1 redirects are essential. One hop, every time.
• Every redirect must preserve query string parameters. This is where most migrations silently fail. A 301 redirect that strips the query string kills GCLID passthrough and destroys UTM attribution. Server configurations, CDN caching layers, and even some WordPress redirect plugins can strip parameters during the redirect without any visible error. Test explicitly — never assume.
• Account for every URL variant. Trailing slash vs. no trailing slash. HTTP vs. HTTPS. With and without www. Google Ads flags a destination URL mismatch if the final resolved URL doesn’t match what’s in the ad’s Final URL field — even a trailing slash discrepancy can trigger a policy disapproval.

Back Up Conversion Tracking and Tag Configurations

This is the parachute. If anything breaks during migration, these backups are the only path to restoring tracking without rebuilding from scratch.

Document every conversion tracking configuration across platforms. For Google Ads: every conversion action’s name, category, conversion window, attribution model, counting method (one vs. every), and value settings. For Google Tag Manager: export the full container JSON — this single file holds every tag, trigger, and variable in your setup, and it’s often the fastest recovery path if GTM breaks during migration.

Extend this to every platform on the old domain: Meta Pixel configurations (including custom event definitions), Microsoft UET tag setups, and any third-party integrations in your stack — call tracking, form attribution, CRM-side conversion imports.

Document your UTM parameter conventions: every naming convention in use, where they’re applied, and whether they’re enforced at the tracking template level or hardcoded in individual ad URLs. Separately, capture the current GCLID auto-tagging status in Google Ads (Settings → Account Settings → Auto-tagging) and note any manual tagging overrides. If you’re running parallel tracking, document that configuration as well — it affects how clicks resolve during the redirect.

Build Your Migration Timeline and Assign Ownership

PPC should not be an afterthought bolted onto a dev-led migration timeline. Paid media has its own dependencies — tags need to fire, redirects need to preserve parameters, conversion actions need to verify — and these don’t naturally align with a developer’s checklist of DNS switches and server configurations.

Build a timeline that coordinates PPC, SEO, development, and analytics. Key timing considerations:

• Avoid migrating during peak conversion periods. If your highest-ROAS days are Tuesday through Thursday, don’t kick off the migration on a Tuesday morning. A temporary tracking gap during a low-traffic window costs a fraction of what it costs during your best days.
• Allocate 2–4 weeks minimum for pre-migration preparation. The migration itself may take hours. The preparation takes weeks. Rushing the URL mapping or skipping the tracking backup is how these go wrong.
• Plan for at least 2 weeks of intensive post-migration monitoring. Silent tracking failures can bleed budget for days before surfacing in reports.

Every checklist item needs a named owner — not a team, a person. When something breaks at midnight, “the dev team” doesn’t answer their phone.

Owner	Responsibility
PPC Lead	Campaign audit, URL mapping, ad URL updates, bid strategy management
Analytics Lead	Conversion tracking backup, GTM container migration, GA4 configuration
Dev / IT Lead	301 redirect implementation, DNS management, server configuration
SEO Lead	Redirect map coordination, cross-functional URL validation
Project Manager	Timeline enforcement, stakeholder communication, escalation protocol

Pre-Migration Checklist Summary

Task	Owner	Status	Due Date
Export full campaign performance baseline (all platforms)
Identify highest-risk campaigns (smart bidding, highest budget)
Flag all DSA campaigns for separate handling
Build complete ad URL mapping document
Verify 1:1 301 redirects for every ad URL
Test query parameter passthrough on all redirects
Export/document all conversion tracking configurations
Export GTM container JSON
Document UTM conventions and GCLID auto-tagging status
Document Meta Pixel, Microsoft UET, and third-party tag configs
Build migration timeline with PPC-specific dependencies
Assign named owners to every task
Confirm migration window avoids peak conversion periods

Migration Execution: Redirect, Re-Tag, and Relaunch Without Breaking Signal

The operational window is open. Sequence matters here — redirects go live first, then tags are verified, then ad URLs are updated. Doing these simultaneously or out of order is how tracking breaks without anyone noticing.

Implement 301 Redirects and Verify Ad Landing Pages

With the redirect map finalized, coordinate with your development team to deploy 301 redirects before the DNS switch — redirects should be ready and testable the moment the new domain resolves.

Testing protocol for every ad landing page URL:

1. Run curl -I “https://olddomain.com/landing-page/?gclid=test123&utm_source=google&utm_medium=cpc” to check the redirect response. Confirm the HTTP status is 301 — not 302, not a chain.
2. Check the Location header. It should point to the exact new URL with all query parameters intact: gclid=test123, utm_source=google, utm_medium=cpc must all appear in the destination.
3. Follow the redirect manually. There should be exactly one hop. Old → intermediate → new is a chain. Fix it before proceeding.
4. After DNS propagation, re-test using the new domain. Confirm the final resolved URL matches what you’ve entered (or will enter) in the Google Ads Final URL field. Check trailing slashes, HTTPS enforcement, www/non-www canonicalization.
5. Load the page in a browser. Verify it renders correctly, meets speed thresholds, and has a valid SSL certificate. A misconfigured SSL cert triggers Google Ads disapprovals immediately.

Don’t overlook your CDN and caching layer. Cloudflare, Fastly, and similar edge platforms can strip query parameters from redirected URLs — particularly GCLID and UTM values. Cloudflare’s redirect rules, for example, default to preserve_query_string: false, meaning query strings are stripped unless explicitly preserved.

This is one of the most common silent failures in PPC migrations: the redirect works, the page loads, but tracking parameters were stripped at the edge and conversion attribution is broken with zero visible errors. Test parameter passthrough through your CDN specifically, not just at the origin server.

Update Every Ad URL, Extension, and Feed Across All Platforms

This step happens after redirects are live and verified. The redirects are your safety net; once confirmed, update the ad platforms to point directly to new URLs.

Google Ads: Update final URLs at the ad level, sitelink assets, call assets with tracking templates, image assets, and any DSA page feeds. Changing a final URL on an existing ad creates a new version — the ad enters re-review, and ad-level performance history (impressions, clicks, CTR) resets. Campaign and ad group data remain intact. Previous version data remains accessible via version history.

Two approaches: update existing ads in place, or create new ads with new URLs and pause the old ones. Updating in place is simpler but loses ad-level history and triggers re-review. Creating new ads preserves old ad history for reference but requires more manual work. For most migrations, updating in place is the pragmatic choice — ad-level history loss is minor compared to the risk of running duplicate ads during a transition. Use Google Ads Editor for bulk updates; doing this in the web UI one ad at a time invites human error.

Check tracking templates at the account and campaign level. These are set once and forgotten, but a tracking template with a hardcoded old domain will override your new final URLs and silently break tracking.

Microsoft Ads: Same process. If you import campaigns from Google Ads, be cautious — an import pulls current campaign data including URLs, so importing before updating Google means Microsoft Ads receives the old URLs. Run the URL update natively in Microsoft Ads to avoid sync timing issues.

Meta Ads: Update destination URLs in all active ad sets, but verify that the Meta Pixel is firing on the new domain first. Switching ad destinations before the pixel is confirmed creates a window where ads drive traffic to an untracked domain — and Meta’s optimization algorithms lose their conversion signal entirely.

Verify Conversion Tracking on the New Domain

This is where a conversion tracking domain migration is won or lost. “The tag is installed” is not the same as “conversions are tracking.” Test the full funnel — click → land → convert → data appears in platform — before considering tracking verified.

Google Ads: Open Google Tag Assistant and navigate to a landing page on the new domain with a test GCLID parameter appended. Confirm the conversion linker tag fires, all conversion tracking tags fire, and the GCLID is captured in a first-party cookie.

Then complete an actual test conversion — submit a form, complete a purchase in staging, trigger a phone call event. Verify the conversion appears in Google Ads within the expected window. Check the Conversions > Diagnostics report to confirm data is flowing and no conversion actions show “no recent conversions” warnings.

GA4: Confirm the measurement ID is deployed on the new domain. If running cross-domain measurement, update the configuration to include the new domain. Add the new domain to your referral exclusion list — without this step, traffic from your old domain (still redirecting) appears as referral traffic, inflating your numbers and masking the true source of conversions. Verify conversion events are firing correctly using GA4 DebugView. For ongoing conversion path optimization after migration, Web Upon’s CRO services can help ensure nothing falls through the cracks.

Meta Pixel: Use the Meta Pixel Helper extension on the new domain. Verify standard events (PageView, Lead, Purchase) and custom events fire correctly. Test the full conversion path — the pixel needs to fire on the confirmation page, not just the landing page.

Microsoft UET: Verify tag firing with the UET Tag Helper extension. Confirm conversion goals tied to UET events register on the new domain.

Manage Smart Bidding Through the Transition

Most migration guides skip this section entirely. It’s the one that can cost the most.

Here’s the core insight: Google Ads smart bidding algorithms — Target CPA, Target ROAS, Maximize Conversions, Maximize Conversion Value — don’t see your domain. They see conversion data. A Google Ads domain change, by itself, doesn’t trigger a learning period — domain changes aren’t among the documented triggers (which include new strategy creation, target changes, and campaign composition changes). If your conversion actions remain the same, tracking doesn’t gap, and conversions keep flowing into the same actions, the algorithm’s optimization signal stays intact.

The danger isn’t the domain change. It’s the conversion data gap. If tracking breaks for even 24–48 hours, smart bidding loses its real-time signal and may enter a learning period. Google’s documentation states that recalibration requires approximately 50 conversion events or three conversion cycles. For campaigns generating 5–10 conversions per day, that’s a week or more of unstable performance. Lower-volume campaigns could take three to four weeks.

Mitigation for high-budget campaigns: The safest smart bidding domain change strategy is to reduce algorithmic dependency during the highest-risk window. If you’re not fully confident in conversion tracking continuity — and healthy skepticism is warranted — consider temporarily switching your highest-budget smart bidding campaigns to Manual CPC or Enhanced CPC before the migration window. This removes the algorithm’s dependency on real-time conversion data during the highest-risk period.

Once 2+ weeks of clean, uninterrupted conversion data are confirmed on the new domain, switch back to automated bidding. The algorithm will enter a brief learning period, but it will calibrate on clean data rather than trying to optimize through a gap.

Isolate variables. Don’t change your bid strategy and migrate your domain at the same time. If performance drops and you’ve made both changes simultaneously, you can’t diagnose whether the issue is tracking-related or bid-strategy-related. One change at a time, measure, then proceed.

Migration Execution Checklist Summary

Task	Owner	Status	Due Date
Deploy 301 redirects for all ad URLs
Test every redirect: status code, destination, parameter passthrough
Test redirects through CDN/caching layer specifically
Verify SSL certificate on new domain
Update final URLs in Google Ads (ads, sitelinks, assets, DSA feeds)
Update tracking templates at account/campaign level
Update final URLs in Microsoft Ads
Update destination URLs in Meta Ads (after pixel verification)
Verify Google Ads conversion tracking (Tag Assistant + test conversion)
Verify GA4 measurement ID, cross-domain config, referral exclusions
Verify Meta Pixel firing (all standard and custom events)
Verify Microsoft UET tag firing and conversion goals
Confirm smart bidding strategy decision (maintain or temp switch to manual)

Post-Migration: Monitor, Validate, and Optimize

The migration is live. Stable doesn’t mean healthy — silent failures can take days to surface in reports. For the next 2–4 weeks, active monitoring is the job.

Run a 48-Hour Conversion Tracking Validation

The first 48 hours are active surveillance, not passive waiting.

Set up a monitoring dashboard with these reports open simultaneously:

• Google Ads: Campaigns > Conversions tab (real-time count), Conversions > Diagnostics (tracking health), and Change History (to catch automated changes triggered by the migration).
• GA4: Realtime report (confirming active users are tracked on the new domain), Acquisition > Traffic Acquisition (watching for self-referral from the old domain), and DebugView for event validation.
• Back-end system: Your CRM, e-commerce platform, or lead management system — compare its conversion count against what Google Ads reports. Google Ads shows 15 conversions but your CRM logged 22 form submissions? That’s a tracking gap.

Key signals to monitor:

• Self-referral from the old domain. If it appears as a referral source in GA4, the referral exclusion list hasn’t been updated or cross-domain measurement is misconfigured. This inflates referral traffic and misattributes conversions.
• GCLID auto-tagging. Check Google Ads > Conversions > Diagnostics and confirm GCLID is populating correctly on the new domain. Warnings here demand immediate investigation.
• Ad policy disapprovals. Check the Google Ads Policy Manager within 24 hours. Landing page mismatches, redirect issues, and SSL problems trigger automated disapprovals that can pause ads before you notice. A bulk disapproval across hundreds of ads can zero out impression share before you notice.

Compare Post-Migration Performance to Your Pre-Migration Baseline

At the 1-week and 4-week marks, pull performance data and compare against the baseline you captured during Pre-Migration. This is why that baseline exists — without it, you’re guessing whether changes are migration-related or normal market fluctuation.

Metrics to compare: CTR, CPC, CPA, ROAS, conversion rate, impression share, and Quality Score at the keyword level for top performers.

Metric	Pre-Migration Baseline	Week 1 Post	Week 4 Post	Variance (%)
CTR
CPC
CPA
ROAS
Conversion Rate
Impression Share
Quality Score (top keywords avg.)

What’s normal: Some fluctuation in the first 1–2 weeks is expected. Quality Score may dip temporarily as Google re-evaluates landing page experience signals on the new domain — the algorithm re-crawls, re-assesses page speed, and re-establishes content relevance. Google evaluates Quality Score based on comparison with other advertisers over the last 90 days, and landing page experience assessment uses data from Google’s various crawlers. A Quality Score drop of 1–2 points that recovers within two weeks is common in practice. CTR and CPC may shift modestly as ads go through re-review and smart bidding learning periods resolve.

What’s not normal: Conversions dropping to zero (tracking is broken, not fluctuating). Quality Score falling 3+ points across multiple keywords (landing page experience issue — investigate speed, SSL, content match). CPA doubling or ROAS halving with no recovery trend after 7 days (smart bidding has entered a full learning period or conversion data is gapped).

Troubleshoot Common Post-Migration Failures

When something breaks, speed of diagnosis is everything.

Conversion count drops to zero 

Cause: Tags aren’t firing on the new domain, GCLID capture is broken, or conversion actions were inadvertently deactivated. 

Fix: Re-run Tag Assistant on the new domain. Verify the conversion linker fires. Confirm GCLID is stored as a first-party cookie. Check that conversion actions are active in Google Ads > Goals > Conversions. If using GTM, verify the container is published and triggers reference the correct domain.

Quality Score drops across multiple keywords 

Cause: Landing page speed is slower on the new domain, content mismatch between ad copy and landing page, or SSL certificate issues. 

Fix: Run PageSpeed Insights on affected pages. Compare load times against the old domain. Verify content on the new URL matches what Google’s relevance algorithm expects. Confirm the SSL cert is valid — mixed content warnings can significantly hurt landing page experience scores.

CPC spikes sharply 

Cause: Usually Quality Score drops and smart bidding re-learning compounding each other. Lower Quality Score raises auction CPCs; smart bidding in a learning period means the algorithm is testing ranges rather than optimizing. 

Fix: Don’t panic-adjust bids in the first week. Fix landing page issues and give Google time to re-evaluate. If smart bidding is in a learning period, let it resolve — interference resets the clock.

Ad disapprovals 

Cause: Redirect chains, broken landing pages, destination URL mismatches, or SSL issues.

Fix: Check Policy Manager for specific reasons. Fix the root cause, then request re-review. Web Upon’s paid search services can help diagnose persistent post-migration issues.

Self-referral inflation in GA4 

Cause: New domain not added to GA4’s referral exclusion list, or cross-domain measurement not updated. 

Fix: In GA4: Admin > Data Streams > your web stream > Configure tag settings > Show all > List unwanted referrals. Add the old domain. If running cross-domain measurement, update the domain list in GTM.

Close the Loop: Report, Record, and Update the Runbook

Within 4 weeks, prepare a post-migration performance report for stakeholders. Include: performance comparison against baseline, tracking issues encountered and their resolution, timeline of interventions, and recommendations for future migrations. The next migration, or the next person who inherits these campaigns, will need this record. What broke, how it was fixed, what you’d do differently. Update the runbook and store it alongside the report.

Post-Migration Checklist Summary

Task	Owner	Status	Due Date
Run 48-hour active monitoring protocol
Verify GCLID auto-tagging on new domain
Check for self-referral traffic from old domain in GA4
Monitor for ad policy disapprovals (first 24 hrs)
Pull Week 1 performance comparison vs. baseline
Pull Week 4 performance comparison vs. baseline
Investigate any Quality Score drops > 2 points
Diagnose and resolve any conversion tracking gaps
Prepare stakeholder post-migration performance report
Document lessons learned and update migration runbook

When to Call In Specialist Help

A domain migration with active ad spend is one of the highest-risk operations in paid media management. This checklist gives you the process — the complete protocol for protecting conversion data, maintaining smart bidding continuity, and catching failures before they compound. Executing it under real pressure, with real budget on the line, across multiple platforms and teams simultaneously — that’s a different matter.

The margin for error is thin. A redirect that strips query parameters silently breaks attribution. A forgotten tracking template hardcodes the old domain into hundreds of ad URLs. A conversion gap measured in hours sends a smart bidding strategy into a learning period that takes weeks to resolve. Every one of these failures is preventable, but preventing them requires experience across paid media, tag management, server configuration, and campaign strategy at the same time.

Web Upon has executed this process across dozens of domain migrations — not just SEO redirect maps, but full paid media continuity operations where every dollar of ad spend stayed tracked, attributed, and optimizing throughout the transition. If you’re planning a domain migration and your ad spend is on the line, reach out for a migration readiness assessment.