Set up a paid-media client, account, data-source, privacy, and mutation-guardrail profile for Claude Ads. Use for onboarding, initial configuration, API tokens or credential profiles, environment-variable or keychain setup, connecting exports or read adapters, safe native or verified-local installation, curl-pipe-bash install requests, declaring KPIs, or preparing a new advertising project.
Read the main ads contract. Website-derived brand profiles belong to ads-dna.
Collect business model, offer, geography, regulated categories, objective,
conversion taxonomy, economics, active platforms, account IDs, date/time
conventions, and reporting audience.
Record data-source type and whether required credentials are present, but never
store credential values, cookies, tokens, customer lists, or raw exports.
Create and validate data-lifecycle.json before persisting the setup profile.
Declare classification; explicit minimum retention and purpose-bound deletion
deadline or documented exception; verified at-rest/in-transit controls and
evidence; access owner and roles; deletion method and verification; and private
incident owner/channel. This is an operational contract, not legal advice or a
claim of regulatory compliance.
Declare mutation authority, approvers, budget/policy ceilings, and rollback owner.
Validate the profile and write it atomically beneath the project's Claude Ads
state directory.
