Every Facebook campaign is only as strong as the click that lands and converts. Broken domains, expired SSL certificates, misfiring pixels, or sluggish mobile pages silently drain spend and erode attribution. A rigorous pre‑flight quality assurance (QA) process ensures each impression has a fair chance to convert—and that every conversion is correctly recorded.

This checklist provides a structured, step‑by‑step process your team can run before launch and reuse for ongoing governance. It covers domain and link integrity (DNS/SSL), pixel and Conversions API validation, event configuration and priorities, UTM hygiene, landing page speed and mobile UX, and the resilience steps—failover links and real‑time monitoring—that keep revenue flowing even when something breaks.

Step 1: Verify Domain and Link Integrity (DNS, SSL, Redirects)

Your destination must be reachable, secure, and stable across all variants. Validate the following:

1) DNS resolution

• Confirm A/AAAA records for root and www resolve globally (e.g., via DNSChecker).
• Check CNAMEs for tracking domains or vanity links.
• Ensure TTLs are reasonable (not excessively long) to facilitate quick fixes pre‑ or mid‑campaign.
• Validate there is a single canonical destination (e.g., non‑www redirects to www or vice versa) to avoid split analytics.

2) SSL/TLS health

• Run an SSL test (e.g., SSL Labs) to verify certificate validity, full chain, hostname coverage (root and subdomains), and upcoming expiry.
• Enforce HTTPS everywhere (301 redirect HTTP → HTTPS).
• Enable HSTS only after confirming all subresources load over HTTPS to avoid mixed‑content issues.

3) Redirect behavior and UTM preservation

• Map your exact ad URLs and test each in an incognito window and on mobile.
• Ensure all redirects are 301/302 (not meta refresh or JS‑only).
• Verify that query strings (UTMs, fbclid) are preserved across all hops.
• Standardize trailing slashes and casing to avoid fragmenting analytics.
• Confirm final landing URL domain matches your verified domain in Meta Business Manager.

4) Link accessibility and edge cases

• Test from multiple geographies and mobile networks (carrier restrictions and geo‑rules can block domains).
• Validate deep links (if used) gracefully fall back to web when the app is not installed.
• For consent and geofencing, ensure regional redirects do not strip UTMs or block content unnecessarily.

5) Domain verification in Meta

• Complete domain verification via DNS TXT, HTML file, or meta tag in Meta Business Manager.
• Assign permissions for ad accounts and ensure the intended conversion events are associated with this verified domain.

Step 2: Confirm Tracking Fidelity (Pixel, Conversions API, Event Configuration)

Accurate measurement is the foundation of optimization. Before spending, validate both browser and server‑side signals.

1) Facebook Pixel basics

• Ensure only one pixel base code fires per page unless you have a deliberate multi‑pixel strategy.
• Use the Meta Pixel Helper to confirm pageview and relevant standard events fire with correct parameters (content_ids, value, currency).
• Avoid firing events on page load if they represent user intent (e.g., Purchase should fire post‑transaction, not on checkout start).

2) Conversions API (CAPI)

• Implement server‑side events for your key conversions to improve signal resilience (ad blockers, iOS restrictions, network drops).
• Include event_name alignment with pixel events and pass an event_id to deduplicate where both fire for the same action.
• Populate advanced matching fields (hashed) where compliant (email, phone, external_id) to raise Event Match Quality.

3) Deduplication and quality checks

• In Events Manager > Test Events, trigger each conversion path. Confirm both pixel and CAPI entries appear with deduped status.
• Review Diagnostics for warnings (parameter missing, currency mismatch, invalid content_ids).
• Audit Event Match Quality and aim for “Good” for primary events.

4) Event priorities and attribution readiness

• In Events Manager, confirm your key conversion events exist, are correctly configured, and align with campaign objectives (e.g., Purchase for Sales, Lead for Lead Gen).
• Set and review event priority ordering so the most valuable outcome is favored when privacy constraints limit reporting.
• If using multiple domains, ensure events are associated with the correct verified domain to avoid optimization and reporting gaps.

5) Privacy and consent compliance

• Validate that consent banners gate non‑essential events appropriately and that consent states are honored by both pixel and CAPI.
• Ensure region‑specific requirements (e.g., GDPR/EEA) do not inadvertently suppress essential parameters or break deduplication.

Pro tip: Document a canonical event map that defines event names, triggers, parameters, and ownership. Include links to GTM/Server‑GTM containers or code repos for traceability.

Step 3: Standardize Attribution with Robust UTM Tagging

A consistent UTM strategy ensures clean reporting in analytics, BI, and MMM. Establish and validate the tagging scheme before launch.

1) Adopt a standard template

• utm_source=facebook
• utm_medium=paid_social
• utm_campaign={{campaign.name}} or {{campaign.id}}
• utm_content={{ad.name}}
• utm_term={{adset.name}} or audience descriptor
• Optional: placement={{placement}} and site_source_name={{site_source_name}} (as additional query parameters)

2) Implement at scale

