Documentation

curl -sS -X POST 'https://api.infralytiqs.com/il/token' \
  -H 'companyId: 665f1c9e4a2b3d0012ab34cd' \
  -H 'tenantName: acme' \
  -H 'clientKey: 3f9a1c7d5e2b8064af31c9d2' \
  -H 'clientSecret: 9d41e7c8b25a06f3ac18de74b09f52a6c3e81d47f265ba90c1d38e07f4b2a659'

# The JWT comes back in data.token, signed with your clientSecret.
# Send its tokenId claim as x-il-token on read requests.
#
# The secret grants read access to your reports, so it belongs in
# server-side configuration and never in a browser bundle or a mobile app.

curl -sS -X POST \
  'https://api.infralytiqs.com/il/analytics/acme/acme-www/report-query' \
  -H 'Content-Type: application/json' \
  -H 'x-il-token: 1f4c8a92-6e30-4b57-9d21-c8a70f3b5e14' \
  -d '{
        "query": {
          "metrics": [
            { "agg": "count", "label": "Page Views" },
            { "agg": "uniqExact", "field": "anonymous_id", "label": "Unique Visitors" }
          ],
          "dimensions": [{ "field": "page_path" }],
          "filters": [{ "field": "event_type", "op": "eq", "value": "page_view" }],
          "timeRange": { "preset": "last_7_days" },
          "orderBy": { "field": "Page Views", "dir": "DESC" },
          "limit": 25
        },
        "timezone": "Europe/London"
      }'

# Rows come back with dim_0, metric_0, metric_1 keys and a columns array
# describing them.

-- The escape hatch that makes everything else safe to adopt: when the
-- console cannot express your question, the data is still right there.

SELECT
    page_path,
    count()                  AS page_views,
    uniqExact(anonymous_id)  AS visitors,
    uniqExact(session_id)    AS sessions,
    round(count() / uniqExact(session_id), 2) AS views_per_session
FROM website_events
WHERE event_type = 'page_view'
  AND event_date >= today() - 7
GROUP BY page_path
ORDER BY page_views DESC
LIMIT 25;

-- Nothing about this query goes through Infralytiqs. It is your database,
-- your credentials and your SQL client.