How a product gets created
The agent follows the same path every time, so you always see what you are about to publish before it goes live:- Pick inventory. Choose the ad-server objects to package: ad units, placements, or key-values from your synced inventory.
- Draft. The agent turns your selection into a product draft (name, the inventory it covers, formats, and description) and shows it to you.
- Validate. The agent checks the draft against your ad server and surfaces any problems to fix before publishing.
- Preview. The agent shows what a buyer would see for the product.
- Confirm and create. Creating a product is a durable change, so the agent asks you to approve it explicitly. Once you confirm, the product is created and visible to buyers.
Creating several products at once
When you have a set of products to add, for example a spreadsheet of ad units, you do not have to approve them one by one. The agent validates and previews each draft, then creates the whole set after a single approval.- Drop a spreadsheet into the chat. Attach a CSV or spreadsheet of products and the agent maps the rows into drafts, validates them, and proposes the batch.
- One approval for the batch. You approve the full set once rather than per product.
- It keeps going if one fails. Bulk creation continues on error: if one product can’t be created, the rest still are. At the end you get a clear per-product result showing which products were created and which failed, with the reason, so you can re-run just the ones that need attention.
Updating several products at once
When you need to change a set of products, for example fixing the ones that failed during a batch create or adjusting pricing across a slate, you do not have to approve each edit one at a time. The agent applies all patches after a single approval.- Describe the changes in chat. Tell the agent which products to update and what to change. You can paste a list or describe the edits; the agent maps them to the matching products and shows you what will change before asking for approval.
- One approval for the batch. You approve the full set of updates once rather than per product.
- It keeps going if one fails. Bulk updates continue on error: if one product can’t be updated, the rest still are. At the end you get a clear per-product result showing which products were updated and which failed, with the reason, so you can re-run just the ones that need attention.
Product status
Every product has a status:| Status | Meaning |
|---|---|
draft | Not yet live, not visible to buyers. |
active | Live and discoverable by buyers. |
archived | Taken off the market. Archive a product to stop offering it; make it active again to bring it back. |
active unless you ask for a draft.
Related
Inventory sources overview
How sources sync inventory you can package
GAM access
Connect Google Ad Manager
Source diagnostics
Check sync health before packaging
Storefront onboarding
End-to-end seller setup