Events and privacy

SiteCargo accepts the following events:

Event	Purpose
install	Installs and the retention cohort
session_start	Session start
app_open	App open
page_view	Page view
push_open	Push notification open and CTR
purchase	Confirmed purchase
custom	Additional app event

Not every event has a separate report.

Event date

After a 201 Created response, the event is available the next time the report loads. A page that is already open does not refresh automatically.

If the app sends occurred_at, the event is assigned to that date. Otherwise, the request receipt time is used. A delayed event with an earlier date updates that past day and will not appear in a range that excludes it.

Stored data

The server hashes the installation identifier, session identifier, and IP address. Analytics does not store the original values of these fields.

The server determines the country from the IP using a local DB-IP Country Lite database, without calling an external API. The result is cached for one day by IP hash; events store only the country code and name.

Event type and time, country, platform, device type, app version, URL, referrer, source, user agent, and the meta object may be stored in plain text.

Do not send names, contact details, passwords, tokens, cookies, payment details, exact addresses, coordinates, or other sensitive information in the URL, referrer, source, or meta. Analytics use must be disclosed in the app's privacy policy and store data declarations.