Skip to main content

Register your account here

Start your 14 days free trial.

Already have an account? Sign in

A-TRACK event analytics illustration
What We provide

The best attribution data, ready to use

Traffic Source Parsing

Capture where a user came from and turn referrers, UTM tags, campaigns, and landing URLs into structured data.

Raw Acquisition Data

Return the original signals alongside parsed fields so your product can store, analyze, and reuse the raw marketing data.

Client Context Capture

Collect browser, device, locale, viewport, timezone, referrer, and runtime context automatically on the client.

Identity Resolution

Start anonymous, generate a UUID automatically, and keep all future events linked to that user across the full lifecycle.

Realtime Event Ingestion

Ingest user events with consistent payloads from frontend and backend SDKs, then associate them with the right UUID.

Parsed Attribution Output

Normalize incoming traffic data into clean fields your application can use immediately without extra transformation code.

SSR and Backend Ready

Pass server-known values like IP address, user agent, and referer from Node, Python, Go, Rust, PHP, Swift, .NET, and more.

Raw Data Back to You

Send data in, let A-TRACK parse and enrich it, then return the raw structured output so you can power your own attribution logic.

A-TRACK delivery channels illustration
Powerful Options

Get your data where your team already works

A-TRACK does not lock your attribution data inside one dashboard. We deliver structured output back to your stack through APIs, SQL access, backup files, and real-time webhooks.

REST API Access

Query user attribution, raw payloads, and parsed traffic data directly from your backend or internal tools.

SQL Database Access

Work with attribution records in SQL for analytics, joins, internal reporting, and custom data pipelines.

Backup Files

Export snapshots or scheduled backup files so your team always has a portable copy of collected raw and parsed data.

Webhooks

Push enriched user and event data to your systems in real time whenever new attribution signals are captured.

Pricing

Simple plans for attribution workloads

Choose the setup that matches your traffic volume. Every plan includes the full data layer, delivery options, and a 99.999% uptime SLA.
PERSONAL

$25

Per Month
  • 1 vCPU / 1 GB RAM
  • Storage minimum: 10 GiB
  • Connection limit: 50
  • 10,000 requests daily
  • Geolocation Data
  • Commercial Blocklists
  • ASN Data
  • Company Data
  • VPN Detection
  • ML IP Reputation Scores
  • Data Downloads
  • 99.999% uptime SLA
STARTUP

$49

Per Month
  • 2 vCPU / 4 GB RAM
  • Database size: 50 GiB
  • Connection limit: 150
  • 50,000 requests daily
  • Geolocation Data
  • Commercial Blocklists
  • ASN Data
  • Company Data
  • VPN Detection
  • ML IP Reputation Scores
  • Data Downloads
  • 99.999% uptime SLA
PRO

$120

Per Month
  • 4 vCPU / 8 GB RAM
  • Database size: 150 GiB
  • Connection limit: 300
  • 100,000 requests daily
  • Geolocation Data
  • Commercial Blocklists
  • ASN Data
  • Company Data
  • VPN Detection
  • ML IP Reputation Scores
  • Data Downloads
  • 99.999% uptime SLA

Own your attribution data from first touch to export.

Capture traffic source signals, normalize them into structured fields, and get raw outputs back through the delivery channel that fits your stack.

See the API docs

API, SQL, backups, and webhooks from one ingestion pipeline

Collected User Data

A-TRACK groups raw inputs into clear data layers so your team can work with attribution, geo, device, and client context without digging through noisy payloads.
UTM and campaign data
source, traffic_source, keyword, campaign, adset, ad metadata
Click identifiers
gclid, wbraid, msclkid, fbc, fbp, ttclid, ttp
Query and landing parameters
incoming query params, raw landing URL, referrer, parsed source fields
Geo and IP intelligence
ip, country, region, organization, ASN, ISP, IPv6, timezone
VPN and hosting signals
hosting provider detection, satellite provider flags, commercial blocklists, reputation layers
Company and network data
organization names, company ownership, network identity, autonomous system data
Browser and app environment
browser name, family, platform, in-app browser, bot and device classification
Device and display context
device family, model, mobile or desktop type, viewport, screen size, pixel ratio
Locale and user context
user locale, timezone, timezone offset, language, regional client context

Pipe attribution data into your stack,
keep the raw source signals,
and build on top of your own logic.

Read the documentation

Structured delivery through API, SQL, backups, and webhooks