Create Campaign

You can automate Meta campaign provisioning by defining campaigns in a declarative YAML config. The workflow maintains idempotent state via an admanage-state file, skipping existing entries during execution to prevent duplicates.

Yes, you can test Meta ads creation safely using a built-in dry-run mode. This feature performs pre-flight validation and queues payloads locally in a pending directory without triggering actual Meta API calls.

The best way to manage paused-by-default Meta campaigns is using a declarative YAML config. The automation reads this config to queue new campaigns and ad sets, ensuring they remain paused until a postprocess step activates them.

Postprocess execution handles the actual Meta API calls for queued ad sets. After execution, it writes the final generated IDs back to the state file and notifies operators, enabling downstream scheduling and activation.

A declarative workflow skips campaigns during ad creation to enforce idempotent behavior. It checks a local state file for existing entries and proactively skips them to prevent duplicate campaigns and ad sets.

Yes, you need a separate postprocess step to finalize Meta campaign creation. The initial execution only validates inputs and queues payloads locally, deferring actual API calls to this subsequent postprocess execution phase.