CLItrail Docs

Changelog

What changed in CLItrail, newest first.

#

#Organisations, sign-in and plans

  • Organisations with owner, admin, member and viewer roles, checked on every request; invitation links for a verified email, valid once for 7 days; an organisation switcher. Every existing account became the owner of its own organisation, with its websites.
  • Sign in with Google or a passwordless email link through Firebase Authentication on the hosted service. Existing accounts link on the first sign-in with the same verified email.
  • Plans: Free, Standard at $99 a month and Enterprise at $499 a month, billed monthly through Stripe, with limits for every plan, a Usage card and a monthly quota of tracked events. Free performs no matching at all.
  • Install paths, each with its own hook: 1 on Free and Standard, up to 10 on Enterprise.

#Attribution

  • Reconstruction from the network, time, OS, time zone, language, browser and architecture replaces network matching. On by default on paid plans, always labelled probable, with its signals shown.
  • Safari and External reasons for installs nothing could link.
  • Browser, system and device breakdowns with logos, on every plan. The hook now reports the install path, architecture, browser families present, default browser, time zone and language.
  • The hook searches the Snap, Flatpak and XDG profiles of Firefox and Chromium and Zen’s profiles on Linux, and Chrome Dev and Canary on macOS.

#Destinations

  • X Ads, through the X Conversions API with twclid; the website tag now reads twclid.
  • Google Ads with your own Google Cloud service account key. The “Link Google Ads account” sign-in is gone: every destination is set up by pasting credentials.
  • Destinations are part of the paid plans, with a limit per website.

#Logs and security

  • Logs of every request received and sent, with exact bodies and credentials redacted, an install trace and CSV or NDJSON export.
  • Log streams on Enterprise, to Amazon S3, S3-compatible storage or a signed webhook.
  • Credentials moved to a separate secret store, apart from the main database and its keys.

#Docs and help