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

# Platform Signals

Fusion integrates with Lucidworks Platform to consume pre-aggregated signals for query boosting and result reranking.
This integration lets Fusion leverage user behavior data captured by the [Signals Beacon](/docs/lw-platform/lw-analytics/signals/signals-beacon) or [Platform Signals API](/docs/lw-platform/lw-analytics/signals/signals-api) and aggregated in a Lucidworks Platform [Signals Store](/docs/lw-platform/lw-analytics/signals/signals-store).

Platform signals provide an alternative to Fusion's native signals system.
Instead of capturing and aggregating signals within Fusion, the Platform signals integration lets Fusion consume signals that have already been collected and aggregated by Platform Analytics.

## Architecture

The Platform signals integration involves three main components:

1. **Signal collection** via [Signals Beacon](/docs/lw-platform/lw-analytics/signals/signals-beacon) (browser-based) or [Platform Signals API](/docs/lw-platform/lw-analytics/signals/signals-api) sends raw signals to the Platform Signals Store.
2. **Fusion** reads aggregated signals from the Platform Signals Store and indexes them for use in query boosting.
3. **Query Pipelines** use the aggregated signals for query boosting via the [Boost with Signals stage](/docs/5/fusion/reference/config-ref/pipeline-stages/query-stages/recommendation-boosting-query-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.
Fusion periodically retrieves these aggregated signals and indexes them in the `signals_aggr` collection.
Query pipelines then use these signals through the Boost with Signals stage to rerank search results based on user behavior patterns.

```mermaid theme={"dark"}
graph LR
    A["Beacon or Platform Signals API"] --> B["Platform Signals Store"]
    B --> C[Fusion]
    C --> D["signals_aggr collection"]
    D --> E["Query Pipeline Boost Stage"]
```

## 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 Fusion without additional infrastructure.
* **You want adaptive behavioral relevance.** Platform Signals feeds real customer behavior into Fusion'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 Fusion native signals

| Feature            | Fusion native signals   | Platform signals                                                      |
| ------------------ | ----------------------- | --------------------------------------------------------------------- |
| Signal collection  | Fusion Signals API      | Beacon (browser-based) or Platform Signals API (any application type) |
| Signal storage     | Fusion collections      | Platform Signals Store                                                |
| Signal aggregation | Fusion SQL aggregations | Platform aggregation engine                                           |

## Collections

When you enable Platform signals integration, Fusion creates and populates the `COLLECTION_NAME_signals_aggr` collection that stores aggregated signals retrieved from the Platform Signals Store.

Unlike Fusion-native signals, Platform signals integration does *not* create the following collections because they are not needed:

* `COLLECTION_NAME_signals` is the raw signals collection. Raw signals remain in the Platform Signals Store.
* `COLLECTION_NAME_signals_session_aggr` is for session-level aggregations. Platform handles these aggregations.

## Next steps

* [Configure Platform signals integration](/docs/5/fusion/getting-data-in/platform-signals/configuration)
* [Configure Boost with Signals stage](/docs/5/fusion/reference/config-ref/pipeline-stages/query-stages/recommendation-boosting-query-stage)
* [Troubleshoot Platform signals](/docs/5/fusion/getting-data-in/platform-signals/troubleshooting)

## Related topics

* [Indexing Signals](/docs/5/fusion/getting-data-in/indexing/indexing-signals/overview) - Fusion's native signals system
* [Platform Analytics Signals](/docs/lw-platform/lw-analytics/signals/overview) - Platform signals documentation