A delivery is a zip file with the approved ads of a batch, ready to put into an advertising platform. You download it on the batch page with Download delivery. It only works once the batch has been reviewed and everything that was not yet reviewed has been signed.
What is in it
- The images. Only ads that passed the brand gate and were approved. What the gate blocked or you rejected does not go along.
- A manifest. Per image the file name, the key, a checksum, the dimensions, placement, language, angle, the texts, the gate result, the origin (made by AI or not) and whether it must be disclosed. Advertising platforms strip metadata from a file on upload; the manifest is the dossier that remains.
- A sheet of ads. A starting point with the columns we can fill honestly. It is not a Meta template: that changes and differs per objective. Fetch the current template there and copy the columns over.
- A read-me with what is not in it. There is no C2PA manifest and the disclosure flag is calculated, not checked by a lawyer.
The file name is the key: the same text is in the ad name and in utm_content, so afterwards you know which of fifty creatives did it.
When it cannot be done
If a new version appeared after your review, it says that one has to be reviewed again. In a trial workspace a delivery is closed: it is an export, and a trial takes nothing along in full quality.
Via MCP and the director
An agent can ask for the address of the delivery of a batch with creative_delivery. It gives only the address; downloading needs access to the workspace and follows the same rules as on the screen, including for a trial. An agent cannot deliver in the sense of sending or publishing: a delivery goes nowhere until a human takes the file themselves. What goes in a delivery is decided by the review, and that is a proposal that a human signs (see Reviewing a batch).