RecipePinterest Ads
Diagnose a Pinterest CPA spike fast
The Pinterest CPA-spike sequence, attribution lag treated as a first-class suspect.
IntentWhy Pinterest CPA jumped: tag, lag, or auction.
- 2
- Steps
- 2
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- CPA jumped beyond noise on meaningful spend.
Do not use it when
- No specific contraindication beyond the preconditions below.
What it needs first
Required
Preconditions
- The account is ticked in the dashboard, confirmed via list_accounts.
Inputs
window- Analysis window.Default: last 30 days.
Procedure
In order. Every tool named is one the gateway ships, and links to its reference.
Split spend vs conversions with a lag-trimmed window.
Check conversion setup and tag recency.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
The spike sits inside Pinterest's long attribution tail
Conclude
Probably lag, not cost: re-read in days, and say which day the verdict is due.
Evidence every conclusion must carry
- Every figure carries its account, metric and window.
- Anything below a readable sample size is reported as unjudged, not as zero.
Where the agent stops
- The readout changes nothing. Any change it motivates goes through Safe Writes: preview, human confirmation, then apply.
How it goes wrong quietly
The cases where the analysis is wrong and still looks right. Read them before trusting a number.
- Pinterest windows are long by design: judging this week's CPA this week is structurally premature.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.