SearchStax Site Search tracks search request usage based on API calls to specific endpoints. Use the Subscription page to monitor your usage, understand what counts as a search request, and plan for your subscription limits.
Where to View Your Plan Usage
Plan limits for search requests and items are account-based. You can view total usage for your account or specific apps.
- In SearchStax, click the Account dropdown in the top navigation.
- Select Subscription.
- View your current month's usage and review available usage trends. For dashboard details, see Subscriptions.
The usage metrics shown reflect account-level consumption. For sandbox-enabled accounts, Subscription shows separate Production and Sandbox totals. Accounts without Sandbox Apps see combined account usage without separate Production and Sandbox views.
For sandbox-enabled accounts, qualifying search requests are counted in the environment where they run. Production usage doesn't reduce Sandbox limits, and Sandbox usage doesn't reduce Production limits. Analytics reflects only tracked search events, so Analytics counts can be lower when tracking isn't set up for some search calls. Check tracking coverage in the Tracking API (JavaScript) and Tracking API (REST) docs.
What Counts as a Search Request
The following API calls contribute to your search request usage:
- Search API calls: Requests made to the
/selector/emselectendpoints count as one search request each. The number of results you request doesn't change that count. For example, a request withrows=500still counts as one search request. Requests to/emselectcount only when they execute a search query. Requests that don't run a query, such as initialization or validation calls, don't count. - Autocomplete and auto-suggest calls: Requests made to the
/autocompleteendpoint count as one search request each. Requests made to the/emsuggestendpoint don't count as search requests. - Smart Answers: When the Smart Answers
/answerendpoint is triggered, it counts as an additional search request on top of the underlying search query. - Related Content: Requests for related content count toward your search request usage.
Note: Indexing or updating content doesn't count toward your monthly search request usage.
When Usage Metrics Are Updated
Subscription usage refreshes approximately every 20–30 minutes. Last Updated shows the most recent refresh in your local time.
Note: Analytics tables and graphs refresh every hour. Some metrics can look static between reporting intervals.
If you need more frequent monitoring or detailed usage insights, contact Support.
Getting Notified About Usage
SearchStax automatically sends email notifications to all users in your account when you reach usage thresholds:
- 60% of monthly limit: Early warning
- 80% of monthly limit: High usage alert
- 100% of monthly limit: Limit reached
These notifications help you review your usage and take action before reaching your monthly search request limit.
Viewing Previous Months' Usage
Use the Subscription page's Trends section to review available historical usage ranges. For the supported ranges and chart guidance, see Subscriptions.
Why Search Request Usage Seems High
If your search request usage appears higher than the search activity shown in your analytics, consider these common causes:
Analytics tracking gaps: Analytics only captures search requests that include tracking events. Verify that analytics tracking is enabled on all sites connected to your SearchStax App.
Example: A hospital search page sends tracking events for user searches. A header search suggestions widget calls the Search API on every page load without tracking. Subscription includes those requests, while Analytics shows only tracked searches. Check your tracking coverage in the Tracking API (JavaScript) and Tracking API (REST) docs.
Additional API usage: Your implementation might use the Search API for purposes beyond user search queries, such as:
- Faceted navigation requests
- Product recommendations
- Content suggestions
- Automated content retrieval
Automated traffic: Bots or automated scripts can increase your usage if they call an endpoint that counts as a search request.
Multiple API calls per user action: Complex search interfaces might trigger multiple API calls for a single user interaction, such as auto-suggest queries, facet updates, and result retrieval.
Environment-based accounting: For sandbox-enabled accounts, usage is tracked separately by environment, and request and item alerts are based on Production thresholds. Current-month Production totals can include usage from deleted Production Apps. Accounts without Sandbox Apps see combined account usage without separate Production and Sandbox views. For those accounts, current-month request totals can also include usage from deleted Apps when applicable.
Tip: Review your implementation to identify all places where the Search API is called, not only the main search interface.
Tip: If you suspect an API token is being used by an unexpected client, rotate your Search API tokens. Create new tokens, update your clients to use the new tokens, and remove the old tokens. See Search API tokens for token management details.
What Happens When You Reach a Limit
Reaching a subscription limit can affect your account differently depending on the limit and your subscription. For details about search request, indexed-item, and App limits, see Service Limits.
What's Next
For more information about SearchStax plans and pricing, see Site Search Pricing. If you're an Acquia or Terminalfour customer, contact Acquia or Terminalfour for more information.
To learn more about Smart Answers usage, see Smart Answers.
If you need additional help optimizing your search request usage, contact Support.