Build highly-personalized search & discovery experiences at scale
Apply best-in-class algorithms to identify relevant shopper signals and actions throughout the customer journey and deliver personalised rankings and product recommendations at each step.
Refine your ranking strategy
Smart Automation & Creative Control
Decide where and how rankings are applied and override personalisation with business rules.
Ranking & Ranking Cocktails
Rank navigation and search query results based on one or more attributes.
Row-based Merchandising
Apply personalisation to parts of or your entire product listing page – on specific pages or across the website.
Tailored Rankings by Channel
Display different product rankings based on the retail channel.
Guide discovery and optimize up and cross sell opportunities
Segment shoppers based on real-time on-site user behaviour.
Display content that resonates highly with them.
Optimize conversion and retention through personalized product recommendations.
Where AI Scores Can Be Used
| Homepage | Search result page | Product list page | Product page | Result mods | Basket | |
| Ranking & Ranking cocktails | x | x | x | |||
| Product & Content recommendations | x | x | x | x | x |
How it works
User Data Tracking
- AI Scores captures and analyses a variety of user activities from different data points and consolidates into a relevant set of user data.
- The tracker is used to identify the shopper and send the behaviour signals to FHR in real-time. It receives back a cluster id of which that shopper has an affinity with.
Build Personalised Ecommerce Experiences
AI Scores Implementation - Flow
AI Scores Implementation - Architecture
AI Scores Implementation - Tracker Response
The standard Google Tag Manager integration provides the following view action. This is required to initiate the segment assignment of the visitor.
{
"action": "view",
"sourceId": "8c1ed347-49681a",
"target": {
"product": "625606_red"
},
"user": {
"identities": {
"sessionid": "7c2d8f12-3c95724149d4"
},
"segments": [],
"traits": {}
}
}The tracker will respond with something like the following. This need to be used to define the `customer_segment` custom trigger value for Fredhopper.
{
"action": "view",
"sourceId": "8c1ed347-49681a",
"target": {
"product": "625606_red"
},
"user": {
"identities": {
"sessionid": "7c2d8f12-3c95724149d4"
},
"segments": [],
"traits": {}
}
}
Comments
0 comments
Article is closed for comments.