• Use Facebook’s dynamic parameters (e.g., {{campaign.name}}) to auto‑populate values and reduce manual errors.
• Enforce lowercase and hyphen/underscore naming conventions to avoid duplicates in analytics.
• Prohibit PII in UTMs.

3) Validate end‑to‑end

• Click test each ad preview; confirm UTMs persist through every redirect to the final URL.
• Ensure your analytics platform auto‑tags fbclid or does not override your UTMs.
• For link shorteners or smart links, verify they do not strip or re‑order parameters.

4) Governance

• Maintain a living taxonomy document that lists campaign naming rules, allowed values, and examples.
• Add validation to your trafficking sheet or ad creation workflow (e.g., regex checks) to prevent shipping untagged links.

Step 4: Guarantee Conversion‑Ready Landing Pages (Speed, Stability, Mobile UX)

A click wasted on a slow or confusing page is budget burned. Validate user experience and performance across devices.

1) Speed and stability metrics

• Test with PageSpeed Insights or WebPageTest for mobile; track LCP, INP, and CLS.
• Target: LCP < 2.5s on a throttled 4G profile for your key geographies.
• Eliminate render‑blocking resources; inline critical CSS; defer non‑critical JS.
• Compress images (WebP/AVIF), preload hero images and fonts, and enable HTTP/2 or HTTP/3.

2) Mobile UX essentials

• Place the primary CTA above the fold with adequate tap targets (44px+).
• Ensure forms are short, mobile‑friendly, and keyboard types match inputs (tel, email, number).
• Validate error states, required fields, and confirmation messages.
• Avoid intrusive interstitials that obscure content or CTAs.
• Confirm tracking consent flows do not obstruct progression or hide the CTA on smaller screens.

3) Functional paths to conversion

• Test complete journeys: ad click → landing page → add to cart/lead → checkout/thank you.
• Validate coupon fields, shipping calculators, and payment gateways in both guest and logged‑in flows.
• Confirm the thank‑you page consistently renders and fires the Purchase/Lead event.

4) Content and continuity

• Match headline and hero content to ad promise to reduce bounce and improve Quality Ranking.
• Localize currency, units, and language where targeting international audiences.
• Ensure trust signals (reviews, guarantees, security badges) are visible and load instantly.

5) Resilience under load

• Run a light load test or traffic spike simulation to catch bottlenecks.
• Ensure CDN caching is configured for static assets and that cache busting does not break UTMs or cause redirect loops.

Step 5: Build Resilience with Failover Links and Real‑Time Monitoring

Even the best setups encounter outages, expired certs, or third‑party hiccups. Prepare for failure modes before they happen.

1) Failover link strategy

• Define a backup destination for each campaign (e.g., a simplified landing page or the most relevant category page).
• Implement server‑side logic (CDN/edge or reverse proxy) that:
  • Checks primary page health (status code, TLS validity, load time threshold).
  • Automatically 302‑redirects to the backup if the primary fails.
  • Preserves all query parameters (UTMs, fbclid) in the redirect.
• For app deep links, include a fallback chain: app → app store (if desired) → mobile web.

2) Health checks and alerts

• Set up synthetic checks every 1–5 minutes from multiple regions to request your ad URLs and measure:
  • HTTP status (expect 200/301/302).
  • TLS validity and days to expiry.
  • TTFB and total load time thresholds (e.g., fail if TTFB > 800 ms or on repeated 5xx).
• Send alerts to Slack/Teams/Email with the affected ad sets and URLs.
• Log incidents with timestamps to correlate with spend and performance dips.

3) Real‑time link monitoring

• Track landing page availability and latency over time; visualize in a dashboard.
• Monitor redirect chains for unexpected hops introduced by tag managers or new plugins.
• Add JavaScript error tracking on landing pages to catch runtime failures affecting forms or CTAs.

4) Operational runbook and ownership

• Assign owners for domains, certificates, pixels/CAPI, analytics, and landing pages with clear escalation paths.
• Document renewal dates (domains, SSL, CDN) and set reminders well ahead of expiry.
• Conduct a “game day” drill: simulate a landing page outage and verify failover and alerting work as intended.

5) Final pre‑flight go/no‑go checklist

• Domain resolves globally (root and www) and redirects canonically.
• SSL valid, full chain present, HTTPS enforced.
• All ad URLs tested; UTMs persist across redirects.
• Pixel and CAPI firing with deduplication; diagnostics clean; event match quality good.
• Event priorities configured for your primary conversion.
• UTM taxonomy applied via dynamic parameters across all ads.
• Landing pages pass mobile performance thresholds; forms and payments verified.
• Failover links configured; health checks and alerts live.
• Ownership and escalation documented; monitoring dashboards active.

With this pre‑flight process institutionalized, your team reduces preventable errors, protects ROAS, and preserves the integrity of your data. Most importantly, you ensure every paid click lands on a working, fast, and conversion‑ready page—so optimization efforts reflect true performance, not avoidable friction.