The vehicle fulfillment [vehicle_fulfillment] attribute is used to detail the method by which the vehicle will be delivered to the customer. This group attribute is used with the store code [store_code] sub-attribute for in store fulfillment. Store code [store_code] isn't required for online offers.
The vehicle fulfillment [vehicle_fulfillment] attribute can be repeated up to 3 times for each offer, allowing dealers to specify an option for each fulfillment type.
On this page
When to use
Note: Online vehicle fulfillment is currently a beta feature. It is reserved exclusively for advertisers who are:
- Promoting build-to-order offers (learn more About build-to-order vehicle ads).
- Possess the capacity to provide national delivery of vehicles
If you meet these criteria and would like to request access, you can apply here for participation.
Required for Online vehicle offers (where option
[option] is set to online [online]).
Optional for In-store vehicle offers if you provide the location using the top-level store code
[store_code] attribute instead.
Format
Follow these formatting guidelines to make sure Google understands the data you submit. Learn when and how to submit your product data.
| Formatting specifications | |
|---|---|
| Technical name | vehicle_fulfillment |
| Type | Unicode characters (Recommended: ASCII only) |
| Sub-attributes |
This attribute uses the following sub-attributes:
The option
|
| Limits |
For store codes, 64. For vehicle fulfillment, in store, up to 500 store codes are supported, delimited by a colon ( : ). |
| Repeated field | Yes, up to 3 times, once per option type. |
| Schema.org property (Whatâs this?) | No |
File format examples
To ensure your attribute is recognized correctly, use the formatting specific to your data source type.
| Data source format | Examples |
| Text (TSV or CSV) data sources | in_store:1111 |
| XML data sources |
|
| Merchant API | To format your data for Merchant API, go to the Vehicle ads Merchant API guidelines. |
Minimum requirements
These are the requirements you'll need to meet to show your product. If you don't follow these requirements, we'll disapprove your product and let you know in your Merchant Center account.
- If the method for vehicle fulfillment is the in store
[in_store]attribute, then the store code[store_code]sub-attribute must also be submitted along with one or more appropriate store code values. - If you are specifying more than one store code value, then repeat
:store_codein the header for each store code, up to the specified maximum.
:" is still required for each store code mentioned in the header.Best practices
These best practices can help you go beyond the basic requirements to optimize your product data for performance.
- Choose the simplest method for in-store offers. Either the vehicle fulfillment
[vehicle_fulfillment]attribute (withoptionset toin_store) or the top-level store code[store_code]attribute is required for in-store (local) ad targeting. You do not need to provide both attributes. - If only a single store code will be associated with a given vehicle, the store code
[store_code]attribute may be a simpler approach. View the âVehicle fulfillment vs. store codeâ examples section below for illustration.
Examples
Submitting the vehicle_fulfillment group attribute
| Group attribute | vehicle_fulfillment |
| Sub-attributes |
|
Text data source
Format the group attribute name using vehicle_fulfillment, and then in parentheses, adding one of the supported fulfillment values followed by store_code (as needed). The store_code sub-attribute needs to be repeated for each store code value you want to submit, separated by a colon ( : ).
Example: In store fulfillment
If the store_code sub-attribute is repeated in the group attribute name, but only one store code value is submitted, the entry will still be accepted since thereâs only one colon in the value.
When a colon ( : ) doesn't indicate a separate sub-attribute value, the value should be surrounded by quotes ( " ).
| Name | vehicle_fulfillment(option:store_code:store_code) |
| Values |
|
Example: Online fulfillment
The store_code sub-attribute isn't required for online offers.
| Name | vehicle_fulfillment(option) |
| Value | online |
Example: Hybrid offer
A hybrid offer combines both of the above examples as separate columns in the data.
{other data source cols} |
vehicle_fulfillment(option) |
|
| ... | online |
in_store:1111:2222 |
Google Sheets
Format the group attribute name the same way as with text data source. When a colon ( : ) isn't used to separate sub-attribute values, it should be submitted with a preceding backslash ( â \ â ).
| Name | vehicle_fulfillment(option:store_code:store_code) |
| Values |
|
XML data source
Include the store_code sub-attribute as needed. To specify different fulfillment options, submit multiple vehicle_fulfillment attributes and include the store_code sub-attribute.
Example
<g:vehicle_fulfillment>
<g:option>online</g:option>
</g:vehicle_fulfillment>
<g:vehicle_fulfillment>
<g:option>in_store</g:option>
<g:store_code>1111</g:store_code>
<g:store_code>2222</g:store_code>
</g:vehicle_fulfillment>
Vehicle fulfillment vs. store code
The store_code attribute (data source top level) is equivalent to using vehicle_fulfillment with option = in-store. This is a simplified method of providing one or more store code values without the more complex structure of vehicle_fulfillment (option:store_code:...) group attribute.
For in-store, you must provide one or more store codes. With vehicle_fulfillment for in-store, note that the header in the data source (TSV or CSV file) must list a store_code header value for each store code in the vehicle offers.
Example
id |
... |
vehicle_fulfillment(option:store_code:store_code:store_code) |
... |
Comments |
| 123 | âĶ | in-store:store1:store2:store3 |
âĶ | 3 store codes |
| 456 | âĶ | in-store:store1:store2: |
âĶ | 2 store codes and note the trailing colon required as a delimiter |
| 789 | âĶ | in-store:store1:: |
âĶ | 1 store code and note the trailing colons required as delimiters |
All of the examples above can also be specified using only the store_code attribute because theyâre only in-store (assuming a TSV or non-comma separated data source file in this example):
id |
... |
store_code |
... |
Comments |
| 123 | âĶ | store1,store2,store3 |
âĶ | 3 store codes |
| 456 | âĶ | store1,store2 |
âĶ | 2 store codes |
| 789 | âĶ | store1 |
âĶ | 1 store code |
