Wildcards
In Elastic, filters may be omitted entirely. When you do filter, wildcards (*) are supported in string and filter values, letting you match many domains, URLs, or keywords in a single request instead of enumerating each value.
Each wildcard * matches zero or more characters. Wildcards are subject to two limits:
- 2 wildcard characters per value — e.g. *.*.databricks.com is valid (two *); *.*.*.databricks.com is not.
- 100 wildcard expressions per request — the total number of wildcard-bearing values across the entire payload (domains, filter values, etc.) may not exceed 100.
Where wildcards apply
Wildcards can be used anywhere a string value is accepted:
- Domains - match subdomains or domain patterns without listing each one.
- Filter values inside query - combine with operators such as ilike to pattern-match against string metrics (e.g. a top organic URL).
Examples
- Match all subdomains of a domain. Return every subdomain under databricks.com (e.g. docs.databricks.com, community.databricks.com):
"domains": ["*.*.databricks.com"]
2. Match a URL path pattern. Use ilike (case-insensitive) with wildcards to find keywords whose top organic URL contains a given path:
"query": {"ilike": ["desktop_keywords_top_organic_url", "*/chatgpt/*"]}
Plain text
{
"v5_payload": {
"delivery_information": {
"response_format": "csv"
},
"report_query": {
"tables": [
{
"filters": {
"countries": [
"US"
],
"domains": [
"*.*.databricks.com"
],
"include_subdomains": false
},
"granularity": "monthly",
"latest": true,
"metrics": [
"desktop_visits",
"mobile_visits"
],
"paging": {
"limit": 100
},
"query": {
"gt": [
"desktop_visits",
50000
]
},
"vtable": "traffic_and_engagement",
"window_size": "1m"
}
]
}
}
}Was this section helpful?
On this page
- Wildcards