Snapchat Ads joins, and every delete is permanent so every delete waits for a person
Snapchat Ads is a full platform here: 22 reads and 25 writes covering campaigns, ad squads, ads, audiences and the Conversions API. One property of Snap's API shaped most of the design decisions, and it is worth knowing before you plan around it.
Snap has no archive state
Most ad platforms let you archive something and change your mind. Snap does not: a delete is permanent. So every delete — campaign, ad squad, ad, segment, and removing users from a customer list — is person-class on every lane, including under auto-approve and including over MCP.
That is not a policy bolted on afterwards. It is the fence the integration was built around, because an approval dialog in front of an irreversible action is the only control that means anything.
What shipped
- 22 reads, 25 writes. Campaigns, ad squads, ads, creatives, audiences, the Conversions API and reporting.
- Creates land paused. Every write reads its target first and is bound to the selected ad account — an ad squad through its campaign, an ad through its ad squad.
- Conversion events validate by default. Sending them live is a separate, person-class decision —
live: trueis not the default and never happens unattended. - Three hosts, kept straight. The Ads API, the Public Profile API and the Conversions API are different hosts with different rules; pagination is only ever followed on the host a page came from.
The landing-URL macros pass through literally
Snap's own URL macros — {{campaign.id}}, {{adSet.name}}, {{ad.id}} and the rest — are text Snap substitutes at serve time, not templates for anything here to resolve. They pass through untouched and are never percent-encoded, because a percent-encoded macro is a broken link that still looks right.
Frequently asked questions
- Can the agent delete a Snapchat campaign on its own?
- No. Snap has no archive state, so a delete is permanent, and every delete is person-class on every lane — including under auto-approve and over MCP. It is proposed with its reasoning and waits.
- Will it send live conversion events?
- Only when you say so. Conversion events validate by default; sending them live is a separate, person-class decision that never happens unattended.
- Are Snapchat budgets in micro-currency here?
- No. Snap's API is micro-currency but every argument and result in these tools is in major units, so a budget reads as 250 rather than 250000000 and never needs dividing again.
- Do new Snapchat campaigns start running?
- No — every create lands paused, and every write reads its target first and is bound to the ad account you selected.