Lucidworks Search integrates with Lucidworks Platform to consume pre-aggregated signals for query boosting and result reranking. This integration lets Lucidworks Search leverage user behavior data captured by the Signals Beacon or Platform Signals API and aggregated in a Lucidworks Platform Signals Store. Platform signals provide an alternative to Lucidworks Search’s native signals system. Instead of capturing and aggregating signals within Lucidworks Search, the Platform signals integration lets Lucidworks Search consume signals that have already been collected and aggregated by Platform Analytics.Documentation Index
Fetch the complete documentation index at: https://doc.lucidworks.com/llms.txt
Use this file to discover all available pages before exploring further.
Architecture
The Platform signals integration involves three main components:- Signal collection via Signals Beacon (browser-based) or Platform Signals API sends raw signals to the Platform Signals Store.
- Lucidworks Search reads aggregated signals from the Platform Signals Store and indexes them for use in query boosting.
- Query Pipelines use the aggregated signals for query boosting via the Boost with Signals stage.
Signal flow
User interactions are captured via Signals Beacon or Platform Signals API and sent to the Platform Signals Store for storage and aggregation. Lucidworks Search periodically retrieves these aggregated signals and indexes them in thesignals_aggr collection.
Query pipelines then use these signals through the Boost with Signals stage to rerank search results based on user behavior patterns.
When to use Platform signals
Use the Platform Signals integration if any of the following apply:- You already use Analytics Studio. This integration uses your existing Platform signals in Lucidworks Search without additional infrastructure.
- You want adaptive behavioral relevance. Platform Signals feeds real customer behavior into Lucidworks Search’s boost stage, enabling relevance that adapts continuously to your users.
- You manage multiple search applications. Platform Signals aggregates behavior from multiple sites and applications using the Signals Beacon (web) or Signals API (any application type), giving you a unified view across your search ecosystem.
- You want advanced signal aggregation. Platform’s aggregation formulas produce refined signals that reflect meaningful behavior patterns rather than raw event counts.
Comparison with Lucidworks Search native signals
| Feature | Lucidworks Search native signals | Platform signals |
|---|---|---|
| Signal collection | Lucidworks Search Signals API | Beacon (browser-based) or Platform Signals API (any application type) |
| Signal storage | Lucidworks Search collections | Platform Signals Store |
| Signal aggregation | Lucidworks Search SQL aggregations | Platform aggregation engine |
Collections
When you enable Platform signals integration, Lucidworks Search creates and populates theCOLLECTION_NAME_signals_aggr collection that stores aggregated signals retrieved from the Platform Signals Store.
Unlike Lucidworks Search native signals, Platform signals integration does not create the following collections because they are not needed:
COLLECTION_NAME_signalsis the raw signals collection. Raw signals remain in the Platform Signals Store.COLLECTION_NAME_signals_session_aggris for session-level aggregations. Platform handles these aggregations.
Next steps
- Configure Platform signals integration
- Configure Boost with Signals stage
- Troubleshoot Platform signals
Related topics
- Signals - Lucidworks Search’s native signals system
- Platform Analytics Signals - Platform signals documentation