DestinationsMeta match quality day by day

Meta match quality day by day

meta_capi destinations only. The daily series behind GET /client/v1/destinations/{id}/quality: one row per (day, event), newest first.

Why it exists. Meta returns the CURRENT score and keeps no history of its own, so "when did match quality drop" is unanswerable from the live read. Mythic snapshots every connected dataset daily; this is that series.

Gaps are real. A day with no row is a day nothing was captured (a sweep outage, or a token that could not read quality). No value is carried forward — a flat line through an outage would read as stability.

Each row is that day's LAST capture. null means Meta scored nothing that day, never zero. flags are the findings as judged on the day, not re-derived against today's thresholds.

curl -X GET "https://mythic-analytics.gulp.workers.dev/client/v1/destinations/example_string/quality/trend?days_back=30&event_name=John%20Doe" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{
  "success": true,
  "data": {
    "action_id": "123e4567-e89b-12d3-a456-426614174000",
    "days_back": 42,
    "days": [
      {
        "day": "2024-12-25",
        "event_name": "John Doe",
        "action_id": "123e4567-e89b-12d3-a456-426614174000",
        "dataset_id": "example_string",
        "event_match_quality": 3.14,
        "event_coverage_percentage": 3.14,
        "event_coverage_goal_percentage": 3.14,
        "server_dedupe_key_percentage": 3.14,
        "browser_dedupe_key_percentage": 3.14,
        "browser_coverage_from_dedupe_key_percentage": 3.14,
        "additional_conversions_percentage": 3.14,
        "critical_flags": 42,
        "warning_flags": 42,
        "info_flags": 42,
        "test_events_only": 42,
        "flag_codes": [
          "example_string"
        ],
        "upload_frequency": "example_string",
        "captured_at": "2024-12-25T10:00:00Z"
      }
    ]
  }
}
GET
/client/v1/destinations/{id}/quality/trend
GET
Base URLstring

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

Bearer Token
Bearer Tokenstring
Required

Client key as bearer token. Use an agency key (Bearer ak_...) for read-write access or a location secret key (Bearer sk_...) for read-only access. Scoped keys (mcp_) are accepted too and need destinations:read or destinations:write. See Using an mcp_ key over HTTP.

Client key as bearer token. Use an agency key (Bearer ak_...) for read-write access or a location secret key (Bearer sk_...) for read-only access. Scoped keys (mcp_) are accepted too and need destinations:read or destinations:write. See Using an mcp_ key over HTTP.
query
days_backinteger

Days of history. Default 30, clamped to 1-365.

Min: 1 • Max: 365
query
event_namestring

Restrict to one Meta event name, e.g. Purchase.

Request Preview
Response

Response will appear here after sending the request

Authentication

header
Authorizationstring
Required

Bearer token. Client key as bearer token. Use an agency key (Bearer ak_...) for read-write access or a location secret key (Bearer sk_...) for read-only access. Scoped keys (mcp_) are accepted too and need destinations:read or destinations:write. See Using an mcp_ key over HTTP.

Path Parameters

Query Parameters

days_backinteger

Days of history. Default 30, clamped to 1-365.

event_namestring

Restrict to one Meta event name, e.g. Purchase.

Responses

successboolean
dataobject