DSP Integration Guide — send us traffic

SavItUp LLC · Demand-side partners · Updated September 2026

Machine-readable version: /docs/dsp.md · Index for agents: /llms.txt

Overview

How the tracked link behaves

  1. A visitor opens https://savitup.com/go/<id>.
  2. SavItUp records one click event and 302-redirects to https://savitup.com/?c=<id>.
  3. If the visitor installs and signs up, the campaign is attributed: automatically via the carried code, or when they type the 16-character code at signup.
  4. Deactivated or unknown ids still redirect but record nothing — dead campaigns stop counting instantly.

What SavItUp stores about your traffic — and what it never stores

Stored per click: campaign id, timestamp, coarse device class (ios/android/desktop/other), coarse region, and the referrer domain when present.

Never stored: IP addresses, user-agent strings, cookies, or any cross-site identifier. Nothing to place on your side, nothing extra to disclose beyond a standard outbound link.

Attribution semantics (exact)

Reporting

Per-campaign clicks and attributed signups are tracked in SavItUp's systems; your SavItUp contact shares performance on request or an agreed cadence. Code-entry attribution is exact; link-through attribution is labeled correlated.

QR codes

Any QR encoding your /go/ link works — SavItUp can generate one. Print and offline placements attribute exactly like web links.

Contact

support@savitup.com — include “DSP integration” in the subject.