πŸ“Š Find wasted Meta ad spend by placement, region, age and hour with Claude

⚑ 75 views Β· πŸ“Š Market Research & Insights

Description

Quick overview

This workflow pulls the last 30 days of Meta Ads insights across multiple breakdowns, calculates an account cost-per-result benchmark, flags high-waste delivery slices, and uses Anthropic Claude to rank a prioritized β€œkill list” with recommended actions.

How it works

  1. Runs when triggered manually.
  2. Sets the analysis configuration, including the date preset, spend floor, cost-per-result multiple, minimum attribution threshold, and which Meta β€œaction” events count as results.
  3. Queries the Meta Marketing API for account-level insights and breakdown insights (placement, region, age/gender, and hour), then computes the account cost-per-result benchmark and skips breakdowns with low conversion attribution coverage.
  4. Flags breakdown slices that exceed the spend floor and either have zero results or a cost-per-result above the benchmark threshold, then calculates β€œat risk” spend and keeps the top waste candidates.
  5. Sends the waste list and benchmark context to Anthropic Claude to rank the slices and return a recommended action (pause, exclude, or reallocate) with a one-line rationale.
  6. Prints a formatted wasted-spend report (and returns the parsed JSON ranking) for use in downstream reporting.

Setup

  1. Add your Meta Marketing API details as environment variables: META_ACCESS_TOKEN, META_AD_ACCOUNT_ID (act_…), and optionally META_API_VERSION.
  2. Add your Anthropic credential as an environment variable (ANTHROPIC_API_KEY) to enable Claude ranking.
  3. Review and adjust RESULT_ACTIONS, SPEND_FLOOR, CPR_MULTIPLE, and MIN_ATTRIBUTION in the configuration step to match the conversion events and thresholds you optimize for.

Requirements

Customization

Additional info

Built by nocode.expert (done-for-you automation and tracking). Auto-skips delivery breakdowns Meta does not attribute conversions to, so you never get false waste. All secrets read from environment variables.

πŸ”— Nodes Used

HTTP Request, Facebook Graph API

πŸ“₯ Import

Download workflow.json and import into n8n: Workflow menu β†’ Import from File

πŸ“– Importing guide Β· πŸ”‘ Credential setup