This release introduces improvements that help you get more value from Activate Search. Updates include smarter user engagement capabilities, more flexible ranking and sorting options, and several fixes that improve reliability and search accuracy across the platform.
Improvements
Advanced Ranking and Sorting
Ranking rules now support date-type fields, giving you more control over how search results are prioritized. You can create rules using conditions such as “greater than”, “less than”, and “between” to fine-tune results based on time-based data.
Sorting options have also been expanded. You can now sort results using date and text fields, making it easier to configure search results in a way that best fits your use case.
Enhanced Error Handling and Usability
Several improvements have been made to make the platform easier to use. When import payloads exceed supported limits, the interface now provides a clear notification so you know what action to take.
User management settings have been streamlined to align with the updated Spotler ID system, helping create a clearer and more consistent user management experience.
Smarter Search Request Handling
The Javascript Client now allows you to block search requests in the beforeFetch hook. This gives you more control over which queries are sent to the search endpoint and helps you fine-tune how search requests are handled on your website.
Improved Multi-Dataset Query Logic
Search queries that return no results in one dataset but matches in another will now still display relevant results. This helps prevent situations where valid results are hidden when searching across multiple datasets.
Bug Fixes
Searches for fractional values (e.g., “1/2”) now return only relevant results, with exact matches prioritized and unrelated results filtered out.
Filtering with “OR” now works as expected, returning results that match any specified criteria.
Spellcheck now only uses enabled fields, improving result accuracy.
User management options have been streamlined to prevent confusion.
The Javascript Client V2 now uses the correct context, resolving previous script issues.