Events & ExportAd platform bot traffic

Ad platform bot traffic

Daily count of ad platform review bots Mythic dropped before storing anything. When ads launch, the platform's own crawlers open every landing page. Meta's arrive with ordinary phone and desktop browsers, an fbclid and a facebook.com referrer, so they look like ad clicks. Mythic drops any request from Meta's, TikTok's, LinkedIn's or X's own network, and declared ad crawlers such as AdsBot-Google, at the edge. They never reach sessions, attribution, experiments, replays or destinations, so this count is the only place they show.

source is events (event batches; events counts the events in them), replay (session recording uploads) or link_click (Mythic short-link clicks). Events stored before the filter shipped on 2026-10-07 were removed from Meta's network by IP.

curl -X GET "https://mythic-analytics.gulp.workers.dev/client/v1/data/sessions/bot-traffic?location_id=example_string&days=30" \
  -H "Content-Type: application/json" \
  -H "X-Location-Id: example_string" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{
  "success": true,
  "data": {
    "location_id": "538d4ced-447c-40b9-9afa-d220f9afcc84",
    "days": 30,
    "date_from": "2026-09-08",
    "total_requests": 121,
    "total_events": 259,
    "by_platform": {
      "meta": {
        "requests": 121,
        "events": 259
      }
    },
    "daily": [
      {
        "date": "2026-10-07",
        "platform": "meta",
        "source": "events",
        "requests": 81,
        "events": 259
      },
      {
        "date": "2026-10-07",
        "platform": "meta",
        "source": "replay",
        "requests": 40,
        "events": 0
      }
    ]
  }
}
GET
/sessions/bot-traffic
GET
Base URLstring

Target server for requests. Edit to use your own host.

Bearer Token
Bearer Tokenstring
Required

Agency key (ak_) or location secret key (sk_) as a bearer token. Format: Bearer ak_... or Bearer sk_.... Scoped keys (mcp_) are accepted too and need the read scope of the family the route belongs to (people, events, sessions, replays, exceptions, heatmaps or bigquery_export). See Using an mcp_ key over HTTP.

Agency key (ak_) or location secret key (sk_) as a bearer token. Format: Bearer ak_... or Bearer sk_.... Scoped keys (mcp_) are accepted too and need the read scope of the family the route belongs to (people, events, sessions, replays, exceptions, heatmaps or bigquery_export). See Using an mcp_ key over HTTP.
query
location_idstring

Alternative to the X-Location-Id header for agency (ak_) keys. Ignored for secret (sk_) keys.

query
daysinteger

Trailing window in days. Default 30, min 1, max 400.

Min: 1 • Max: 400
header
X-Location-Idstring

Location to scope the request to. Required for agency (ak_) keys on the event routes. Ignored for secret (sk_) keys, which resolve their own location, and not used by /export.

Request Preview
Response

Response will appear here after sending the request

Authentication

header
Authorizationstring
Required

Bearer token. Agency key (ak_) or location secret key (sk_) as a bearer token. Format: Bearer ak_... or Bearer sk_.... Scoped keys (mcp_) are accepted too and need the read scope of the family the route belongs to (people, events, sessions, replays, exceptions, heatmaps or bigquery_export). See Using an mcp_ key over HTTP.

Query Parameters

location_idstring

Alternative to the X-Location-Id header for agency (ak_) keys. Ignored for secret (sk_) keys.

daysinteger

Trailing window in days. Default 30, min 1, max 400.

Headers

X-Location-Idstring

Location to scope the request to. Required for agency (ak_) keys on the event routes. Ignored for secret (sk_) keys, which resolve their own location, and not used by /export.

Responses

successboolean
dataobject