Skip to main content

In your app

A function makes the call on the client it is given, so your code passes the real one and a test passes a fake.

Add the function

src/attract/get-ads-metrics.ts

Call it

A script makes the client once and calls the function:
scripts/get-ads-metrics.ts
Terminal
A route handler, a job or a queue worker calls it the same way.
Two sections:
  • landings — page views whose URL carried an ad click ID, from the Request Log (every visitor counts; nothing identifying is used). Empty while the Request Log is switched off. Only day, platform (google, meta, tiktok, other), utmSource, utmCampaign and landingPath apply.
  • conversions — conversion events by when they happened. Always also grouped by currency. value sums restated values and leaves out retracted events. Grouped by platform (a destination such as google-ads), each row adds browser and server delivery outcomes — the delivery success rate.
Days are UTC. At most 5,000 rows per section.
One object, e.g. getAdsMetrics({ from }); leave out the optional fields.
Date | string | null | undefined
Optional. Leave it out (or pass null) and it isn’t sent: the site’s default applies. Start (inclusive), ISO 8601 date or time. Default: 30 days before to. Format: an ISO 8601 date and time.
Date | string | null | undefined
Optional. Leave it out (or pass null) and it isn’t sent: the site’s default applies. End (exclusive), ISO 8601 date or time. Default: now. Format: an ISO 8601 date and time.
readonly GroupBy[] | null | undefined
Optional. Leave it out (or pass null) and it isn’t sent: the site’s default applies. Comma-separated dimensions, or the parameter repeated. Each one of day, conversion, platform, utmSource, utmCampaign, landingPath. No duplicates.
An AdsMetricsResponse. The aggregates. Read its properties (adsMetrics.from): each says whether the site always sends it.
Date
Always sent. The window’s start (inclusive). Format: an ISO 8601 date and time.
Date
Always sent. The window’s end (exclusive). Format: an ISO 8601 date and time.
readonly GroupBy[]
Always sent. The dimensions asked for. Each one of day, conversion, platform, utmSource, utmCampaign, landingPath.
AdsMetricsResponseLandings
Always sent. An AdsMetricsResponseLandings. Page views whose URL carried an ad click ID (from the Request Log — empty while it is switched off). Grouped only by day, platform (google, meta, …), utmSource, utmCampaign and landingPath.
AdsMetricsResponseConversions
Always sent. An AdsMetricsResponseConversions. Conversion events. value sums restated values and leaves out retracted events. Grouped by platform (a destination such as google-ads), each row adds delivery outcomes.
Nothing to catch: the SDK retries what is safe, and throws the rest as the classes below; catch only what you want to react to (see Errors and testing).
400
The request is not valid. data.errors lists each problem with the path of the parameter or body field it concerns.Retried first: No. Read: errors (field → messages), siteMessage.
401
The API key is missing, malformed, unknown, disabled, expired or archived (invalid), or a request that must be signed — by the route, or by the key’s own signing mode — has a missing, stale or wrong signature (an upload signs its SHA-256, declared in X-Fetchski-Content-SHA256, in the body’s place) (unauthorized).Retried first: No. Read: siteMessage, errorName, data.
403
The API key lacks the scope this route needs (the message names it), or the key is used from an address outside its allowlist.Retried first: No. Read: siteMessage, errorName, data.
404
Nothing with this identifier — or the caller may not use the Data API at all (anonymous visitors and non-admin sessions get 404 so the API is not advertised). A write while conversion tracking is switched off also answers 404.Retried first: No. Read: siteMessage, errorName, data.
429
The key used up its reads- or writes-per-minute limit (set per key; defaults 600 / 120). Still, after the client’s own waits and retries.Retried first: Yes: the client waits Retry-After (1 s when absent; over 60 s it gives up at once) and retries, up to retries times (2 by default). Read: retryAfter (seconds, or null), siteMessage.
5xx
The site failed (or something in front of it did). Its logs say why.Retried first: A 502, 503 or 504: yes, after 0.5 s then 1 s. A 500: no. Read: siteMessage, errorName, data.
no answer
No answer: DNS, a refused connection, TLS, or the timeout (15 s per attempt by default).Retried first: Yes, after 0.5 s then 1 s. Read: reason, neverConnected.
not sent
The client refused to send it (e.g. a path segment of ..); the site never saw it.Retried first: No. Read: reason (what to change).
any other
Any other status, or a success whose JSON doesn’t match this SDK version’s types (update the SDK).Retried first: No. Read: reason, status.
setup
sites.forSite('acme') named a slug your sites (createSiteClients()) don’t have.Retried first: No: nothing was sent. Read: message, slug.
setup
The client’s settings are wrong: no FETCHSKI_ATTRACT_URL (or baseUrl), or a malformed API key.Retried first: No: nothing was sent. Read: message (what to fix).

Behavior

  • Access: an API key with ads-metrics:read — or its group master ads:all, or admin:all — or a signed-in user holding the analytics:view permission. Anonymous callers get 404.
  • Rate limit: the key’s own reads-per-minute limit, set when the key is created (default 600); over it, 429 with Retry-After. The client waits and retries for you; you see RateLimited only if that runs out.
  • Retries: a read is safe to repeat: the client retries it on no answer, a 502/503/504 and a 429.
  • Timeout: 15 s per attempt by default; raise timeout (milliseconds) on the client for longer.

Test it

It calls the function above with a fake client: the fake answers every call with a valid example, so nothing leaves your machine and no settings or key are needed. Run it with node --test.
tests/adsMetrics-getAdsMetrics.test.ts

GET /ads-metrics

The endpoint this calls, in the API reference: the HTTP request and answer, and every rule the site checks.