Use and Invoke Different Search Profiles With Drupal Views

Search Profiles work with Drupal Views to create customized search experiences across different sections of your site.

Search Profiles are named collections of search-related settings that let you switch among multiple search experiences for your website. This means your main site search can work differently from other search implementations on your site.

How Search Profiles Work with Drupal Views

The SearchStax Drupal Module provides a "Relevance model" option under Advanced Query settings. This option allows you to select different Search Profiles for different Views. Each View can use a different Search Profile, giving you more control over search behavior across your site.

Selecting Search Profiles in Views

The relevance model option shows published models and marks the default model with "(default)". When you select a specific Search Profile for a View, searches performed through that View will use the configurations defined in that profile.

Note: This option requires the SearchStax Drupal module 1.9.2+. If a View was configured before upgrading, open the View's Advanced Query settings and save again to apply the selected profile.

Tip: Before enabling this option, verify your installed SearchStax Drupal module version against the latest releases on the Drupal.org project page.

Drupal View Query Options showing SearchStax Settings Relevance model options: Use default, Main Profile (default), Faculty. Use default selected

Passing Context from Drupal to Search Profiles

To enable features in Search Profiles such as Rules and Promotions, the Parse mode and searched fields option must be selected. This ensures the search query is passed in a way that the Search Profile can understand.

Drupal Views can pass additional context to your Search Profiles through contextual filters and exposed filters that influence search behavior.

Analytics and Tracking

SearchStax Site Search supports tracking search results for Drupal websites. Searches are automatically tracked for all searches known to the Drupal Search API module. You can verify which searches are tracked by going to the SearchStax configuration page and checking which searches are listed under "Search-specific analytics keys".

Note: If you're building a tabbed search experience, create a separate View for each tab and configure each View to use its own Search Profile. This gives you independent analytics and configuration options for each search section. See Integrating Search Profiles into Search Experiences.

What's Next

To implement Search Profiles with your Drupal Views, first create and configure Search Profiles in SearchStax. You can then modify your Drupal Views to use specific profiles. For detailed instructions on configuring Search Profiles, see Search Profiles.

Articles in this section