Skip to main content

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.

Configure Lucidworks Search to consume aggregated signals from Lucidworks Platform for query boosting and result reranking.

​
Prerequisites

Before configuring Platform signals in Lucidworks Search, make sure you have the following: For Platform setup, see Platform signals documentation.

​
Configuration steps

Contact Lucidworks Support to enable Platform signals integration for your Lucidworks Search instance. Provide the following information in your support request:
  • Platform integration name
  • Platform Client ID and Client Secret
  • Platform application ID
  • Lucidworks Search app name where signals should be indexed
  • Signal aggregation formula configuration
Example formula configuration:
formula1:
  CLICK: 2.0
  CART: 3.0
  PURCHASE: 4.0
The formula configuration defines how different signal types are weighted and must match the aggregation formula configured in Lucidworks Platform.
Lucidworks Support will configure the Platform credentials and signal retrieval settings for your instance.
Verify that your Lucidworks Search app exists:
  1. Log in to Lucidworks Search Admin UI.
  2. Navigate to Apps.
  3. Confirm your app is listed.
Lucidworks Search automatically creates the COLLECTION_NAME_signals_aggr collection when signal retrieval is configured. You don’t need to create the collection manually.
Add the Boost with Signals stage to your query pipeline:
  1. Navigate to your app’s default query pipeline.
  2. Add a Boost with Signals stage.
  3. Configure the stage parameters as shown in the table below:
ParameterValueDescription
Aggregation Typeformula1This must match the formula name in the signal retrieval configuration.
Rollup Fielddoc_idThis is the field containing the document ID in aggregated signals.
Rollup Weight Strategyweight_dThis is the field containing the calculated weight.
See Boost with Signals Stage for detailed configuration options.
After configuration, verify the integration is working:
  1. Check collection population:
    • Navigate to the COLLECTION_NAME_signals_aggr collection in Lucidworks Search.
    • Open Query Workbench.
    • Run a query: q=*:*.
    • Verify documents exist with expected fields.
  2. Test query boosting:
    • Execute a query through your configured pipeline.
    • Verify that results with signal data receive appropriate boosts.
  3. Contact Support if needed:
    • If signals are not appearing in the collection, contact Lucidworks Support.
    • Provide your app name and the approximate time you expect signals to have been retrieved.
If the integration is not working, see Troubleshooting Platform Signals.

​
Next steps