Refer App
Documentation
Tags
Label and segment sessions automatically, based on rules you define.
ProTags let you slice your attribution data beyond the default channel classifications.
Create a tag called Q3 Campaign that matches any session where
utm_campaign contains q3, and every matching session — past and
future — gets that label.
Creating a tag
- Go to Tags and click Add tag
- Give the tag a name and choose a colour (used in the tag pills throughout the console)
- Add one or more rules that define which sessions should receive this tag
- Save. New sessions are tagged automatically as they arrive. Use Apply to existing sessions to tag historical sessions retroactively.
Rule types
Each tag can have multiple rules. All rules must match for a session to receive the tag (AND logic).
UTM rule
Matches on any UTM parameter. Useful for tagging by campaign, medium, or source.
| Field | Operator | Value | Matches |
|---|---|---|---|
utm_medium | equals | email | Sessions where the medium is exactly "email" |
utm_campaign | contains | black-friday | Sessions from any campaign with "black-friday" in the name |
utm_source | starts with | partner- | Sessions from any source beginning with "partner-" |
URL pattern rule
Matches on the landing URL or page path. Useful for tagging sessions that arrived on a specific page or section.
| Field | Operator | Value | Matches |
|---|---|---|---|
landing_url | contains | /pricing | Sessions that landed on any pricing page |
page_path | starts with | /blog | Sessions that arrived on any blog post |
Date range rule
Matches sessions that occurred between two dates. Useful for tagging sessions from a specific campaign flight or event period.
| Format | Example |
|---|---|
YYYY-MM-DD..YYYY-MM-DD | 2024-11-25..2024-12-02 — Black Friday week |
Operators
| Operator | Behaviour |
|---|---|
| equals | Exact match (case-insensitive) |
| not equals | Does not match exactly |
| contains | Value appears anywhere in the field |
| starts with | Field begins with the value |
Applying tags to existing sessions
When you create a new tag or add rules to an existing one, new incoming sessions are tagged automatically. Historical sessions that match the rules are not tagged automatically — click Apply to existing sessions on the tag to run the rules retroactively across every session in the database.
Deactivating a tag
Deactivating a tag stops it being applied to new sessions but leaves existing tagged sessions unchanged. The tag's rules are preserved, so you can reactivate it later and apply it retroactively again if needed.