Replicas do not share analytics data with their primary index.
As events are not forwarded from a primary index to its replicas, analytics data remains specific to the index where events are triggered. Each event is tied to the index of the search is was triggered from.
This mean if an event is being triggered on a replica index you should pass the replica's name in the index in the parameter.
When viewing the Analytics for your indices, you can:
- View the analytics for a specific index, or
- View aggregated analytics of a primary and its replicas together
This allows you to analyze performance either at the individual index level or across the full index set.
If you plan on implementing Dynamic Re-Ranking (DRR) on your primary index, but most user events are triggered from a replica, you can set the replica as the source index.
This means that events from the replica will be used to determine the re-ranking behavior applied to the primary index. This ensures that DRR is based on the index that receives the most relevant user interaction data.