How Trakbolt works
The big picture
The tracking script records each visit to your site with where it came from (ad click, campaign, search, social, email). Your server sends the things that happen after: leads, checkouts, orders, refunds. Trakbolt joins the two into one journey per person, credits the sale to the touches before it, and sends the sale back to the ad platforms that earned it.
Key terms
| Term | Meaning |
|---|---|
| Visit (session) | A stay on your site. A new visit starts after 30 minutes without a page view (the default; your workspace can change it). |
| Touch | A visit, or an ad click your server reported, with its channel and campaign. Touches are what attribution credits. |
| Person | Everyone Trakbolt knows is the same buyer: their browsers, their ids from your server, their orders. |
| Join key | An id your system adds to links into your app (for example ?ref_id=…), echoed back in your server events, so a later order joins the visit. |
| Channel | Where a touch came from: an ad platform, organic search, social, email, referral or direct. |
| Order | A purchase from your server (or the page), with its value, refunds and status. |
How a sale finds its click
An order joins a visit in one of these ways, shown on every event as matched_by:
| matched_by | How |
|---|---|
visitor_id | visitor id |
join_key | join key |
contact | contact |
order | order id |
matched_late | joined later |
none | no visit |
Why server-side
Browser pixels miss sales: ad blockers, Safari's tracking limits, a checkout on another domain, or a buyer who comes back on another device. Trakbolt sends each sale from the server with the click id and hashed contact the platform needs to match it, so each platform sees the sales it drove, each counted once.