Tracked.it

Overview

Tracked brings ad tracking and landing pages into the same campaign workspace. The product follows traffic from its source through a landing-page variant to an offer click and conversion, so teams can read campaign results alongside the page that served each visitor. It is positioned for media buyers and teams running paid traffic, with spend and profit views when the supporting cost data is available.

MTB’s scope covers product engineering, data workflows, and dashboards.

The challenge

Campaign work often crosses a tracker, page host, editor, and report. That makes it harder to connect a campaign result with the exact page version and message a visitor saw. Tracked addresses that handoff by keeping campaign context, page variants, conversion events, and reporting together.

Our approach

Teams can upload an existing HTML page or ZIP, serve it on a custom domain, and direct traffic to a selected page or offer. Weighted destinations support page tests, while campaign rules can choose what to serve based on incoming request context.

Conversion callbacks connect back to the originating click; event mapping and eligible callback backfills help reconcile provider event names. A visitor timeline places impressions, offer clicks, conversions, and postbacks in sequence, with session, device, and campaign context for investigation.

Page edits can be made in the visual editor and reviewed before publishing. The public site also presents optional AI editing and MCP access to analytics, while spend sync and network feedback depend on provider and account configuration. Because the visitor view can show the sequence behind a conversion, a buyer can move from a summary count to the events that formed it. Page comparison and the postback trail remain connected to the same campaign context.

The outcome

The resulting product is a single campaign workflow connecting page delivery, traffic allocation, attribution, and performance review. Teams can use that context to decide what page message to test next, then inspect results alongside the corresponding campaign events. The workflow keeps comparison, visitor-path review, and page changes in one context, giving operators a clear next move: keep, edit, or test another variant.