OK, I have the hotdogs, the burgers, the buns, the ketchup, the cheese… Hmm, do I have everything? Oh! Beer! I almost forgot the beer!
Next Queries provide shoppers with ideas on what to look for next. In other words, this feature predicts what shoppers might need next before they even know they need it. For example, “cereal”, “cookies”, or “cocoa” might be the next search suggestions for “milk”.
Next queries are related to the initial query, so they usually appear after performing a first search. When a shopper selects a next query, a new search launches without needing to type the search term.
You can identify next queries mostly under labels such as What’s next?, Those who searched for X also searched for, or Other users have also searched.
Organic and curated next queries
With Empathy Platform, you can show organic and curated next queries in your commerce store. Organic next queries are generated automatically based on collective behavioral information, offering the most common searches that are performed by other shoppers after the initial search. Alternatively, you may want to curate the search experience and suggest search suggestions that shoppers might like to use after their initial search to drive sales as part of a branded campaign. For example, as category manager you decide to guide shoppers towards a branded beer by associating a query containing the brand name as next query after the query “hot dogs”, instead of the organic next query “beer”.
Using the Next Queries curation tool in the Empathy Platform Playboard, you can review the organic next queries generated for a query, create new curated next queries that respond to marketing strategies, change the order in which the curated next queries appear, and choose to show or hide organic next queries.
A celebrity working on your jewelry new campaign
See how curated Next Queries can benefit your shoppers and your business
Spot the difference
Although Next Queries and Related Tags are suggestions closely related to the initial search, Next Queries prompts a new query in the search box and launches a completely new search. On the other hand, Related Tags refines the current search without changing the query syntax in the search box.
Try Next Queries to...
- Anticipate shoppers' intent by offering new search suggestions that support your merchandising strategy.
- Improve product findability. Guide shoppers to products they want or are likely to need next.
- Speed up query entry, especially on mobile devices.
- Offer shoppers a shopping list-like feature.
The inner workings of Next Queries
Organic next queries are generated by shoppers’ actions in the search UI. As shoppers perform different searches and actions, behavioral information (queries, clicks, add-to-cart, etc.) is collected using the Tagging microservices.
This information is analyzed by the Query Signals batch process to select the possible query pairs from the same session related to a specific query. So, from the query pairs “milk-cereal”, “milk-cocoa”, “milk-cookies”, cereal, cocoa, and cookies are identified as the organic next queries for the query “milk“ based on the highest interaction.
A review process is performed to check if each query pair is valid according to different filters (i.e. it doesn't feature on a blacklist, it isn't duplicated, etc.) and a ready-to-go list of organic next queries is created and stored by the Beacon microservice.
Curated next queries are created manually by the commerce marketer or merchandiser in the Playboard and sent to the Beacon microservice to be stored with the organic next queries. When the shopper performs a search in the frontend, Empathy Platform Interface X calls the Beacon API to retrieve a list of organic and curated next queries associated with the query, displaying them in the commerce store after the initial search.
Next Queries can also use the local web data stored in the shopper’s browser to determine precisely when a query was written, displaying only those next queries that haven’t been used yet in the current session. For that purpose, you use the History Queries feature.