GA4 devices
AI-referred site traffic broken out by device category — mobile, desktop, tablet.
curl --request GET \
--url 'https://api.aiclicks.io/api/v1/ga4/devices?domain_id=8f1d3c0a-2f9b-4c11-9b80-7a82e1f0c3f3&days=30' \
--header 'Authorization: Bearer ak_live_xxx'
import httpx, os
resp = httpx.get(
"https://api.aiclicks.io/api/v1/ga4/devices",
params={"domain_id": "8f1d3c0a-2f9b-4c11-9b80-7a82e1f0c3f3", "days": 30},
headers={"Authorization": f"Bearer {os.environ['AICLICKS_API_KEY']}"},
)
resp.raise_for_status()
for row in sorted(resp.json()["data"]["items"], key=lambda r: r["sessions"], reverse=True):
print(f"{row['sessions']:>6} {row['device']}")
const url = new URL("https://api.aiclicks.io/api/v1/ga4/devices");
url.searchParams.set("domain_id", "8f1d3c0a-2f9b-4c11-9b80-7a82e1f0c3f3");
url.searchParams.set("days", "30");
const resp = await fetch(url, {
headers: { Authorization: `Bearer ${process.env.AICLICKS_API_KEY}` },
});
const { data } = await resp.json();
for (const row of data.items) console.log(row.sessions, row.device);
{
"data": {
"items": [
{ "device": "mobile", "sessions": 720 },
{ "device": "desktop", "sessions": 500 },
{ "device": "tablet", "sessions": 20 }
]
},
"domain_id": "8f1d3c0a-2f9b-4c11-9b80-7a82e1f0c3f3",
"days": 30,
"llm_source": null,
"generated_at": "2026-07-13T10:00:11.218Z"
}
{ "detail": "domain_id query parameter is required. List the domains this key can access with GET /api/v1/domains, then pass ?domain_id=<uuid>." }
{ "detail": "Invalid or revoked API key" }
{ "detail": "API access is not enabled for this team. Contact support@aiclicks.io." }
{ "detail": "Too many requests. Please try again later." }
How the domain's AI-referred visitors split across device categories — mobile, desktop, tablet. Use it to see whether AI-driven traffic skews differently from the rest of the site, which matters when deciding where to optimise landing pages that assistants surface.
Each row is a device category and its AI-referred session count over the window.
Unlike the other GA4 lists, device rows are not sorted — there are only a few categories. Sort client-side by sessions if you need a ranking.
domain_id is a required query parameter. Use `` to discover which domains the calling key can access. When the domain has no connected GA4 property (or no AI-referred traffic in the window), items is empty with a 200.
Authorizations
Your API key formatted as Bearer ak_live_<your-key>. Create one in the dashboard under Settings → Developers.
Optional UUID for log correlation. If omitted, we generate one and echo it back in the response.
Query parameters
UUID of the domain. Find domains via ``. Omitting this returns 400.
Trailing look-back window, 1–365. Defaults to 30.
Optional. Restrict to a single AI/LLM referral source — chatgpt, perplexity, claude, gemini, copilot, … Omit for all sources combined.
Response
The list payload.
One row per device category. Not sorted — sort client-side if needed.
Device category as reported by GA4: mobile, desktop, or tablet.
AI-referred sessions on that device category during the window.
Echo of the requested domain.
Echo of the requested window.
Echo of the requested llm_source filter, or null when unset.
ISO-8601 timestamp of when the server produced (or cached) this response.
Response headers
| Header | Description |
|---|---|
X-Cache | HIT or MISS. Whether the response came from cache. |
X-Request-Id | Unique request id. Echoes incoming if you set one. |
X-RateLimit-Limit | Max requests per minute for this key. |
X-RateLimit-Remaining | Requests remaining in the current minute. |
X-RateLimit-Reset | Unix epoch seconds when the window resets. |
Caching
Cached for a short window per (domain_id, days, llm_source). Freshly synced GA4 data appears after the TTL expires.
Empty result
{
"data": { "items": [] },
"domain_id": "8f1d3c0a-2f9b-4c11-9b80-7a82e1f0c3f3",
"days": 30,
"llm_source": null,
"generated_at": "2026-07-13T10:00:11.218Z"
}