Product Ads

Product Ads allow you to promote your products and offers in Native search campaigns. In order to run product ad campaigns, you must first share your product catalog with Verizon Media Native. Contact your Verizon Media representative for details.

Products are provided through a product feed. Products contain info such as itemId, category, brand, condition and price. Products automatically expire in Native if they have not been updated in the last 30 days. This information is managed through your product feed.

You can manage which products are promoted in a Shopping campaign by creating one or more Product Filters. If no Product Filters are set, all products will be promoted in the campaign. Every product has a CPC bid associated with it at either the Product Group level, or at the Ad Group level if no Product Groups are defined. Product Ads are created with a Campaign Objective = Shopping.

  • New Campaign Objective for Product Ads: For Product Ads campaigns, set Campaign Objective=Shopping to promote your offers in Native search campaigns

  • New Objects for Product Ads
    • Product Filter

    • Product Group

    • Tracking Template

Product Filters

A Product Filter is associated with a campaign. You can use product Filters to describe the set of products that participate in a Shopping campaign. If no Product filters are set, all the products will be promoted in the campaign.

You can set a product filter using one of the following set of fields from the product feed:

  • ITEM_ID

  • BRAND

  • CONDITION

  • CATEGORY_L1,CATEGORY_L2,CATEGORY_L3,CATEGORY_L4,CATEGORY_L5

  • PRODUCT_TYPE_L1, PRODUCT_TYPE_L2, PRODUCT_TYPE_L3, PRODUCT_TYPE_L4, PRODUCT_TYPE_L5

  • CUSTOM_LABEL_0, CUSTOM_LABEL_1, CUSTOM_LABEL_2, CUSTOM_LABEL_3, CUSTOM_LABEL_4

  • RETAILER

Note

Google shopping campaign exported files do not have product filters. If you want to filter out certain products, this needs to be done via Native bulk file.

You can create up to seven product filters per campaign.

Fields

The following are the minimum required set of fields for creating and managing a product filter. Other fields required to create a campaign may still apply.

Name

Description

Type

Add

Update/Delete

Campaign ID

ID of the parent campaign for which the product filter is being created.

long

Required if campaign already exists

required

Campaign

The name of the parent campaign.

string

Required if the product filter is being created as part of a new campaign.

optional

Product Filter

The product filter value.

string

required

optional

Object ID

ID of the parent campaign for which the product filter is being created.

long

N/A

required

Status

ID of the parent campaign for which the product filter is being created.

enum

optional

optional

Create Product Filters

The examples below illustrate how to add a product filter.

Action

Object Type

Campaign ID

Object ID

Product Filter

Status

ADD

Product Filter

1

Category_L1=’Software’

Active

ADD

Product Filter

1

Brand=’Yahoo’

Active

Update Product Filter

The examples below illustrate how to update the status and product value of a product filter.

Action

Object Type

Campaign ID

Object ID

Product Filter

Status

UPDATE

Product Filter

1

134567222

Category_L1=’Software’

Paused

UPDATE

Product Filter

1

156000992

Brand=’NewYahoo’

Active

Delete Product Filter

The examples below illustrate how to delete a product filter.

Action

Object Type

Campaign ID

Object ID

Product Filter

Status

DELETE

Product Filter

1

156000992

Brand=’NewYahoo’

Active

Product Group

A Product Group is associated with an ad group. A Product Group allows you to partition your inventory along multiple dimensions and set bids for each partition. Only the Product Groups that match the campaign’s Product Filter criteria will be honored. If Product Group bids are not set for an ad group, then the ad group level bid will be honored.

A product group can be set using one or more of the following set of fields from the product feed

  • ITEM_ID

  • BRAND

  • CONDITION

  • CATEGORY_L1,CATEGORY_L2,CATEGORY_L3,CATEGORY_L4,CATEGORY_L5

  • PRODUCT_TYPE_L1, PRODUCT_TYPE_L2, PRODUCT_TYPE_L3, PRODUCT_TYPE_L4, PRODUCT_TYPE_L5

  • CUSTOM_LABEL_0, CUSTOM_LABEL_1, CUSTOM_LABEL_2, CUSTOM_LABEL_3, CUSTOM_LABEL_4

  • RETAILER

You can partition your inventory by effectively managing nodes and building a tree. There are three types of nodes:

  • Root - the top of the tree

  • Parent - used to partition your inventory

  • Leaf - contains a bid and represents a biddable product group

The following are the minimum required set of fields for creating and managing a product group. Other fields required to create an ad group may still apply.

Name

Description

Type

Add

Update/Delete

Ad Group ID

ID of the parent ad group for which the product group is being created.

long

Required if the ad group already exists

required

Ad Group

The name of the parent ad group.

string

Required if product group is being created as part of a new ad group

optional

Product Group

