Open the installation section of your dashboard and copy the script containing your catalog ID. Place it before the closing body tag in your shop theme, or use your platform’s footer code setting.
If the existing search field is not detected, configure its CSS selector under Appearance. Verify product links, prices and keyboard controls on desktop and mobile. The catalog ID is public; never put private feed tokens or item-update keys into theme code.
The example below starts product search without cookies or individual search, click and purchase analytics. Aggregate search totals still count toward usage.
For JTL, use the Grumeria plugin and its JTL Consent Manager integration. In other integrations, your consent manager must set data-analytics-consent on the embedded script to 1 only after consent and back to 0 on withdrawal. Optional measurement stays off without this connection.
Set up the product advisor. Open “Product advisor” with editor access and create three to five questions, each with two to eight answers. Each question uses a different active public filter; answers select its catalog values or numeric ranges, including prices. Base the wording on supported product attributes. Try the preview, then save with product selection enabled. It remains off until enabled. Viewers can use the preview but cannot edit the setup.
Use the product advisor in your shop. Shoppers can answer, skip, go back or start again. Counts come from the current catalog; answers with no matching products are disabled. Selected answers appear above the results. This selection creates no persistent customer profile or search and click measurements; answers stay in browser memory.
Use price ranges. A public price filter can show up to five ranges with result counts. These counts reflect the query and every other filter; the current selection for this price filter is excluded from the range counts. Clicking a range sets that price selection. “Under” excludes the upper boundary; shoppers can still enter their own price limits. A ≥ before a count means “at least” because the index counting limit was reached. Ranges are not offered for results using semantic matching in a hybrid search or effective permanently pinned products. Ordinary price inputs remain available when reliable range counts cannot be obtained.
Inspect searches with few clicks. Under “Data quality”, “Results found. Was anything clicked?” lists query and filter combinations with at least ten completed searches with results in the last 30 days and a linked click rate of 10% or less. The most recent 30 minutes are excluded to allow time for a click. Only new, linked searches from the updated widget count, and only when your consent manager sets data-analytics-consent to 1 after explicit consent; it must reset the attribute to 0 on withdrawal.
Choose “Inspect products” in the click report to restore the query, filters and sort order in “Test search”. Review the products available now, then adjust synonyms, placement or filters if needed. A missing click does not prove a lost sale. An empty report may mean there are not enough eligible measurements yet; it does not establish that search quality is good or poor.
Copy the script into your theme. Check desktop, mobile, keyboard navigation and the fallback to native shop search.
<script src="https://grumeria.com/widget-consent-v1.js" data-engine-id="YOUR_CATALOG_ID" data-analytics-consent="0"></script>Account setup and the dashboard are available in English and German.
Sign in