Tracker

See which ads bring visits and conversions, what each conversion is worth, and send your conversions back to Meta, TikTok and Snapchat.

Your tracking domain

Tracking runs on a domain of your own. ScalingDeck never offers a domain of its own for tracking.

1. In Tracker, Setup, Domains, click + Connect a domain.
2. Type a Subdomain (for example go.yourbrand.com, never yourbrand.com alone), pick its Workspace, and click Next.
3. The DNS records window shows two records. Add both, exactly as shown, where your domain's DNS is managed (usually where you bought the domain):
   • A TXT record proves the domain is yours.
   • A CNAME record points the subdomain at ScalingDeck.
4. Click Check now, or Later. ScalingDeck keeps checking on its own.

Remove on a domain's row takes it off, after asking. Use it for a mistyped domain or one claimed by another organization. Pages using a removed domain stop being tracked.

"DNS records" on a domain still waiting or connecting shows the records again, with a note when something is wrong. Use a subdomain of the same domain as your landing pages.

The script and the click ID

Once a domain is Proven, Tracker, Setup, Script shows The line for pages built elsewhere. Copy it and paste it into every landing page your ads send people to.

On each visit the script gives the visitor a click ID, a code that is theirs alone, and adds it to every form on the page. The click ID ties a visit to the conversions that come later.

Bots and link previews (the platforms' crawlers, automated browsers, uptime monitors) are kept but never counted as visits. See them under Visits, Bots and previews.

Setting up the link in your ad

1. Use your landing page's own address, the page that carries the script.
2. Add these parameters, each filled with the platform's own dynamic value, so the platform puts in the real id at each click:
   • sd_campaign: the campaign ID (on Meta, {{campaign.id}}).
   • sd_adset: the ad set ID (on Meta, {{adset.id}}).
   • sd_ad: the ad ID (on Meta, {{ad.id}}).
   • sd_placement: the placement (on Meta, {{placement}}).
   • sd_src: meta, tiktok or snapchat.
3. Publish the ad.

Meta, TikTok and Snapchat add their own click ID to every click, so the platform is known even without sd_src. The names other trackers use (campaign_id, adset_id, ad_id...) work too. Cost joins only ads in the ad accounts you connected (Connections).

Conversion types

Anything can be a conversion. Name your own in Tracker, Setup, Conversion types (+ New conversion type): a booked call, a sign-up, whatever your offer pays on. Every organization starts with two:

• Lead: comes from leads. Counts as a conversion, not toward revenue.
• Won: comes from leads marked Won. Counts toward revenue, not as a conversion.

Each type has:

• Counts toward revenue and Counts as a conversion: two switches, also in the table.
• When a postback has no value: No value, or a Default value.
• Flag values above: a larger value is marked "Large value". It still counts; the flag asks you to look.

How conversions arrive

• Leads. A lead whose form carried a click ID becomes a Lead conversion. Marking it Won adds a Won conversion with its value; clearing Won, or Not a fit, reverses it. Saving Won again with a new value updates the conversion. See Leads.
• Postbacks from networks, offers and other tools. In Tracker, Setup, Postbacks, click + New postback source, give it a Name and pick its Network (Everflow, CAKE, TUNE (HasOffers) or Any other tool). Pick a conversion type, Copy the Postback address and paste it into the network. It already holds the network's own placeholders. The table below it shows what a postback carries: the click ID and the type are needed; value, currency, transaction ID and status are optional.
• Updates from buyers: what a buyer tells you later about a lead. See Updates from buyers and Signals below.

The click ID must reach the network. A postback can only send back the click ID the network received, so pass it on with each click to the offer.

One transaction, one conversion. Postbacks with the same transaction ID update one conversion (approved, pending, rejected, refunded, or a new amount). Without one, each postback is its own conversion.

Replace token asks first, then gives a new postback address and stops the old one at once.

Conversions

The Conversions tab lists each conversion; click one for its History. Gross revenue adds the values of types that count toward revenue, Reversed is what was rejected or refunded, Net revenue is what is left. Not matched means it arrived without a click ID: kept, but not tied to an ad. Money is in US dollars for now. These numbers cover the whole period. The list shows the newest 200 and says so when there are more.

If Tracker's data store is briefly out, visits and conversions wait and go in by themselves when it is back, keeping the time they arrived. After 24 hours of trying they appear in Needs review.

Signals

A signal sends your conversions back to Meta, TikTok or Snapchat, so the platform learns who converts. Set it up once in Signals, in the sidebar, + New signal.

• Signal: a Name, its Workspace, and Default: each platform can have one default signal in a workspace. It sends for that platform's campaigns without a signal of their own.
• Sends to: the Platform, the pixel or dataset ID, and the token. The token is never shown again ("Key saved"). Test event code (optional) is for Meta and TikTok.
• Events: + Add an event picks a conversion type. Choose what it is sent as (a platform event, or Its own name on Meta and TikTok), When (When it arrives, Once approved) and Value (Send its value, No value).
• Updates from buyers: Copy the address next to Buyers send updates to and give it to your buyers. + Add a rule says what a buyer's status is sent as. Statuses without a rule are sent as they come (on Snapchat, as Custom event 1) or not at all. Buyers sent lists statuses that arrived; click one to give it a rule.
• Leads: the platform already has Instant Form and WhatsApp leads (Meta) and Snapchat form leads. Choose Don't send, or Send later conversions only to send what happens to them later, like Won.
• Campaigns: + Assign campaigns picks the ad campaigns it sends for. A campaign has one signal; assigning it here takes it from another.

Send a test never counts as a real conversion. On Meta and TikTok it needs the test event code and shows in the platform's Test Events.

A refused token: if a platform refused conversions because the token was bad, replace the token. Those from the last 7 days are sent again by themselves.

Snapchat's PURCHASE needs a value. Keep the value on for it, or choose another event. A lead marked Won with no amount on a PURCHASE event is refused by Snapchat.

What is sent: conversions tied to an ad click, never rejected or refunded ones. A lead from no ad at all goes through the default signal, matched by its email or phone. If the workspace has a default for more than one platform, that lead is not sent. Recent sends shows each one: Sent, Waiting, Retrying, Refused, Failed (for example a buyer's update whose value can't be read clearly, such as N/A or €25: that one is not sent, the others are. $25 and 1,000 are read fine), Expired, or Not sent: too late (platforms refuse events older than 7 days). Failures ring the workspace admins' bell once a day per signal (Notifications). Archive signal is in the ⋯ menu; nothing is deleted.

Visits

Tracker opens on Visits. Spend, visits, conversions and revenue together are on Reports.

Visits lists the newest visits with their source, campaign, ad, landing page, country, device and any conversion.