Product intelligence search: overview

The Product Intelligence search type lets you research a product, market, brand, patent, scholarly topic, event or app and pull back what the underlying Google and Apple data sources hold for it. Pick it from the search composer when your starting point is a search query — a keyword, product or brand name — rather than a username, email, phone number, wallet address or other personal identifier.

The UserSearch composer with the Product Intelligence search type active, showing the grid of seven Modules with Product Trends selected, its Google Trends description, the Search Query input with Location, Language and Search-Type dropdowns, and a "Cost per search: Free" line

When to use it

Use the Product Intelligence search type when your starting point is a query rather than a person, and you want to:

• Measure search interest in a term over time, or see what is trending right now (via the Product Trends and Trending Now Modules, both on Google Trends).
• Find academic publications on a topic (via Scholar Search, on Google Scholar).
• Look up events (via Events, on Google Calendar).
• Research patents (via Patents, on Google Patents).
• Pull ad creative data (via Ad Creatives, on Google Ads).
• Search App Store listings (via Apple Apps, on Apple).

This search type exposes seven Modules across six Google and Apple data sources. For the full breakdown of each Module, its data source, its cost, and what it returns, see Product intelligence modules & options.

The end-to-end flow

The Product Intelligence search type follows the same search composer flow as every other search in UserSearch — see How UserSearch works for the general model.

1. In the composer header, open the Search type selector and choose Product Intelligence. It is shown with a box/package glyph and a chevron.
2. Pick a Module from the grid — Product Trends (the selected/lead Module) or one of Trending Now, Scholar Search, Events, Patents, Ad Creatives or Apple Apps. The Module grid is single-select: selecting one deselects the others. The selected tile is drawn with a coral-orange highlighted border, and it loads its description, its Cost per search value, and its query form below.
3. Enter your term in the Search Query field. In the captured build the placeholder is e.g. iphone. Optionally set the Location, Language and Search-Type dropdowns beside the query — in the captured build (with Product Trends selected) these default to Auto-detect, Auto-detect and Web Search respectively.
4. Confirm the Cost per search line beneath the input before you run. With Product Trends selected it reads “Cost per search: Free” — the Module consumes no Credits per search.
5. Select Search Now (the coral-orange button with a magnifier icon beside the Search Query field) to run the query.

Caution

This search type does not expose the OneScan multi-source Module or a Choose Data Source configuration modal in the captured build — each of its seven Modules runs against a single data source. Beyond the Location, Language and Search-Type dropdowns, no per-search filters or entity-type tabs are part of the Product Intelligence composer as captured. See Product intelligence modules & options for details and OneScan explained for how OneScan works where it is offered.

Note

Product Trends is the app’s fixed out-of-box default for this Search type, not a persisted last-used preference (per Lee, 2026-07-10); it is also the only Module whose cost was captured (Free). Confirm the Cost per search line for whichever Module you actually select before running.

What you get back

Selecting Product Trends and running a search returns, per its on-screen description, an analysis of product search trends over time via Google Trends. The captured description panel reads: “Analyse product search trends over time using Google Trends. Useful for market research and competitive analysis.” Each other Module returns the data of its own source instead — current trending topics, academic publications, calendar events, patent records, ad creative data, or App Store listings respectively (see the modules page for the per-Module detail).

Results populate the Search Results panel on the right, which carries the standard Found / Enriched / Connections counters and Details / Graph tabs, with the data source repeated in the results as the Data Source column.

For how to read and verify those results — the counters, the results table columns, and the Details panel — see Reading Product intelligence results.

Verified against UserSearch v2.0.20