| Attribute
Name |
Explanation
|
actor
|
Actor featured in
the video.
Examples:
• Good: Charlie Chaplin
|
age
|
Age of the person. Numeric values
only.
Examples:
• Good: 18
|
agent
|
The name of the
property agent.
Examples:
• Good: Sue Johnson
|
| apparel_type |
The type
of clothing.
Examples:
• Good: Dress
• Good: Socks |
area
|
The size of a piece
of property.
Examples:
• Good: 1000
• Good: 300
• Good: 300 square ft
|
artist
|
Artist that created
the artwork.
Examples:
• Good: Vincent van Gogh
|
author
|
Author of the
information.
Examples:
• Good: John Steinbeck
|
bathrooms
|
Number of
bathrooms. Numeric values
only.
Examples:
• Good: 2
|
bedrooms
|
Number of bedrooms.
Numeric values only.
Examples:
• Good: 3
|
brand
|
The
brand/manufacturer of the product.
Examples:
• Good: IBM
• Bad: IBM - Server
|
calories
|
The amount of calories in a recipe serving.
Examples:
• Good: 280
|
cholesterol
|
The amount of cholesterol in a recipe serving (listed in milligrams).
Examples:
• Good: 130
|
color
|
Color of item.
Examples:
• Good: Black
|
condition
|
Condition of the
item.
Examples:
• Good: new
• Good: used
|
cooking_time
|
The amount of time a recipe requires to be cooked (in minutes).
Examples:
• Good: 50
|
course
|
The part of a meal a recipe belongs to.
Examples:
• Good: main entree
|
course_date_range
|
Dates that a class
is in session, in ISO 8601 format. Format: YYYY-MM-DD or
YYYY-MM-DDThh:mm:ss/YYYY-MM-DDThh:mm:ss
Examples:
• Good: 2006-08-29T00:01:00/2006-12-16T23:59:00
|
course_number
|
ID code associated
with a course.
Examples:
• Good: Bus 172A
|
course_times
|
Time that a class
is in
session.
Examples:
• Good: MWF 12:30-14:00
|
cuisine
|
The style of cooking the recipe falls under.
Examples:
• Good: Italian
|
currency
|
The currency that
your prices are
listed in. Please use the ISO
4217 code. Every item in the bulk upload should use the same
currency.
Examples:
• Good: usd
• Good: gbp
• Bad: US Dollars
• Bad: Pounds |
delivery_notes
|
Additional
instructions to explain the delivery process. Commas are allowed for
this attribute.
Examples:
• Good: Item usually shipped within 24 hours.
|
delivery_radius
|
The distance you
will deliver the
item.
Examples:
• Good: 10
• Good: 10 km
|
description
|
Text describing the
item. We search over this text when matching user queries to your item.
The maximum length for the description is 65536 characters. Commas are allowed for this attribute.
Not Acceptable:
• Extra promotional text or keywords that do not appear on your
web site.
• Boilerplate text (e.g., "We
accept MasterCard & Visa.")
|
education
|
Level of education
required for the job position. Commas are
allowed for this attribute.
Examples:
• Good: PhD
|
employer
|
Company providing
employment. Commas are allowed for this
attribute.
Examples:
• Good: Google, Inc
|
ethnicity
|
Ethnicity of the
person in the
personal entry.
Examples:
• Good: Latino
|
event_date_range
|
Date and time the
event will take
place. This can either be a start date or a date range. Times are based
on the 24 hour clock. If a range of dates are included, separate the start and end dates by a forward slash. Format: YYYY-MM-DDThh:mm or
YYYY-MM-DDThh:mm:ss/YYYY-MM-DDThh:mm:ss
Examples:
• Good: 2006-12-20T23:00
• Good:
2006-12-20T23:00:00/2006-12-21T08:30:00
• Bad: 2006-12-20, 11:00PM
• Bad: Dec.
20, 2006
• Bad: 12-20-2006
• Bad: 20/12/06
|
expiration_date
|
Date that the item
expires. Format: YYYY-MM-DD
Examples:
• Good: 2005-12-20
• Bad: Dec.
20, 2005
• Bad: 12-20-2005
• Bad: 20/12/05
|
fiber
|
The amount of fiber in a recipe serving (listed in grams).
Examples:
• Good: 9
|
format
|
Format of the
content.
Examples:
• Good: DVD
• Good: CD
|
from_location
|
Starting city and
state/country of the trip.
Examples:
• Good: San
Francisco, CA
• Good: Paris, France
• Bad: San Francisco
International Airport
|
gender
|
Gender. We only
accept the following
values: "M," "F," "male," or "female."
Examples:
• Good: M
• Good: female
|
hoa_dues
|
Monthly dues paid
to a homeowners association. If there are no monthly dues, leave this
attribute blank.
Examples:
• Good: 100
|
id
|
Unique alphanumeric
identifier for
each item - e.g., your internal ID code.
IMPORTANT: Once you submit an item with a unique id, this identifier
must not change when you send in a new bulk upload. Each item must
retain the same id in subsequent bulk uploads.
|
image_link
|
URL of an
associated image. Use your full-sized images; do not use thumbnail
images. Up to ten image_links, separated by a comma, can be included
with each item. If you do not have an image available, leave the
attribute blank. Please do not include an image that says "Image not
available."
Not Acceptable:
• Relative URLs (You must include the entire URL)
• Logos
Examples:
• Good: http://example.com/images/1006.jpg
• Good:
http://example.com/i/6.jpg,http://example.com/i/9.jpg
• Bad: /images/1006.jpg
• Bad: example.com/images/1006.jpg
|
immigration_status
|
Legal residency
requirements for this job position.
Examples:
• Good: Permanent Resident
|
interested_in
|
Interests of the
person being profiled.
Examples:
• Good: Long walks on the beach.
|
isbn
|
ISBN
Examples:
• Good: 0821122681
• Good: 082111509x
|
job_function
|
The function of the
job. Commas are allowed for this attribute.
Examples:
• Good: Product Manager
|
job_industry
|
The industry of the
job.
Examples:
• Good: Government
|
job_type
|
Type of position.
Full-time, part-time, contractor, etc.
Examples:
• Good: Contractor
|
label
|
A list of phrases
related to the
item. Up to ten relevant, user-selected labels can be included and will
be used to match your item to queries. An individual label is limited
to 40 characters. Each label will be checked for
compliance. Be sure to include a comma between each label.
Examples:
• Good (events): vip,front row,backstage,Madison Square
Garden,rock,KROCK 101.5,parking passes
• Good (vehicles): leather,power
locks,sunroof,air conditioning,6 speaker,ABS,V6
• Bad: vip front row
backstage
|
language
|
This is the
language that your site is in. Please use the ISO 639
language code. Every item in the bulk upload should use the same
language.
Examples:
• Good: en
• Bad: English
|
link
|
URL of the web page
associated with the item. Enter the fully qualified URL, including the
http://
Acceptable: Tracking URLs
Not Acceptable:
• Higher-level category pages
• Relative URLs
Examples:
• Good: http://www.example.com/asp/sp.asp?id=1030
• Bad: /asp/sp.asp?id=1030
|
listing_type
|
The type of
property listing. Appropriate values are "for sale" and "for rent."
Examples:
• Good: For sale
|
location
|
Location. Can be
formatted as either
an address or latitude and longitude. Addresses should be
formatted: street, city, state, postal code, and country, in that
order. Latitude and Longitude should be formatted: latitude,longitude.
Provide all possible information. Each location element
should be separated by a comma.
Examples:
• Good:1600 Amphitheatre Parkway, Mountain View, CA,
94043,
USA
• Good: Mountain View, CA,
94043
• Good: 37.423130,-122.083706
• Bad: 1600 Amphitheatre Parkway, , CA, USA
• Bad: corner of Market and 2nd, San Francisco, CA
|
main_ingredient
|
The defining component in a recipe.
Examples:
• Good: Tofu
|
make
|
The vehicle
manufacturer.
Examples:
• Good: Mini
|
manufacturer
|
Company that
manufactures the item.
Examples:
• Good: Acme Inc.
|
manufacturer_id
|
Unique product ID
code assigned by
its manufacturer.
Examples:
• Good: 030779A
|
marital_status
|
Marital status of
an individual in a Personals bulk upload entry. For example - single,
divorced, separated, widowed, married, and "in relationship."
Examples:
• Good: single
• Good: widowed
|
meal_type
|
A time or occacion a recipe is normally prepared for.
Examples:
• Good: Breakfast
|
megapixels
|
Resolution of a
digital imaging
device.
Examples:
• Good: 4.3
• Good: 4.3 megapixels
|
memory
|
The amount of
memory included in the
product.
Examples:
• Good: 256
• Good: 256 MB
|
mileage
|
Current mileage of
the vehicle.
Examples:
• Good: 1700
• Good: 1700 km
|
model
|
The vehicle model.
Examples:
• Good: Mini Cooper S
|
model_number
|
Model number of the
product.
Examples:
• Good: 1924863
|
name_of_item_reviewed
|
The name of the
item being reviewed. Commas are allowed for
this attribute.
Examples:
• Good: Google Mini
|
news_source
|
The source of news.
Examples:
• Good: Journal
|
occupation
|
Industry the person
is employed in.
Examples:
• Good: Sales
|
pages
|
The number of pages
in the publication. Numeric values only.
Examples:
• Good: 18
|
payment_accepted
|
Please include at
least one of the
following payment methods: "Cash," "Check," "GoogleCheckout," "Visa," "MasterCard,"
"AmericanExpress," "Discover," or "WireTransfer." If you
accept more than one method, separate each method with a comma.
Examples:
• Good: Cash
• Good: Cash,Check
• Bad: Cash Check Visa
NOTE: The "GoogleCheckout" payment option can only be specified if you meet all of the following requirements:
- You are selling a product or vehicle.
- You have registered for a Checkout account.
- Price values are included in each of your item details.
- The price value is between $1.00 and $1999.95.
- Quantity values are included in each of your item details.
|
payment_notes
|
Additional
instructions to explain your payment policies. Commas
are allowed for this attribute.
Examples:
• Good: Cash only for local orders.
|
pickup
|
Information about
whether or not an
item is available for pickup. Acceptable values are "true" (1) and "false" (0).
Examples:
• Good: true
• Bad: only on Tuesdays
|
preparation_time
|
The amount of time a recipe takes to be prepared (in minutes).
Examples:
• Good: 70
|
price
|
Prices can be a
single price or blank if not applicable.
Not Acceptable:
• Using commas instead of decimals
Examples:
• Good: 5.95
• Bad: 5,95 (This is the same as entering 595
as the price)
• Bad: 5.00 - 10.00
• Bad: 1000 or best offer
• Bad: free
|
price_type
|
The type of pricing
for the item. We
only accept the following values: "negotiable" or "starting." The
default is "starting."
Examples:
• Good: negotiable
• Bad: 100 OBO
|
processor_speed
|
The processor speed
for the product.
Examples:
• Good: 1500
• Good: 1500 MHz
|
product_type
|
The type of product
being offered.
Toys, books, flowers, etc.
Examples:
• Good: electronics
|
property_type
|
Type of property:
house, apartment,
condominium, etc.
Examples:
• Good: mobile home
|
protein
|
The amount of protein in a recipe serving (listed in grams).
Examples:
• Good: 25
|
publication_name
|
Name of the
publication.
Examples:
• Good: Journal of Appropriate Technology
|
publication_volume
|
Volume of the
publication.
Examples:
• Good: XIV
|
publish_date
|
Date published.
Format: YYYY-MM-DD
Examples:
• Good: 2005-12-20
• Bad: Dec.
20, 2005
• Bad: 12-20-2005
• Bad: 20/12/05
|
quantity
|
Numeric value that
represents the
number of units in stock. This attribute can be left blank if you have
a large quantity or if it is not applicable.
Examples:
• Good: 18
• Good: 0
• Bad: out of stock
|
rating
|
Rating of the
product or service on a scale of 1-5, with 5 as the best. Numeric
values only.
Examples:
• Good: 4
• Bad: superb service
|
review_type
|
The category of the
item being
reviewed.
Examples:
• Good: restaurant
• Good: toy
• Good: truck
|
reviewer_type
|
The type of rating
being provided:
"editorial" (A review written by a member of your staff) or "user" (A
review written by a user of your site).
Examples:
• Good: editorial
• Good: user
|
salary
|
Salary for this
position.
Examples:
• Good: 50000
• Bad: 50000-55000
|
salary_type
|
The type of salary
included. We only
accept the following values: "negotiable" or "starting." The default is
"starting."
Examples:
• Good: negotiable
• Bad: 50000-55000
|
saturated_fat
|
The amount of fat in a recipe serving (listed in grams).
Examples:
• Good: 3
|
school_district
|
The school district
the property is
in.
Examples:
• Good: Union School
District
|
service_type
|
The type of service
being offered. Web hosting, legal, gardening, etc.
Examples:
• Good: consulting
|
servings
|
The total number of helpings in finished recipe.
Examples:
• Good: 6
|
sexual_orientation
|
Sexual orientation.
Examples
• Good: straight
• Good: gay
|
shipping
|
Shipping options
available for an item. Format:
shipTo_country:shipping_service:shipping_price,shipTo_country:shipping_service:shipping_price.
- "ShipTo_country" is a country your product ships to.
Use ISO
3166 country codes.
- "Shipping_service" is the delivery speed for the
shipment.
- "Shipping_price" is the numeric price of delivery.
If you choose to exclude a sub-attribute, you must still include two
colons per shipping option.
Examples:
• Good: US:Overnight:35.95,GB:Overnight:65.95
• Good: US:Ground:5.95
|
size
|
Dimensions of the
item, expressed in
either two or three dimensions.
Examples:
• Good: 12x10x4
• Good: 12x10
|
sodium
|
The amount of sodium in a recipe serving (listed in milligrams).
Examples:
• Good: 1010
|
subject
|
Topic of study for
a course.
Examples:
• Good: Financial Institutions
|
tax_percent
|
The tax rate for an
item. This should
be numeric values excluding a percent sign.
Examples:
• Good: 8.25
• Bad: 8.25%
• Bad: .0825
|
tax_region
|
Region that the
item is being taxed in.
Example:
• Good: Santa Clara
|
title
|
The name or title.
Maximum of 80
characters. Commas are allowed for this
attribute. |
to_location
|
Destination city
and state/country of the trip.
Examples:
• Good: San
Francisco, CA
• Good: Paris, France
• Bad: San Francisco
International Airport
|
total_carbs
|
The amount of carbohydrates in a recipe serving (listed in grams)
Examples:
• Good: 22
|
total_fat
|
The amount of fat in a recipe serving (listed in grams).
Examples:
• Good: 8
|
travel_date_range
|
Date and time of
the trip. This can
either be a start date or a date range. Times are based on the 24 hour
clock. If a range of dates are included, separate the start and end dates by a forward slash. For flights, list each segment as a separate item.
Format: YYYY-MM-DDThh:mm or YYYY-MM-DDThh:mm:ss/YYYY-MM-DDThh:mm:ss
Examples:
• Good: 2006-12-20T23:00:00
• Good:
2006-12-20T23:00:00/2006-12-21T08:30:00
• Bad: 2006-12-20,11:00PM
• Bad: Dec.
20, 2005
• Bad: 12-20-2006
• Bad: 20/12/06
|
UPC
|
Universal Product
Code.
|
university
|
The name of the
institution a class
is offered in. Commas are allowed for this
attribute.
Examples:
• Good: Stanford
• Good: Alpha Technical Institute
|
url_of_item_reviewed
|
The URL of an
informational page related to the item. Enter the fully qualified URL,
including the http://
Not Acceptable:
• Higher-level category pages
• Relative URLs
Examples:
• Good: http://www.example.com/item1.html
• Bad: item1.html
|
vehicle_type
|
The type of
vehicle. Car, motorcycle,
scooter, etc.
Examples:
• Good: truck
|
vin
|
Vehicle Identification Number.
Examples:
• Good: 1M8GDM9AXKP042788
|
weight
|
Weight of an item.
Examples:
• Good: 5
|
year
|
The four digit
model year or year built.
Examples:
• Good: 1979
• Bad: 79
• Bad: 26
|
[custom
attribute]
|
Custom attributes allow you to include
additional information about your item. You can include an unlimited
number of custom attributes with types. To define a custom attribute,
you must start the attribute with a c: (example - If you would like to
define an attribute called cooking_ingredients, the attribute in the
header column should be called c:cooking_ingredients.) You must use
underscores ( _ ) to denote spaces. You may also include typing
information based on your custom attribute. Example:
c:cooking_ingredient:string lets us know that the custom attribute
"c:cooking_ingredients" has the value "string."
Examples of typed attributes you may
submit are -
- Brand of your product - Header -
c:brand:string
- Event Date of your Street Fair -
Header - c:event_date:dateTime
The following types are supported.
| Type |
Description |
Header Column |
Values |
string
|
Any string
|
c:brand:string
|
sony
|
integer
|
Number without a decimal point.
|
c:revenue:integer
|
32000000
|
decimal
|
Number with a decimal point.
|
c:megapixels:decimal
|
4.3
|
dateTime
|
Date Time Range -
YYYY-MM-DDThh:mm:ss/YYYY-MM-DDThh:mm:ss
|
c:event_date:datetime
|
1974-09-25
|
location
|
Location
|
c:job_location:location
|
921 W.
Dana Street, Mtn View - 94103
|
URL
|
HTTP URL
|
c:rating_url:url
|
http://www.google.com
|
boolean
|
Value may be either Yes/No or
True/False
|
c:promo_offer:boolean
|
Yes or No
|
|
