Back to SiteAPI Docs

Using Analytics Filters

Learn how to filter Smler analytics by UTM parameters, device, country, city, browser, referrer and more to get precise insights into your link performance.

May 17, 2026 5 min read
A
Abhishek Singh
Published in Smler Docs
Using Analytics Filters

Smler's analytics support a rich set of filters so you can slice your click data exactly the way you need — by campaign, geography, device, or individual link. Filters work identically whether you are using the dashboard UI or the REST API.

Date Range

Every analytics query requires a startDate and endDate in YYYY-MM-DD format. The time series endpoint automatically switches from daily granularity to hourly granularity when the selected range is 2 days or fewer — useful for monitoring a live campaign launch.

Pass one or more short URL IDs in the shortUrlId array to scope results to specific links. This is useful when you want to compare a handful of links side-by-side without pulling the entire account's data.

{
  "startDate":  "2026-05-01",
  "endDate":    "2026-05-17",
  "shortUrlId": ["abc123", "xyz789"]
}

UTM Filters

UTM parameters let you trace exactly which campaign, channel, and creative drove a click. Smler captures all five standard UTM dimensions:

Filter field

UTM parameter

Example values

utmSource

utm_source

google, newsletter, twitter

utmMedium

utm_medium

email, cpc, social

utmCampaign

utm_campaign

launch-may, black-friday

utmTerm

utm_term

pricing, free-trial

utmContent

utm_content

hero-cta, sidebar-banner

All filters accept an array, so you can include multiple values in a single query:

{
  "startDate":   "2026-05-01",
  "endDate":     "2026-05-17",
  "utmSource":   ["google", "bing"],
  "utmMedium":   ["cpc"],
  "utmCampaign": ["launch-may"]
}

Geographic Filters

Narrow results to a specific audience location at three levels of precision:

  • country — ISO 3166-1 alpha-2 codes, e.g. ["IN", "US", "GB"]

  • region — state or province name, e.g. ["Maharashtra", "California"]

  • city — city name, e.g. ["Mumbai", "San Francisco"]

These filters are combinable. For example, to see only clicks from Mumbai and Bengaluru in India:

{
  "startDate": "2026-05-01",
  "endDate":   "2026-05-17",
  "country":   ["IN"],
  "city":      ["Mumbai", "Bengaluru"]
}

Device, Browser & OS Filters

Understand what environment your audience is using so you can prioritise platform-specific optimisations:

  • device — mobile, desktop, tablet

  • browser — Chrome, Safari, Firefox, Edge

  • os — Android, iOS, Windows, macOS

Referrer Filter

The referrer filter accepts an array of referrer domains. This complements UTM source data by capturing organic traffic that does not carry UTM parameters — for example, a link shared directly on WhatsApp or copied from a browser bar will show up as a referrer rather than a UTM source.

{
  "startDate": "2026-05-01",
  "endDate":   "2026-05-17",
  "referrer":  ["t.co", "linkedin.com"]
}

Folder Filter

If you organise your links into folders, use the folderName filter to see aggregated performance across all links in one or more folders:

{
  "startDate":  "2026-05-01",
  "endDate":    "2026-05-17",
  "folderName": ["campaign-q2", "product-launch"]
}

Combining Filters

All filters are applied together with AND logic. For example, the query below returns analytics only for mobile users from India who arrived through a Google CPC campaign:

{
  "startDate": "2026-04-01",
  "endDate":   "2026-05-17",
  "country":   ["IN"],
  "device":    ["mobile"],
  "utmSource": ["google"],
  "utmMedium": ["cpc"]
}

Within each individual filter field the values are matched with OR logic — so "country": ["IN", "US"] matches clicks from either India or the United States.

Published with LeafPad

Tags

utmfiltersanalytics