Skip to main content
There are two APIs:
  • The Appeeky API (https://api.appeeky.com/v1/analytics/...) to turn Analytics on, manage keys, settings and smart links, and read every dashboard view. You call it with your Appeeky API key or a signed-in dashboard session.
  • The ingest endpoint (https://ingest.appeeky.com/v1/ingest) that the SDK sends events to, with the app’s publishable key.

Authentication

Appeeky API requests use your normal Appeeky API key (X-API-Key or Authorization: Bearer), or your dashboard session in the web app. See Authentication.
Analytics endpoints cost 0 credits.
:appId is the app’s id in My Apps (app_id). The app must be in your apps, and every endpoint except enable needs Analytics to be on for it. Responses use the standard envelope: { "data": … }.

Endpoints

Apps and keys

Settings

Dashboard views

Every number is defined in Metrics. Field rules are on Smart Links.

Query Parameters

With any filter, revenue only counts customers linked to a matching install. Sales without a linked install drop out.

Responses

Dashboard

conversion is install → paid as a share (0.041 = 4.1%). change is relative (0.093 = +9.3%) and null when the previous value is 0.

Breakdown

A null key is the empty value: for source, sales with no linked install. revenueUsd is null for entry and exit.

Funnel

saved is false when the app uses the default funnel.

Retention

retention is null for range=today. values[n] is the share of the cohort active in period n, and null for periods that have not started.

LTV

clicks counts clicks in the period. installs counts installs attributed to the link and first seen in the period, and revenueUsd is all revenue from those installs so far.

SKAdNetwork

See SKAdNetwork for what each field means.

Errors


Ingest Endpoint

The SDK sends batches here. You only need it if you write your own client.
Limits:
  • Up to 100 events per batch and 512 KB per request.
  • Events older than 30 days, more than 10 minutes in the future, or with properties over 4 KB are dropped and counted in dropped; the rest of the batch is kept. A body that does not match the format (for example an invalid event name) is rejected with 400.
  • 600 batches per minute per publishable key.