AdWords is now Google Ads. Our new name reflects the full range of advertising options we offer across Search, Display, YouTube, and more. Learn more

Ads
4.6K members online now
4.6K members online now
For questions related to Google Shopping and Merchant Center. Learn to optimize your Shopping ads
Guide Me
star_border
Reply

unit_pricing_base_measure as schema.org property

Visitor ✭ ✭ ✭
# 1
Visitor ✭ ✭ ✭

I am attempting to include a denominator for our unit price in our Google Product Ads. It is much easier for me to be able to specify this in the product details on our site than in our product feed, so I am attempting to use schema.org to specify this. 

 

Both unit_pricing_measure and unit_pricing_base_measure state the schema.org property is Offer.priceSpecification.referenceQuantity, Type: QuantitativeValue

 

I suspect my issue may be that I don't know how to distinguish between these two product data attributes.

 

I have attempting to incorporate this schema property. For example, the price for this product is for 66 pounds:

 

http://www.glasscraftinc.com/home/gla/page_27559_610/9.5mm_x_2mm_chinese_clear_tube.html

 

Using the structured data tool, it seems my data is at least not incorrectly formatted, but I do not see any unit getting picked up to be used in the product ads:

 

https://search.google.com/structured-data/testing-tool/u/0/#url=http%3A%2F%2Fwww.glasscraftinc.com%2...

 

Any idea what I'm missing here?

1 Expert replyverified_user
1 ACCEPTED SOLUTION

Accepted Solutions
Marked as Best Answer.
Solution
Accepted by MosheTLV (Top Contributor)
April

Re: unit_pricing_base_measure as schema.org property

[ Edited ]
Top Contributor
# 2
Top Contributor

yes, the schema.org properties related to per-unit-pricing is:
UnitPriceSpecification -- as opposed to PriceSpecification.

the properties correspond to the unit_pricing_base_measure

and unit_pricing_measure attributes, defined by google, that
may be submitted, in the product inventory (feed) data.

however, both these attributes are mainly for display and policy

purposes, and are otherwise not picked-up, or used by, google

and do not effect the per-unit price related policies for the item

landing-page, or any submitted data.

 

generally, currently, google does not use any structured data

on the website except to verify price and availability, usually

with respect to the optional automatic-item-updates feature,

to temporarily update shopping-ads.

 

google uses additional schema information for local-shopping-ads.

the price in the structured-data on the landing-page, the price displayed
to users, and the price submitted for the physical item-offer being sold
and shipped to the user, must be for the minimum number of products

that the merchant requires a user to purchase.

google may sometimes use unit_pricing_measure/unit_pricing_base_measure
attributes to display per-unit-pricing, in certain, very specific, circumstances or
contexts -- however, there is no guarantee google will use such information,
and does not effect the price or related per-unit/bulk price policies, for any

submitted data or the landing-page.

unit_pricing_base_measure or unit_pricing_measure
do not effect the display of most shopping-ads in most
contexts -- only the price, for the minimum number
of items, that must be purchased by a customer.

 

per-unit-details do not get picked up, or used, in

product/shopping-ads, in most contexts, for most

categories of item-offers -- there are exceptions,

such as food items, or how users search.


if unit_pricing_base_measure or unit_pricing_measure attributes, cannot
be submitted in the primary-feed, and the api is not being used to submit
the data, the best likely course is to use a feed-rule/supplemental-feed.

 

View solution in original post

Marked as Best Answer.
Solution
Accepted by MosheTLV (Top Contributor)
April

Re: unit_pricing_base_measure as schema.org property

[ Edited ]
Top Contributor
# 2
Top Contributor

yes, the schema.org properties related to per-unit-pricing is:
UnitPriceSpecification -- as opposed to PriceSpecification.

the properties correspond to the unit_pricing_base_measure

and unit_pricing_measure attributes, defined by google, that
may be submitted, in the product inventory (feed) data.

however, both these attributes are mainly for display and policy

purposes, and are otherwise not picked-up, or used by, google

and do not effect the per-unit price related policies for the item

landing-page, or any submitted data.

 

generally, currently, google does not use any structured data

on the website except to verify price and availability, usually

with respect to the optional automatic-item-updates feature,

to temporarily update shopping-ads.

 

google uses additional schema information for local-shopping-ads.

the price in the structured-data on the landing-page, the price displayed
to users, and the price submitted for the physical item-offer being sold
and shipped to the user, must be for the minimum number of products

that the merchant requires a user to purchase.

google may sometimes use unit_pricing_measure/unit_pricing_base_measure
attributes to display per-unit-pricing, in certain, very specific, circumstances or
contexts -- however, there is no guarantee google will use such information,
and does not effect the price or related per-unit/bulk price policies, for any

submitted data or the landing-page.

unit_pricing_base_measure or unit_pricing_measure
do not effect the display of most shopping-ads in most
contexts -- only the price, for the minimum number
of items, that must be purchased by a customer.

 

per-unit-details do not get picked up, or used, in

product/shopping-ads, in most contexts, for most

categories of item-offers -- there are exceptions,

such as food items, or how users search.


if unit_pricing_base_measure or unit_pricing_measure attributes, cannot
be submitted in the primary-feed, and the api is not being used to submit
the data, the best likely course is to use a feed-rule/supplemental-feed.