DestinationsWhat Google did with a delivery after accepting it

What Google did with a delivery after accepting it

Data Manager destinations only (google_ads, google_analytics). A 200 at delivery time means ACCEPTED — not ingested, and not yet visible. Ingestion is asynchronous (roughly 30 minutes to settle in practice) and Google reports downstream failures only here.

This is what distinguishes a working destination from one whose data is being silently discarded: both show a clean run of 200s in the delivery log. request_status is PROCESSING until Google finishes, then SUCCESS, FAILED or PARTIAL_SUCCESS — PROCESSING is normal, not a fault. error_counts names the reason and how many records it affected.

You do not supply Google's request id; it is stored per delivery and resolved for you.

curl -X GET "https://mythic-analytics.gulp.workers.dev/client/v1/destinations/example_string/deliveries/example_string/status" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{
  "success": true,
  "data": {
    "google_request_id": "example_string",
    "request_status": "PROCESSING",
    "record_count": "example_string",
    "error_counts": [
      {
        "reason": "example_string",
        "recordCount": "example_string"
      }
    ],
    "warning_counts": [
      {}
    ]
  }
}
GET
/client/v1/destinations/{id}/deliveries/{eventUuid}/status
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.
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

Responses

successboolean
dataobject