Analytics Area

BETA

Agent Gateway is in BETA, and we're continuing to expand its capabilities. Your feedback helps shape what we build next—reach out to us through Relewise Support.

The Analytics area provides read-only insights into Relewise performance and user behavior. Use it to understand Search behavior, identify opportunities, and evaluate attributed revenue.

The Analytics area must be allowed in the Agent Gateway Configuration before its REST endpoints or MCP tools can be used.

Search Analytics

Search Analytics supports an overview of Product Search performance, available filter values, and focused lists of Search Terms. It reflects Product Searches made by identified users; anonymous Product Searches are not included.

Capability	REST Endpoint	MCP Tool
Search overview	/analytics/search/overview	fetch_search_analytics_overview
Filter options	/analytics/search/filter-options	fetch_search_analytics_filter_options
Popular searches	/analytics/search/popular	fetch_popular_searches
Searches with a low click rate	/analytics/search/low-click-rate	fetch_low_click_rate_searches
Searches trending up	/analytics/search/trending-up	fetch_searches_trending_up
Searches trending down	/analytics/search/trending-down	fetch_searches_trending_down
Searches without results	/analytics/search/without-results	fetch_searches_without_results

Search Analytics requests use an inclusive date range and a language. Depending on the capability, you can also filter by currency, channel, subchannel, classifications, and Search Term. Search Term lists are bounded for MCP and paginated for REST.

Search Analytics requires a valid language. If one is not already available, use Dataset metadata from the Core area to discover one. When additional filtering is needed, use filter options to discover any currency, channel, subchannel, Classification Key, or Classification Value that is not already known to be valid. Available values depend on the current selections; for example, available subchannels depend on the selected channel.

Choose the focused Search Term list that matches the question:

• Popular searches ranks terms by search count.
• Low-click-rate searches ranks terms using Relewise's low-click-opportunity calculation.
• Searches trending up ranks terms using Relewise's trending-up calculation for the requested and preceding equivalent periods.
• Searches trending down ranks terms using Relewise's trending-down calculation for the requested and preceding equivalent periods.
• Searches without results ranks terms that returned no results by search count.

Revenue Analytics

Revenue Analytics reports attributed revenue and related measurements across the Dataset, request locations, and recommendation types.

Use the REST endpoint:

GET /api/v1/datasets/{Dataset ID}/analytics/revenue

For MCP, use the fetch_revenue_analytics tool.

The request requires an inclusive date range and currency. The response contains display-ready and numeric measurements so connected tools can present values or perform calculations. It also contains daily Revenue time series for the Dataset overall and for each recommendation type.

Each series contains chronological data points with a date and numeric value in the requested currency. Data points represent dates for which analytics data is available, so the returned dates are not necessarily continuous or identical to the requested period.

REST API Base URL

REST endpoint paths in the tables are relative to:

https://my.relewise.com/agents/api/v1/datasets/{Dataset ID}

See Get Started with Agent Gateway for connection and authentication instructions.