The product group value. This will typically be setup as a hierarchical attribute. Specify the full path of the hierarchical value. Only the Product Groups that match the campaign’s Product Filter criteria will be honored. You may use * / CUSTOM_LABEL_0=123 to define a Product Group object which narrows down product items to those with 123 as the value of custom label 0. Optional. If not set, it is assumed the node is the catch-all Other group.

string

optional

optional

Object ID

ID for the product group.

long

N/A

required

Search CPC

CPC Bid for the Product Group in the currency of your account. The minimum accepted CPC bid is $0.05. If not set, will default to the Ad Group Bid.

decimal

optional

optional

Tracking Template

Used for tracking Product Ad URLs. This can be defined at campaign, product group or ad group level.

string

optional

optional

Status

Valid values are:

  • Active

  • Paused

This value will default to Active if no status is provided upon creation.

enum

optional

optional


Important

You are not allowed to set the Parent ID. If you specify the Parent ID in the Bulk Upload, it will be ignored. The Product Group Parent ID field will be populated in the Bulk Download and Upload result file.

For multilevel product groups (under the same Adgroup), the Parent ID of the product group id 3 is 2 and Parent ID of id 2 is 1. The product group of id 1 is the root, so it doesn’t have a Parent ID.

id

ad group id

product group

product group parent id

1

1

/

2

1

/product_group_a

1

3

1

/product_group_a/product_group_b

2

Create Product Group

The examples below illustrate how to add a product group.

Product groups can be created while creating an ad group, or separately for an existing ad group. You can also add a product group line to an existing product group

The example below shows how to add new product group with ad group creation.

Action

Object Type

Ad Group ID

Object ID

Search CPC

Tracking Template

Product Group

Ad Group Status

Status

ADD

Ad Group

0.1

Active

ADD

Product Group

*/

Active

ADD

Product Group

http://trackingurl.com

  • / Cat_L1=’IT Companies’ /

Active

ADD

Product Group

0.99

  • / Cat_L1=’IT Companies’ / Brand = ‘Google’

Active

The example below shows how to add new product group in a new file without ad group creation (and no existing product groups).

Action

Object Type

Ad Group ID

Object ID

Search CPC

Product Group

Tracking Template

Status

ADD

Product Group

1

*/

Active

ADD

Product Group

1

** / Cat_L1=’IT Companies’ /

Active

ADD

Product Group

1

0.88

  • / Cat_L1=’IT Companies’ / Brand = ‘Yahoo’

Active

Note

There cannot be any existing offer groups for ad group id 1. The user needs to specify the ad group id for each column. Otherwise, there will be error thrown (cannot create same node)

The example below shows how to add additional product groups in a new file without ad group creation (and with existing product groups).

Action

Object Type

Ad Group ID

Object ID

Search CPC

Product Group

Tracking Template

Status

ADD

Product Group

1

11

*/

Active

ADD

Product Group

1

** / Cat_L1=’IT Companies’ /

Active

ADD

Product Group

1

0.88

  • / Cat_L1=’IT Companies’ / Brand = ‘Yahoo’

Active

Note

The user needs to specify all existing node IDs (except leaf nodes) in the first place (for example, object id for root node */ in this case). Otherwise, there will be error thrown, saying no parent ID found. The above example gives the existing root node ID 11, and then two new nodes are created (Cat_L1 & Brand).

Update Product Group

The examples below illustrate how to update a product group for bid and attribute value.

Action

Object Type

Ad Group ID

Object ID

Search CPC

Product Group

Status

UPDATE

Product Group

1

14141223

0.89

  • / Cat_L1=’IT Companies’ / Brand=’NewYahoo’

Active

Note

Only object ID is honored. The offer group field is optional. Only the last attributeType=attributeValue pair is honored for updating the node. The user can put either of the following product group expressions: - / Cat_L1=’IT Companies’ / Brand = ‘NewYahoo’, - Cat_L1=’IT Companies’ / Brand = ‘NewYahoo’, - Brand = ‘NewYahoo’, - anything / Brand = ‘NewYahoo’

Delete Product Group

The examples below illustrate how to delete the product group node..

Action

Object Type

Ad Group ID

Object ID

Search CPC

Product Group

Status

DELETE

Product Group

1

141412232

0.89

  • / Cat_L1=’IT Companies’ / Brand=’NewYahoo’

Active

Note

Only the object ID is honored. The product group field is optional.

Native Product Ads vs Google Shopping

Please be aware that Native Shopping campaigns are different from Google Shopping campaigns. Google shopping campaigns are supported ONLY for the initial import. The ongoing campaign management via bulk file are supported only in Native format.

The key differences are the following:

  • Google Shopping campaign exports doesn’t have “Product Filter”, “Tracking Template” and campaign priority setting.

  • Category and Product Type product filters are defined using different names. Native names have explicit level information. For example, a product group is defined as * / Category=’Apparel & Accessories’ / Category=’Clothing’ / in Google Shopping campaigns.

  • The equivalent in Native Shopping campaigns needs to be defined as * / CATEGORY_L1=’Apparel & Accessories’ / CATEGORY_L2=’Clothing’ /.