# Usage Examples

Queries that already work, grouped by what they find. Each tile is a live search - click it to see who is running that code right now, then adapt the query to whatever you are actually looking for.

- [Advertising](https://publicwww.com/docs/examples/ads/) - ad networks and exchanges, by the script they inject.
- [Marketing](https://publicwww.com/docs/examples/marketing/) - live chat, popups, email capture, A/B testing.
- [Analytics](https://publicwww.com/docs/examples/analytics/) - counters and tag managers, often with the account id visible.
- [Technologies](https://publicwww.com/docs/examples/webtech/) - what the server runs, as far as it admits to it.
- [Frontend](https://publicwww.com/docs/examples/frontend/) - frameworks, UI kits and the libraries they pull in.
- [Widgets](https://publicwww.com/docs/examples/widgets/) - embedded players, maps, share buttons, comment systems.
- [CMS](https://publicwww.com/docs/examples/cms/) - content management systems, and often their version.
- [Ecommerce](https://publicwww.com/docs/examples/ecommerce/) - shop platforms, carts and payment providers.

Most of these are a single exact phrase. That is usually all it takes: a third-party script has a filename or a configuration key that nobody edits, and searching for it finds every site that installed it. The [query syntax](https://publicwww.com/docs/query-syntax/) page covers narrowing by country, by page depth or by IP, and `snipexp:` for pulling the account ids back out of the matches. For a product that is not here, [Signatures](https://publicwww.com/docs/signatures/) shows how to find its code.

Source: https://publicwww.com/docs/examples/