> ## 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.

# Enable Platform Signals

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:

* A Lucidworks Platform application configured with a [Signals Store](/docs/lw-platform/lw-analytics/signals/signals-store)
* [Signals Beacon](/docs/lw-platform/lw-analytics/signals/signals-beacon) or [Platform Signals API](/docs/lw-platform/lw-analytics/signals/signals-api) configured
* A Platform integration created for Lucidworks Search
* Platform Client ID and Secret

For Platform setup, see [Platform signals documentation](/docs/lw-platform/lw-analytics/signals/overview).

## Configuration steps

<AccordionGroup>
  <Accordion title="1. Request Platform signals integration">
    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:

    ```yaml theme={"dark"}
    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.

    <Tip>
      Lucidworks Support will configure the Platform credentials and signal retrieval settings for your instance.
    </Tip>
  </Accordion>

  <Accordion title="2. Verify app and collection">
    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.
  </Accordion>

  <Accordion title="3. Configure query pipeline boost stage">
    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:

    | Parameter                  | Value      | Description                                                             |
    | -------------------------- | ---------- | ----------------------------------------------------------------------- |
    | **Aggregation Type**       | `formula1` | This must match the formula name in the signal retrieval configuration. |
    | **Rollup Field**           | `doc_id`   | This is the field containing the document ID in aggregated signals.     |
    | **Rollup Weight Strategy** | `weight_d` | This is the field containing the calculated weight.                     |

    See [Boost with Signals Stage](/docs/lucidworks-search/07-improve-your-queries/boosting/boost-with-signals) for detailed configuration options.
  </Accordion>

  <Accordion title="4. Verify the integration">
    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](/docs/lucidworks-search/04-move-data-in/platform-signals/troubleshooting).
  </Accordion>
</AccordionGroup>

## Next steps

* [Troubleshoot Platform signals](/docs/lucidworks-search/04-move-data-in/platform-signals/troubleshooting)
* [Configure Boost with Signals stage](/docs/lucidworks-search/07-improve-your-queries/boosting/boost-with-signals)
* [Platform integration guide](/docs/lw-platform/lw-platform/settings/fusion-integrations/overview)