When your primary domain fails—because of DNS misconfiguration, registrar expiry, SSL problems, CDN issues, or a hosting outage—paid social is usually the first channel to burn budget without returns. Clicks continue, but users land on error pages, conversions drop, learning phases destabilize, and attribution fragments. The objective during an outage is to preserve pipeline flow, maintain signal quality, and avoid losing the algorithmic momentum you have already paid for.
This playbook outlines how social media and performance marketers can rapidly swap destinations, pivot formats, preserve tracking, manage delivery, communicate with audiences, and then cleanly restore campaigns once the site is back.
Key principles:
- Keep a working path to value live (form, schedule, download, purchase alternative).
- Maintain consistent identifiers (UTMs, event names, dedup keys) so reporting remains coherent.
- Reduce disruptions to campaign structure to minimize learning resets.
- Communicate clearly with prospects and stakeholders.
- Document every temporary change to reverse cleanly.
2) First-hour triage: keep traffic productive
Confirm the issue and its scope
- Validate the outage with multiple checks: direct domain, subdomains, staging, and CDN endpoints; use a mobile network to rule out local DNS.
- If DNS is the problem, expect propagation delays; treat the outage window as variable.
Rapidly swap destinations
- Use a resilient, pre-approved link hub:
- A Link in Bio or profile link hub that you control (e.g., a minimal page hosted on a separate platform). Include your key CTAs, a privacy policy link, and contact options.
- A smart redirect link (shortener/vanity URL) you can repoint without editing ads. Keep TTL low and hosting on a separate, reliable domain.
- Deploy backup landing pages:
- Host mirrored pages on an alternate domain or subdomain served by a different provider (e.g., static mirrors on Netlify/Vercel, or a quick Google Sites page).
- Keep these noindexed, compliant, and pixel-enabled when possible.
- Pre-approve these domains in your Business Manager and add them to your ad account’s list of acceptable landing pages.
- Route to third-party destinations when viable:
- E-commerce: temporary links to marketplace listings (e.g., Amazon) or a lightweight hosted checkout. Make sure pricing and availability match current ads.
- Calendaring: direct to scheduling tools for demos/consultations.
- Content: host gated PDFs or videos on cloud storage with share links and a simple lead capture form.
Pivot to native capture on Facebook
- Switch affected conversion campaigns to Lead Ads (Instant Forms) or launch parallel Lead Ads ad sets:
- Mirror your core fields (name, email, phone), add consent text, and link a privacy policy.
- Use Custom Questions if you need qualification; keep forms short to protect CPL.
- Connect the form to your CRM via native integrations or middleware (Zapier/Make) to trigger instant follow-up.
- Consider Click to Message (Messenger or WhatsApp) for high-intent queries if you have live agents or bots to respond.
Minimize editing shock to delivery
- Prefer destination changes over rebuilding campaigns. Bulk-edit URLs in-place to preserve learnings.
- If you must spin up new ad sets (e.g., for Lead Ads), keep budgets and audiences close to your current baseline to avoid destabilizing overall delivery.
3) Preserve measurement: UTMs, Pixel alternatives, and CAPI
Keep UTMs consistent
- Maintain your standard UTM schema even when sending traffic to backup or third-party destinations so that reporting remains attributable.
- Example schema:
- utm_source=facebook
- utm_medium=paid_social
- utm_campaign={{campaign.name}}
- utm_content={{ad.name}}
- utm_term={{adset.name}}
- If you use short links, ensure parameters are appended and preserved through redirects.
Use a smart link for continuity
- Create a single “campaign gateway” URL (on a resilient domain) that 302-redirects to your current destination. Point ads to this gateway during outages.
- Benefits: change the endpoint once, keep UTMs consistent, and reduce repeated ad edits.
Compensate for pixel disruptions
- Pixel events on your downed domain will not fire. Rely on:
- Lead Ads event signals (Facebook collects these natively).
- Messenger/WhatsApp event signals.
- Server-side Conversions API (CAPI) from your CRM or automation platform.
- If using a backup domain, pre-verify that domain in Business Manager and configure Aggregated Event Measurement (AEM) so events can rank and optimize.
Implement Conversions API correctly
- Send server events for key milestones (Lead, CompleteRegistration, Schedule, Purchase) from your CRM/workflow tool.
- Use consistent event names and include:
- event_time (UTC timestamp)
- event_name (e.g., Lead)
- event_id (dedup key also used by client events when they resume)
- user_data with hashed identifiers (email, phone, IP, user agent where applicable)
- custom_data (value, currency, content_ids)
- Map leads from Lead Ads or messaging to server-side events to maintain optimization signals while the site is offline.
Plan for AEM and domain verification
- Verify your primary domain and at least one backup domain in advance.
- Configure AEM priorities to include the events you will use on backup properties or lead forms.
- When you switch domains, review event prioritization and confirm signals appear in Events Manager.
Validate signal health
- Use Events Manager Test Events to verify CAPI hits.
- Click through ads in preview to confirm UTMs pass to the backup destination and forms submit correctly.
- Ensure privacy policies and consent handling remain accessible and accurate on temporary pages.
4) Campaign control: pause, reroute, reallocate
Identify and isolate affected assets
- In Ads Manager, filter by Destination URL contains your primary domain to surface impacted ad sets and ads.
- Bulk-edit the final URL to your gateway link, backup page, or lead form. Use URL Parameters at the ad level to keep UTMs aligned.
Decide what to pause vs. reroute
- Bottom-of-funnel conversion ads that depend on the site checkout should pause or route to an alternative checkout.
- Mid- and upper-funnel prospecting can reroute to Lead Ads, content downloads, or messaging to keep the funnel fed.
- Retargeting that relies on website audiences will degrade. Temporarily expand to:
- Engagers (page, video, lead form viewers)
- Customer lists (hashed)
- Broad signals with strong creative and clear CTAs
Reallocate budgets deliberately
- Shift spend into Lead Ads or engagement campaigns that capture intent without the website.
- Maintain daily budgets close to historical norms to avoid volatility; scale gradually once performance stabilizes.
- Cap frequency if using smaller pools (e.g., lead form retargeting) to prevent fatigue.
Update creative and copy
- Adjust CTAs: “Get the guide,” “Request a quote,” “Book a call,” or “Message us now,” rather than “Shop now” or “Learn more on our site.”
- Set expectations transparently but professionally: “We’re temporarily processing requests via this form.”
- Ensure compliance: include privacy links and any required disclosures.
Quality assurance before resuming full spend
- Test each ad’s link on mobile and desktop.
- Submit at least one lead per form to confirm CRM delivery, notifications, and automation sequencing.
- Validate that ad approvals remain intact after URL edits.
5) Communication, restoration, and hardening for next time
Communicate with prospects and customers
- Pin a short status update on your Facebook Page and other key channels. Provide the alternative path (Lead Form, messaging, backup page) and expected resolution window.
- Reply to ad comments with the current working link or instructions when relevant and safe.
- For high-intent audiences (open opportunities, warm leads), send an email/SMS update with the temporary path and reassure them their requests are being handled.
Coordinate internally
- Spin up a cross-functional channel (marketing, web, IT, sales, support). Assign owners for: destination swaps, tracking, comms, and restoration.
- Keep a change log with timestamps for every edit in Ads Manager and your CRM.
Restore cleanly once the site is back
- Technical validation checklist:
- DNS fully propagated; SSL valid across http/https and www/non-www.
- Landing pages load fast on mobile and desktop; no mixed-content errors.
- Pixel fires on priority pages; verify events in Events Manager.
- CAPI deduplication functioning (no spikes in “Processing Failure”).
- Backup redirects deactivated or pointed back to standard flow.
- Advertising checklist:
- Revert ad destination URLs from gateway/backup to primary pages (or repoint the gateway).
- Keep UTMs identical to pre-outage schema.
- Restore conversion campaigns and website retargeting; re-balance budgets from Lead Ads to site conversion campaigns based on performance.
- Update creatives to original CTAs and remove temporary messaging.
- Monitor CPA/ROAS closely for 48–72 hours; the algorithm may need a brief stabilization period.
- Data reconciliation:
- Deduplicate leads captured via native forms and merge into CRM contact records.
- Attribute conversions from Lead Ads and CAPI to campaigns; annotate your reporting for the outage window.
- Follow up promptly with leads collected during the outage to prevent decay.
Harden your stack to reduce future risk
- Domain hygiene:
- Enable auto-renewal and multiple renewal reminders at your registrar.
- Implement Secondary DNS with low TTL for faster failover.
- Pre-verify a backup domain in Facebook Business Manager and configure AEM.
- Infrastructure resilience:
- Host a minimal, static “failsafe” landing page on a separate provider with pixel/CAPI support and privacy links.
- Maintain a smart redirect gateway on a resilient domain so ad edits are rarely needed.
- Operational readiness:
- Create evergreen Instant Forms for your key offers and keep them published but paused for fast activation.
- Document a one-page runbook with: link inventory, CRM mappings, UTM standards, Events Manager test procedures, and owner contacts.
- Set up uptime monitoring with multi-region checks and on-call alerts.
- Run a quarterly drill: switch to backup flows for one hour, validate end-to-end tracking, and refine the playbook.
By treating DNS and domain outages as a solvable routing and signaling problem, you can protect spend, preserve data integrity, and keep your growth engine running—even when your primary site cannot. With pre-built backups, a consistent measurement layer, and disciplined campaign control, your Facebook ads can continue to generate value while the web team restores the lights.
