Automations

What are automations?

Automations let you take action automatically when an incident starts (and when it recovers). Use automations to pause ads, create tickets, page on-call, or notify stakeholders with the right context.

Meta Ads Guardrails (Pro)

Blind Spot Monitor includes a first-party Meta Ads automation so you can pause allowlisted campaigns when an incident opens and resume them on recovery—no Zapier/Make required.

Recommended playbook: pause ads when checkout breaks

If checkout is down, paid traffic can burn budget and frustrate customers. A common workflow is:

1. Incident opens on checkout → pause ads
2. Recovery alert → resume ads

1. 1

   Create (or pick) a trigger monitor

   Recommended: a checkout monitor (Checkout URL or Checkout Flow on Pro). This is what will trigger your pause/resume.

2. 2

   Connect Meta

   In the app, go to Automations and connect your Meta account.

3. 3

   Choose an ad account + allowlist campaigns

   Select the ad account you want Blind Spot to control, then check only the campaigns you’re comfortable pausing automatically.

4. 4

   Select trigger monitors + enable

   Choose which monitors are allowed to trigger ad actions (typically just checkout), then enable the automation.

Google Ads Guardrails (Pro)

Blind Spot Monitor also supports a first-party Google Ads automation so you can pause allowlisted campaigns when an incident opens and resume them on recovery.

1. 1

   Connect Google

   In the app, go to Automations and connect your Google account.

2. 2

   Choose a customer + allowlist campaigns

   Select the Google Ads customer account you want Blind Spot to control, then check only the campaigns you’re comfortable pausing automatically.

3. 3

   Select trigger monitors + enable

   Choose which monitors are allowed to trigger ad actions (typically just checkout), then enable the automation.

What advertising data Blind Spot uses

Blind Spot reads only the account and basic campaign identity/status needed to let you create a narrow allowlist and verify a safe pause or recovery. It does not need ad creative, audiences, leads, click-level data, conversions, budgets, bids, keywords, or targeting to operate Ads Guardrails.

Provider credentials are handled server-side and encrypted at rest. Google requests offline access because incidents and recoveries can happen while you are not using the app. Blind Spot does not sell provider data, use it to target advertising, or create cross-merchant advertising benchmarks.

For the complete inventory and deletion controls, see Ads data & deletion.

Disconnect safely

If Blind Spot shows campaigns it paused, recover them before disconnecting so they are not left stranded. Then disable the automation and disconnect it from Automations. Disconnect requests provider-side token revocation and removes Blind Spot's active provider connection and encrypted token. If the provider cannot confirm revocation, Blind Spot completes local deletion and tells you to remove the integration in provider settings.

Webhook automations (Zapier/Make)

Webhooks are useful when you want custom playbooks or integrations Blind Spot doesn’t support natively yet.

At a high level:

• Create a workflow that receives a webhook from Blind Spot.
• If the event is an incident, run your action (pause ads, create a ticket, page on-call).
• If the event is a recovery, run your resume/close action.

Other common automations

• Create a support ticket (Zendesk / Gorgias) when a CRITICAL incident opens.
• Page on-call via your existing system (PagerDuty / Opsgenie) using a webhook bridge.
• Notify stakeholders (email/Slack) with incident links and recommended next steps.