included_destination [included_destination]: Definition

Use the included_destination [included_destination] attribute to control the type of ads that your products participate in. For example, you could use this attribute if you want a certain brand of product to appear in a dynamic remarketing Display ads campaign, but not in a Shopping ads campaign. 

When to use

Optional for each product

If you want your product to only appear in certain types of ads, use the included_destination [included_destination] attribute.

Supported values:


Follow these formatting guidelines to make sure that we understand the data that you're submitting. 

Supported values

Shopping ads, Shopping Actions, Display ads, Surfaces across Google

Repeated field Yes
File format Example value
Text feeds

Display ads

XML feeds <g:included_destination>Display ads</g:included_destination>

Repeated fields


To submit multiple destinations that you would like to include, submit the attribute multiple times, once for each destination (recommended). For example:

Product Orthopaedic dog bed
title [title] XXL Orthopaedic Dog Bed
included_destination [included_destination] Display ads
included_destination [included_destination] Shopping ads
included_destination [included_destination] Shopping Actions

You can also separate each destination with a comma (,):

Display ads,Shopping ads,Shopping Actions


To submit multiple destinations to include for an XML feed, include a separate attribute for each included destination:

<g:included_destination>Display ads</g:included_destination>
<g:included_destination>Shopping ads</g:included_destination>
<g:included_destination>Shopping Actions</g:included_destination>

For format API information, please see Content API for Shopping.


Follow these guidelines to make sure that you submit high-quality data for your products.

  • If you submit conflicting information for the excluded_destination [excluded_destination] and included_destination [included_destination] attributes, the excluded_destination [excluded_destination] value will always take precedence over the included_destination [included_destination] value.
Was this helpful?
How can we improve it?

Need more help?

Sign in for additional support options to quickly solve your issue