# Conditions

### When you need a condition

```
Page View trigger fires on every page
→ But you only want to track /pricing page visits
→ Add a condition between trigger and tag
```

***

### How to add a condition

1. Select **Contains (CT)** from the left library panel
2. Place it between a trigger and a tag on the canvas
3. Configure in the right settings panel:

| Field          | Description       | Example                       |
| -------------- | ----------------- | ----------------------------- |
| Condition Type | Comparison method | contains, equals, starts with |
| Field          | Value to check    | page\_path                    |
| Value          | Value to compare  | /pricing                      |

\[📸 IMAGE: Condition settings panel screenshot]

***

### Condition Types

| Type          | Description                 | Example                      |
| ------------- | --------------------------- | ---------------------------- |
| contains      | Value contains string       | page\_path contains /app     |
| equals        | Value matches exactly       | event equals create\_project |
| starts with   | Value starts with string    | page\_path starts with /blog |
| matches regex | Value matches regex pattern | page\_path matches ^/app/.\* |

***

### Examples

#### Fire only on a specific page

```
[PV - Page View]
        ↓
[CT - page_path contains /pricing]
        ↓
[GA4 - pricing_view]
```

#### Fire only for a specific event

```
[CE - _event equals create_project]
        ↓
[GA4 - create_project]
```

\[📸 IMAGE: Canvas showing full flow with condition node]

***

### When to skip conditions

If a tag should fire on all pages or all events without filtering, connect the trigger directly to the tag — no condition node needed.

```
[CE - create_project]
        ↓
[GA4 - create_project]  ← No condition needed
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://taviqo.gitbook.io/taviqo-docs/features/conditions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.