tags define additional attributes for uploaded sales data or product catalogues allowing you to create subsets of the full data. Data subsets can be used to define which campaign sends the feedback requests to consumers or to filter content to generate highly focused reports. Where multiple tags have been added to a single sale or product, filtering can be set up using each tag individually or they can be combined to create complex filtering operations to identify the sales/products concerned.  The full list of system-configured tags is shown in Sales And Product Tags.

File type
TXT/CSV file field name
XML field name (case sensitive)
Required/Optional
Default value
Sales file
tags
tags
Optional
None
Product catalogue
tags
N/A
Optional
None

Tag requirements are:

  • A tag key and a tag value.
  • A colon (e.g. key:value) as the separator but if preferred, equals (e.g. key=value) can be used instead. Note that Reviews API only supports colons as the separator for tags.
  • Any number of tags can be added to each sale/product, each being separated by a comma (,).
  • Where the tag value contains a comma, square brackets [  ] are used as a delimiter to ensure the correct values are assigned.

Sales File Example

You might have three separate sales channels: store, phone and web. By giving each sale in the uploaded sales data one or more tags, each in the form of ‘key:value’ or 'key=value', reports can be generated that filter by tags that only show one or more of these sales channels. Using the format key:value, a tag ‘key’ could be 'saleschannel' and the ‘value’ could be 'Store', 'Phone' or 'Web' depending on which sales channel the customer purchased their items. This means the sales tags would be:

  • For store sales: saleschannel:Store
  • For phone sales: saleschannel:Phone
  • For web sales: saleschannel:Web

The data could then be tagged further with details of the actual store where the purchase took place (for store sales) and the sales person who made the sale (for store and phone sales) giving store sales examples such as:

  • store:London 
  • store:Oxford 
  • store:Southampton 
  • store:Edinburgh 
  • salesperson:Karen Jones 
  • salesperson:Mary O’Brien

And for phone sales: 

  • salesperson:John Smith 
  • salesperson:Jane Williams

Multiple sales/product tags can be added to each sale, each being separated by a comma (,) giving examples such as:

  • For a store sale: saleschannel:Store,store:Oxford,salesperson:Karen Jones 
  • For a phone sale: saleschannel:Phone,salesperson:Jane Williams

Product Catalogue Example

tags can be also added to the product catalogue to give the same effect but as a catalogue only contains products, only product tags can be added. 'Department' is a typical example of a product catalogue tag as it appends each uploaded sale of the product with the 'department' tag automatically without the need for the product-specific tag to be in the sales file. This then allows department-specific feedback requests/reports to be easily generated using the Feefo Hub. Examples being:

  • department:Clothing
  • department:Shoes

tags can sometimes have values that include commas in the content. 'Department' tags are a good example as they often include multiple types of product within the same department. With commas indicating separate tags, square brackets are added to delimit the tag to ensure the correct values are assigned. For example:

  • [department:CDs, Vinyl & Tapes]
  • [department:Cookware, Tableware & Glasses],store:Edinburgh,salesperson:MaryO'Brien
Sales File Field: product linkSales And Product Tags

Back to Product Catalogue field summary