The Tagging section lets you configure the settings for the Tagging microservice that is responsible for capturing shopper interaction in the commerce store.
Only Playboard users with permissions for Instance Management can set up and edit the Tagging settings.
When you access the Tagging configuration form for the first time, the Disabled label appears beside the Tagging section in the side menu. This means that there is no active configuration for the service. Once you have created the configuration, you need to enable the microservice.
To set up the Tagging microservice, you complete these steps:
- Determine the filter settings to be used.
- Determine the data validations to be performed (if required).
- Disable query transformation options.
- Save the configuration and enable the microservice.
You must set up the Tagging microservice before starting to send tagging events to the Tagging API.
Configuring filter settings
Filters are passed as parameters in the events sent to the Tagging microservice from the commerce store to allow customers to filter and segment the data in the Empathy Platform Playboard.
Considerations to take into account
The Tagging microservice accepts five filters: language, scope, catalog, store, and section. The Language filter is mandatory and must be passed in all calls to the microservice. The values entered for the filters in Tagging must also be entered in the Search and Playboard settings.
Languages (required): Language(s) to be passed in tagging events. The language(s) selected here must match the product catalogue language(s). For example, if the Index plugin and microservice store the product catalogue language Spanish as “es”, then enter “es” here.
langparameter must be included in all calls to the Tagging API. Otherwise, it returns a bad request. See Determine tagging filter values.
If value passed in the
langparameter does not match the language value determined in the tagging configuration, the event is logged as “ignored”.
To make it easier to set up the languages, use ISO 639-1 codes (opens new window). If you use two letter codes, it's recommended that you implement store to track specific usage where the language is used in multiple countries. For store, you can use the ISO 3166-1 alpha-2 (opens new window) two letter codes.
If you don't want to implement store, then you can use four letter codes (e.g. EN-GB, EN-IE, EN-US).
However, bear in mind that the language code format must be identical throughout the implementation (Index plugin, product catalogue, Playboard).
Filters (optional): Additional filters to be used to classify the tagging data. Here you can set up four different filters:
- Scope: Can be used to track the device that shoppers use to interact with the store. For example, desktop, tablet, mobile, mobileapp, etc. are common values passed in this filter. It can also be used to track specific operating systems, such as ios, android, etc.
- Catalog: Can be used to track interaction with specific categories of the product catalogue. For example, food, non-food, homeware, etc.
- Store: Can be used to track shopper interaction with specific stores in a global site. For example, ES, US, UK, EU, INTL or internal warehouse IDs to track stores for specific countries or a generic Europe or international store.
- Section: Can be used to track interaction with specific sections of the store. For example, women, men, kids, etc.
You can choose to implement all or none of these filter types. Adapt the values for each filter to reflect the customer's specific requirements. The Tagging API accepts any value.
Event calls to the Tagging API with a value that does not match the Filter value are still collected, but with the value “ignored”.
To add a filter, you need to add all the values for the filter, and then add the filter:
- Enter a value in the Values field and click +. The filter value is displayed below the Values field.
- Select the filter type in the Name field and click the + icon for the Filters section.
- Click Save to keep the changes.
To add more values, enter another value in the Values field and click the + icon. If you want to change a value for the filter, click the X icon to remove the value and then enter a new value in the Values field.
Configuring tagging data validations
Validations are performed on all tagging events to remove undesired activity, such bot actions that trigger events, which may cause unnecessary noise in the data collected, or to retrieve mandatory parameters such as product IDs.
Banned IP addresses (optional): Source IP addresses to be ignored by the Tagging microservice. Any events from the IP addresses listed here are removed before processing.
Use CIDR notation (opens new window) to specify a range of IP addresses. For example, 188.8.131.52/24 bans all addresses from 192.0.2.0 to 192.0.2.255.
Banned user agents (optional): User agents to be ignored by the Tagging microservice. Any events from the user agents listed here are removed. For example, if "Mozilla/5.0" was a forbidden value, all user agents containing the string 'Mozilla/5.0' would be ignored.
Product ID regex (optional): Regular expression used as a fallback product ID locator when the
product_idparameter is not available. If the product ID is not provided, the regular expression entered in this field is used to retrieve the product ID from the URL.
For example, you may want to use a regular expression such as
p(\\d+)to indicate that in the URL http://www.example.com/p12345,
p12345is the product ID.
Disabling query transformations
During tagging enrichment, some query transformation processes are performed such as query stemming or normalization. You apply stemming to queries to normalize the plural of search terms to their singular form (e.g. shoes - shoe) and ensure term variants match during data transformation. When the Tagging Enrichment microservice receives, for example, the term dresses as
query parameter, it can be normalized to dress for easier consumption by other Empathy Platform's services.
- Disable stemming: Allows to disable query stemming for incoming queries. When the Disable stemming toggle switch is turned on, no query transformation process is performed. In other words, search terms in plural are not transformed into their singular form.
Enabling the Tagging microservice
Once you have updated the configuration and clicked Save, you need to enable the Tagging microservice by turning on the Enabled toggle switch.
The Tagging microservice is then ready to start receiving events from the commerce store. To learn how to integrate the tagging events in the presentation layer, see Capture interactions with the Tagging API.