# Query Builder

> Build searches using rules, groups, operators, and logic inside the Kommon Poll Query Builder.

> Build searches using keywords, phrases, exclusions, groups, operators, and logic inside Kommon Poll's Query Builder.

The **Query Builder** lets you craft precise, Boolean-style searches by mixing rules, groups, and operators until the results match your listening goal.

Use this page for the standard visual builder. If you need field-specific syntax, fuzzy matching, proximity matching, boosting, or other expert operators, see [Advanced Query Building](/advanced-query-building).

## 1. Start With A Clear Query Goal

Before adding rules, decide what the query must capture:

- Brand names and common spelling variations.
- Product, campaign, or service names.
- Hashtags and public handles.
- Complaint, praise, risk, or topic terms.
- Exclusions that remove known noise.

A good query usually starts broad enough to catch real mentions, then adds exclusions and filters after you review sample results.

## 2. Start Building Your Query

After adding your social tracking sources, open **Query Builder** inside Kommon Poll.

You can add new rule lines or group blocks and pair them with logical operators:

- **AND** - requires every condition inside the group to match.
- **OR** - allows any condition in the group to match, which broadens the results.

These operators control how your rules work together and help you narrow or expand the data Kommon Poll returns.

## 3. Adding Rules

Click **Add Rule** to add another condition to the query.

Each rule includes:

- An `Enter criterion` field for keywords or phrases.
- A condition dropdown, such as contains phrase, contains, does not contain, or does not contain phrase.
- A source or entity operator that limits where or how the rule is matched.

Rules are the building blocks of your query logic design.

## 4. Adding Groups

Click **Add Group** to combine multiple rules under the same logical operator.

Groups help you:

- Organize related conditions.
- Assemble complex queries that mix nested logic.
- Apply different operators inside larger expressions, such as multiple OR rules inside a parent AND block.

## 5. Source Operators

Source operators determine **where** Kommon Poll looks for keywords or phrases.

### Entire Mention

Searches the full mention, including:

- Title.
- Body text.
- Metadata such as tags, classifications, and system properties.

Use this when you want the entire document to be evaluated.

### Entire Mention Excluding Metadata

Targets everything except metadata, keeping the search focused on user-generated content.

Use this when tags, classifications, and system fields may create noise.

### Title

Searches only the document title.

Use this when the keyword must appear in the title rather than the body.

### Text Context

Searches only the body copy and excludes title and metadata.

Use this when you want matches that are tied to the main written content.

## 6. Entity Operators

Entity operators control **how** your phrase matches the text.

### Contains Phrase

Matches an exact phrase in the mention.

Use this for brand names, slogans, product names, and phrases where word order matters.

### Contains

Matches the given keywords in a broader way.

Use this for topic matching where exact wording is less important.

### Does NOT Contain Phrase

Filters out mentions containing that exact phrase.

### Does NOT Contain

Filters out mentions containing specified keywords.

## 7. Common Logical Operators

### AND

- Narrows the search.
- All conditions must be true.
- Use when you need high precision.

### OR

- Broadens the search.
- Any condition may be true.
- Use when capturing variations or alternatives matters.

### NOT And Exclusions

- Removes known irrelevant matches.
- Use for ambiguous brand names, unrelated meanings, or campaign noise.
- Keep exclusions specific so you do not remove useful mentions by accident.

## 8. Basic Query Patterns

### Brand Variations

Use **OR** to capture different ways people refer to the same brand.

```text
"Kommon Poll" OR KommonPoll OR kommonpoll.com
```

### Brand Plus Topic

Use **AND** when a topic must appear with the brand.

```text
("Kommon Poll" OR KommonPoll) AND (pricing OR dashboard OR report)
```

### Complaints Or Issues

Group complaint terms together with **OR**, then connect them to the brand with **AND**.

```text
("Kommon Poll" OR KommonPoll) AND (issue OR problem OR complaint OR "not working")
```

### Exclude Noise

Use exclusions when a keyword has unrelated meanings.

```text
("Commercial Bank" OR ComBank) AND card NOT cricket NOT "trading card"
```

## 9. Use Filters Instead Of Query Text When Possible

For attributes such as platform, country, language, demographics, sentiment, subjectivity, influence, reach, or engagement, use Kommon Poll filters where available.

Filters are usually better than putting those constraints into the query text because they narrow results cleanly without changing keyword relevance.

Use the query builder for:

- Words and phrases.
- Brand, product, campaign, and competitor terms.
- Inclusion and exclusion logic.
- High-level topic logic.

Use filters for:

- Platform or source.
- Country and language.
- Author, domain, tag, subtopic, or intent.
- Sentiment, subjectivity, influence, engagement, and date ranges.

## 10. Deleting Rules Or Groups

If you need to remove a rule or group, click the **Delete** button beside it.

Kommon Poll updates the logic tree automatically so the remaining structure stays valid.

## 11. Apply Your Query

Once all rules and groups look correct:

1. Review the logic structure and operators.
2. Confirm that source and entity operators match your intent.
3. Click **Apply** to run the query.

Kommon Poll executes the search according to the conditions and hierarchy you built.

## 12. Basic Query Checklist

Before saving or running the query, check:

- Are all brand names and common variations included?
- Are exact phrases handled as phrases in the builder?
- Are OR groups used for alternatives?
- Are AND groups used only where every concept must appear?
- Are exclusions specific enough?
- Have you tested sample results before finalizing the project?
- Are platform, country, language, sentiment, and quota-related constraints handled through filters instead of keyword text?