Loyalty points [loyalty_points]

 

Use the loyalty points [loyalty_points] attribute to specify how many and what type of loyalty points a customer receives when buying your product.

When to use

Optional for products targeting Japan

If you're targeting Japan and you offer loyalty points for purchasing your product, submit information about these points using the loyalty points [loyalty_points] attribute.

This attribute uses 3 sub-attributes:

• Loyalty points programme name [name] (Optional)
  The name of the loyalty points programme (up to 12 full-width characters or 24 roman characters, for example, Programme A).
• Loyalty points value [points_value] (Required)
  Number of loyalty points a customer receives when purchasing your product (for example, 100).
• Loyalty points ratio [ratio] (Optional)
  The ratio of a point when converted to currency (for example, 0.5). If you don't include a value, the default is 1.0.

Format

Follow these formatting guidelines to make sure that Google understands the data that you're submitting.

For details on when and how to submit values in English, learn more about submitting your product data.

Type	Unicode characters (Recommended: ASCII only)
Repeated field	No

File format	Example entry
Text feeds	Format the value by submitting the name, points_value, and ratio sub-attribute values each separated with a colon ( : ). Don't use quotation marks. All colons, even for blank values, are required, in this case two colons are required. You should include attributes in order of priority. For example, for Programme A with 100 points and equal to '0.5 currency units', submit: Programme A:100:0.5 To default to '1.0 currency unit', still include the colon, but leave the value blank: Programme A:100: To submit only '100 points', include the colons, and leave the other 2 values blank: :100:
XML feeds	<g:loyalty_points> <g:name>Programme A</g:name> <g:points_value>100</g:points_value> <g:ratio>1.0</g:ratio> </g:loyalty_points>

To format your data for Content API, have a look at the Content API for Shopping.

Guidelines

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

Minimum requirements

These are the requirements that 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 on the Diagnostics page of your Merchant Center account.

• Provide a date up to one year in the future.

Best practices

These best practices can help you go beyond the basic requirements to optimise your product data for performance.

• Submit loyalty points that have a specific monetary value. Loyalty points are supported only if they have a monetary value. For example, the following types of points aren't supported: mileage and loyalty points that are only exchangeable with goods. 
• Submit points that are issued by you. You can also submit cross-industry points as long as you issue the points. For example, the following types of points aren't supported: points associated with credit cards and electronic money. 

Examples

Text feed

Format the value by separating each sub-attribute (name, points_value and ratio) with a colon ( : ).

For example, for 'Google loyalty programme' with '100 points' where 1 point equals '0.5 currency unit', submit:

Google loyalty programme:100:0.5

To default to 1 point equals '1.0 currency unit', still include the colon, but leave the value blank:

Google loyalty programme:100:

To submit only '100 points', include the colons, and leave the other 2 values blank:

:100: