loyalty_points [loyalty_points]: Definition

 
The loyalty_points [loyalty_points] attribute lets you 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 your purchasing your product, submit information about these points using the loyalty_points [loyalty_points].

The loyalty_points [loyalty_points] attribute uses 3 sub-attributes:

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

Format

Follow these formatting guidelines to make sure that we understand the data that you're submitting. 

Type Unicode characters (Recommended: ASCII only)
Repeated field No
 
File format Example entry
Text feeds

Format the value by submitting the name [name], points_value [points_value] and ratio [ratio], each separated by a colon ( : ). Don't use quotation marks. All colons, even for blank values, are required, i.e. two colons are required. You should include attributes in order of priority.

For example, for Program 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.

  • Ensure that you only use this attribute if you are sure that your product doesn't have any assigned unique product identifiers. 
  • Products for which the identifier_exists [identifier_exists] attribute is incorrectly set to no [no] or false [false], and for which there is evidence that a unique product identifier exists, will be disapproved.

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 [name], points_value [points_value] and ratio [ratio]) by a colon (:). 

For example, for Google loyalty program 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:

Was this helpful?
How can we improve it?

Need more help?

Sign in for additional support options to quickly solve your issue