Meta Pixel Outage Playbook: First Hour Response

Detect the outage (minutes 0-5)

Detection speed determines recovery scope. Most brands discover outages through customer complaints or ad performance collapse, not proactive monitoring. Establish a detection threshold: if conversions fall below 20% of yesterday's same-hour rate for 2 consecutive 15-minute windows, treat it as an outage until proven otherwise.

Check three signals simultaneously: (1) Meta Ads Manager - view Conversions column in campaign performance table; if all campaigns show zero or near-zero conversions, Pixel is likely down; (2) Meta Events Manager - navigate to Test Events and fire a test conversion from your store; if it doesn't appear within 30 seconds, Pixel transmission is broken; (3) Meta status page at status.fb.com - search for 'Conversions API' or 'Pixel' incidents.

Conversions drop >80% below rolling 7-day average for 2+ consecutive 15-min windows = confirmed outage
Test Events in Events Manager should show new events within 30 seconds of firing
Check status.fb.com for official incident reports - do not rely on Meta support chat for confirmation

Verify Pixel health on your store (minutes 5-15)

Outages can be partial (Pixel fires but Meta doesn't receive) or local (your Pixel implementation is broken, not Meta's infrastructure). Verify your store is sending data correctly before escalating to Meta.

Use browser DevTools: open any product page, go to Network tab, filter by 'facebook' or 'analytics'. Complete a test purchase or add-to-cart action. Look for requests to 'graph.facebook.com' or 'connect.facebook.net'. If requests appear but show 400-500 status codes, Meta's API is rejecting your data. If no requests appear, your Pixel code is not firing - check Shopify app settings and pixel ID configuration. If requests show 200 status codes, your Pixel is working; the outage is on Meta's reporting side.

Network tab in DevTools shows request status - 200 = Pixel firing, 400-500 = Meta API rejecting, no requests = code not installed
Test a full purchase flow, not just pageviews - conversion events are most likely to fail first
Verify pixel ID in Shopify settings matches the ID in Meta Events Manager (Settings > Data Sources)

Pause spend and notify stakeholders (minutes 15-25)

During a confirmed outage, every dollar spent on Meta ads is untracked. Pausing campaigns prevents wasted spend and gives you a clear before/after boundary for recovery analysis. Pause at the account level, not individual campaigns, to avoid accidental resume.

Send internal notification to: finance (revenue impact), customer service (prepare for tracking-related questions), and paid media team. Template: 'Meta Pixel outage detected at [TIME]. Conversions tracking offline. All Meta campaigns paused. Recovery ETA: TBD. Will update hourly.' Do not notify customers or public channels - outages typically resolve within 2-4 hours and public statements create unnecessary alarm.

Pause all Meta ad accounts at account level (not campaign level) to maintain clear spend boundary
Notify: finance, CS, paid media. Do not post on social or email customers
Document pause time and last known conversion count for recovery reconciliation

Preserve data and configure fallback tracking (minutes 25-45)

Meta outages can cause permanent data loss if you don't capture conversions during the blackout. Set up secondary tracking to record conversions that Meta misses. Google Analytics 4 and Klaviyo both capture purchase events independently of Meta Pixel.

In Shopify, verify that Google Analytics 4 is connected and firing (Settings > Apps and integrations > Google Analytics). Check that Klaviyo or your email platform is capturing purchase events (these typically sync from Shopify order data, not Pixel, so they're unaffected by outages). If you use a CDP or data warehouse, ensure it's pulling order data directly from Shopify's API, not relying on Pixel webhooks. This secondary data becomes your source of truth for conversions during the outage window.

Verify GA4 is connected and firing - check real-time reports for purchase events
Confirm email/SMS platform (Klaviyo, Klaviyo, etc.) is syncing Shopify orders directly
If using Conversions API alongside Pixel, check that server-side events are still transmitting (separate from Pixel)
Document all conversions from secondary sources during outage window for manual reconciliation

Monitor recovery and reconcile data (minutes 45-60)

Meta outages typically resolve within 2-4 hours. Check Events Manager every 10 minutes after minute 45. When test events start appearing again, Pixel is recovering. Wait 5 minutes after first successful test event before resuming campaigns - this confirms the recovery is stable.

Once campaigns resume, compare Meta's reported conversions to your secondary data sources (GA4, Klaviyo, Shopify order count). Meta will likely undercount conversions during the recovery window because some events are lost in transit. Calculate the delta: (Shopify orders during outage) - (Meta conversions reported) = lost conversions. Document this number for finance and performance analysis. Do not attempt to manually adjust Meta's conversion count - Meta's support team cannot backfill lost data.

Test Events in Events Manager should show new events within 30 seconds of recovery
Wait 5 minutes of stable test events before resuming campaigns
Compare Meta conversions to Shopify order count and GA4 purchase events
Document delta for finance - this is your actual revenue impact, not Meta's reported number
Do not request manual backfill from Meta - they cannot restore lost conversion data

Resume campaigns and post-outage review (minutes 60+)

Resume campaigns at account level once recovery is confirmed. Campaigns will resume with previous budgets and targeting - no manual adjustment needed. Monitor for 30 minutes post-resume to ensure no secondary failures occur. If conversions drop again, pause immediately and escalate to Meta support with specific timestamps and test event logs.

Within 24 hours, conduct a post-outage review: (1) Calculate total revenue lost (Shopify orders during outage minus Meta-attributed revenue); (2) Identify which campaigns were paused and for how long; (3) Check if any audience syncs failed (Custom Audiences, Lookalike Audiences) - these can lag 24-48 hours after outages; (4) Review Meta's incident report for root cause and whether it affects your account specifically. Use this data to inform your outage response plan for next time.

Resume at account level, not campaign level
Monitor for 30 minutes post-resume for secondary failures
Calculate revenue impact: (Shopify orders) - (Meta-attributed revenue) during outage window
Check audience sync status 24 hours post-outage - custom audiences may need manual refresh
Archive incident report and response timeline for future reference

Prevent future outages with redundancy

Meta Pixel outages are infrastructure events, not preventable through configuration. However, redundancy reduces impact. Implement Conversions API (server-side tracking) alongside Pixel. Conversions API sends purchase events directly from your Shopify backend to Meta, bypassing browser-level failures. During Pixel outages, Conversions API often continues transmitting because it uses a different infrastructure path.

Set up a monitoring alert: use a tool like Databox or custom Zapier workflow to check Meta Ads Manager conversion count every 15 minutes. If conversions drop >80% for 2 windows, trigger a Slack alert to your paid media team. This reduces detection time from hours to minutes. Document your outage response playbook in a shared doc and run a quarterly drill - assign roles (detection lead, pause lead, communication lead) so everyone knows their responsibility when an outage hits.

Implement Conversions API alongside Pixel for redundant tracking
Set up automated monitoring alert if conversions drop >80% for 2 consecutive 15-min windows
Document playbook with assigned roles: detection, pause, communication, reconciliation
Run quarterly drill to validate response procedures

Questions

FAQ

How long do Meta Pixel outages typically last?

Most outages resolve within 2-4 hours. Outages lasting >6 hours are rare and usually indicate a major infrastructure failure. Check status.fb.com for estimated resolution time. Do not rely on Meta support chat for ETAs - they typically don't have real-time incident data.

Will Meta refund my ad spend during an outage?

No. Meta does not refund spend during outages, even if conversions are untracked. Your ads continue to run and charge normally. This is why pausing campaigns immediately is critical - you prevent additional wasted spend while tracking is down.

Should I manually add conversions to Meta after an outage?

No. Meta's support team cannot backfill lost conversion data. Attempting to manually re-upload conversions will create duplicate counts and corrupt your historical data. Accept the data loss and use it to justify investment in Conversions API redundancy.

What if only some of my Meta campaigns are affected?

Outages are account-level events - if Pixel is down, all campaigns using that Pixel are affected equally. If some campaigns show conversions while others don't, the issue is likely campaign-level (wrong event setup, audience sync failure) not a Meta infrastructure outage. Check Events Manager test events and your Pixel implementation before pausing.

Want this on your account?

Thirty minutes. Bring the number that keeps you up.

Book a demo

What to do when Meta Pixel stops firing