Supply Chain
Part of Creative management technology
Mapping a product feed into dynamic ad templates
Map item IDs, images, copy, prices and destinations into dynamic ad templates, then validate variants, defaults and publication.
Map each approved feed field to a named dynamic template element, then check that the item identifier, displayed offer and destination refer to the same product or variant. Validate representative rows, defaults and every required ad size before importing the full catalogue.
Define the field mapping
| Source field | Creative use | Validation question |
|---|---|---|
| Item ID | Connects an item to an event or selection rule | Does it match the chosen platform's expected identifier? |
| Title | Visible product text | Does it fit every required size? |
| Image reference | Product image | Can the platform retrieve and render it? |
| Destination | Click-through page | Does it show the matching product or variant? |
| Price and availability | Offer text or eligibility | Do they agree with the destination page? |
This is a planning schema, not a universal feed specification. Required identifiers and reporting fields vary by platform, so check the relevant feed documentation.
Facebook product feed fields include id, title, description, availability, condition, price, link, image_link, brand, MPN, GTIN, google_product_category and fb_product_category. Google Shopping product feed guidance names id and title as mandatory attributes, so do not treat one platform's fields as another's schema.
A separate column is needed for each dynamic element; examples include headline text, an image URL and an exit URL. Assess title, image_link and link against those elements respectively, and confirm that the chosen platform accepts the mapping.
Check how the platform handles images and blank image cells in its feed documentation. Google Ads dynamic remarketing uses a separate feed model, so follow its feed guidance; do not assume an identifier from one dynamic-creative platform is interchangeable with an identifier from another.
Platform-specific product feed requirements for dynamic ads in Australia
- Mandatory fields (Google Shopping)
- id, title
- Mandatory fields (Facebook)
- id, title, image_link, link, price, availability
- Supported image formats (Google Ads)
- JPEG, PNG, WebP
- Image handling (Google Studio)
- Blank cells may cause creative failure; use fallback images
- Identifier type (dynamic remarketing)
- Item ID must match event or selection rule identifier
Check a representative row
Consider a fictional Australian homewares shop advertising a blue lamp. Its approved row has an item ID, title, image, AUD price and destination for the blue variant. Map the title, image and destination to the relevant creative elements. Test a long title, a different variant and an unavailable item.
Record the chosen platform's identifier field in the row; id is one named Facebook product-feed field. Compare the value with the identifier used by the event or selection rule, and confirm that the resulting match is the intended product or variant.
Decide what happens when an image is missing, a price changes or an item is no longer eligible. Remove or suppress an ineligible row according to the campaign's rules, or use an approved generic message. Do not carry an old price into a fallback.
For Merchant Center products, check Google's landing page requirements and price guidance. These are Merchant Center requirements, not rules for every dynamic-creative platform.
Key metrics for dynamic ad feed performance in Australia
- Image missing handling
- Use approved generic message or suppress row
- Price change impact
- Update feed immediately; avoid carrying old prices
- Destination URL validity
- Must show matching product or variant
- Default fallback usage
- Only when no valid match is found
- Merchant Center landing page compliance
- Required for Google Shopping; not universal
Validate before release
Check the chosen platform's actual schema, supported image formats and field limits. In Google Studio, preview dynamic creatives to check how feed variations appear. Include a valid match, a default and each required size.
Record the feed snapshot, template version, mapping, destination checks and approved profile. For Google Studio content updates, follow the platform's documented update process.
Check how feed-column or creative-asset changes affect a live creative, then confirm the published state after the update.
Validating a product feed before dynamic ad release
- Check platform schema and field limitsConfirm supported fields, character limits, and data types
- Preview dynamic creatives in Google StudioTest valid match, default, and all required sizes
- Record feed snapshot and mapping detailsDocument version, template, destination checks, and profile
- Verify live creative after updateCheck how changes affect published content
