Channel Fields and Placeholders

The Fields tab maps each feed column to product data, AI content or static text. This article covers building a field's value, fallbacks, the "Require content for this placeholder" toggle and nested blocks.

Updated November 6, 2026

A field is one column in your channel's output, such as g:title, image_link or video/url. You build each field's value on the channel's Fields tab. Field changes save to a draft, and the live feed changes when you publish.

Destinations expect specific names and value formats, so a field's name must match the destination's specification:

What a field is#

Each row on the Fields tab has:

  • A type icon: Text, Image, Video or Voice over (audio), the same types as Studio placeholders. A fifth type, Nested block, writes a block of child elements. A channel's Voice over field is always spoken by a Google voice in the catalog's language; you can only choose a voice on Studio audio elements.
  • A field name: this goes into the exported feed, so spell it the way the destination does.
  • Field content: the same placeholder editor as in Studio templates.
  • Allow multiple values: a switch that lets a field repeat, up to 10 values per product, for elements that accept several entries, like additional_image_link.

A channel may hold several fields with the same name, as Meta's image blocks do. The order they appear in is what the destination reads as their position. They're numbered on screen, as in image · #1, and the number never reaches the feed.

Adding a field#

Click Add field in the last row of the fields table and give it a name and a type. The field starts empty. You can change the type later with Change type in the field's menu, which keeps the content and changes which content elements it offers. A nested block is the exception, because it's chosen at creation.

Building field content#

Click into a field's content editor to build its value:

  1. Type static text directly, or
  2. Use the dropdown (down-arrow) to insert a content element: AI-written ad copy, review quotes, product data like price or ID, or a templated image or video. See Available placeholders. An archived template can't be added to a channel; unarchive it on the Templates page to use it. A channel that already uses it keeps working.
  3. Chain a fallback after it. A fallback is only used if everything before it resolves empty, so a chain like "AI headline, then product title, then static text" always produces a value.

A price, a discount or an average review score you insert comes with a Format number step: its usual decimals (two for a price), a . (dot) as the decimal separator and none as the thousands separator, because destinations read the number themselves. Click the chip if your destination asks for another format. The step works as described in Placeholders, except that here its separators are set rather than left on the catalog's language.

Other steps, such as Replace, Trim whitespace, Build text and Split, are on the same "+ Add step" menu. See Steps: changing a value before it is used.

Several fields a new channel starts with are already built this way. The condition field, for example, uses your catalog's condition value and falls back to new where that value is missing or blank.

Require content for this placeholder#

Click a content-element chip in a field's editor to open its settings. With no fallback chained after it, the element has a "Require content for this placeholder" toggle:

  • On: if the element can't resolve a value, the field counts as missing content. The built-in Status rule and the channel's Activity tab react to that, for example by archiving the product or raising a warning.
  • Off: if the product doesn't have this content, the field is left empty and doesn't count as missing content. Use this for an optional field that many products don't have.

If a fallback is chained after the element, the toggle reads "Fallback to the next placeholder if this content is missing" instead. It works the same way.

Deleting a field#

The delete button is disabled, with a tooltip saying why, if a channel rule uses the field in a condition or an action. Remove or repoint the rule first.

Nested blocks#

Most feed columns carry one value. Some carry a block of child elements instead: Google's grouped attributes like g:product_detail and g:question_and_answer, and Meta's image block, which pairs an image URL with the tags that name it.

Pick Nested block as the type when you create the field. The row shows a nested chip, with one row per sub-field under it: a name (lowercase letters, numbers and underscores) and its own placeholder expression. Add sub-field asks for a name and a type, and the type decides which content elements the sub-field offers. Each sub-field's own menu has Remove sub-field.

  • Sub-field names may repeat. Two sub-fields named tag write two <tag> children, which is how one block carries several tags.
  • A sub-field with "Require content for this placeholder" off is left out of its block when it has no value. With it on, the whole block is left out for that product and the product counts as missing content.
  • A sub-field can't be a nested block itself.
  • A block can carry at most one image or video sub-field, so an image design and a video design are two separate nested fields.
  • You can change a sub-field's type from its menu, and what you built stays. An option that doesn't fit is disabled, and says why.
  • The type is what makes a sub-field the block's image or video. A Text sub-field that points at an image is text holding a link.
  • Changing a design's image or video to Text or Voice over takes it out of Adaptive designs and Renable Options, so Renable asks first. The feed still sends the block, and changing the type back restores the design.

A channel rule can replace a nested field's whole block for the products it matches, but a condition can't read one. If the field stops being a nested field, the rule stops working and the channel warns you.

Repeating a block#

Turn on Allow multiple values on a nested field and the block repeats, one block per item of a list, up to Max blocks. This is how a Q&A or attributes column writes one block per question or attribute. With the switch off, the field writes one block per product.

Repeating needs a sub-field bound to a list, such as Product attribute name, and all repeating sub-fields must read the same list. CSV and TSV can't carry a repeating block, so switch the channel to XML or JSON on the Settings tab. A single nested block works on every format. When the switch is unavailable, the row says why.

Design blocks#

Meta's image and video blocks have their own screen, the Adaptive designs dialog, which builds and names them for you. On a channel using them, they collapse into one Adaptive designs row, and Show raw fields on that row expands them. See Adaptive designs.

Changing your mind#

To un-nest a field, delete it and add it again as the type you want.

Where to go next#