Integration Types - OnlyTraffic

There are three ways to serve creator cards. They differ in who renders the cards and where the click link on your page points.

	Widget	Backend + First-party	Backend (S2S)
Cards rendered by	our script, in the browser	your server	your server
Click link on your page	our tracking domain	your own domain	our tracking domain
Click resolved by	the visitor’s browser	your server, through the resolve API	the visitor’s browser
External ad links in your HTML	yes	none	yes
Setup	paste a snippet	API fetch + a small relay endpoint	API fetch
Best for	regular pages, quickest start	pages that rank in search, ad-block-sensitive placements	server-rendered pages where the link profile doesn’t matter

Paste one snippet where the cards should appear; rendering, impressions and clicks are handled for you. Layouts, themes and custom templates are covered in Widgets.

Backend (S2S)

Your server fetches creatives as JSON with the widget API key and builds its own HTML. Cards link to the ready-made tracking URLs from the response. Rules and examples: Widgets, Backend (S2S).

Backend + First-party

Server-side rendering like S2S, plus first-party click links: every link on your page stays on your own domain, and your server resolves each click through our API before redirecting the visitor. Why choose it:

Clean link profile. Your HTML contains no external ad links, so pages that rank in search carry no ad-network footprint.
Ad blockers can’t cut the click path. A same-origin link can’t be blocked without breaking the site itself.
You control the referrer. The page URL travels in the resolve call explicitly, and on the final redirect you decide what the destination site sees: a Referrer-Policy: no-referrer header hides your domain entirely.

Every click still goes through OnlyTraffic: the token in each card comes from us, and a click counts (and pays) only after your server resolves it.

How it works

Fetch creatives

Same request as Backend (S2S): call the widget endpoint from your server with the X-Api-Key header, forwarding the visitor’s uip, uua and page.

Render first-party links

Each creative includes a click_token. Link the card to your own route, for example https://yoursite.com/go?t=<click_token>. Don’t use click_url in this mode; the impression pixel (impression_url) works the same as in S2S.

Resolve the click

When a visitor hits your route, call the resolve endpoint server-to-server:

GET https://otsync.com/re?t=<click_token>&uip=<visitor IP>&uua=<visitor user agent>&uref=<page URL>
X-Api-Key: <widget API key>

Redirect

The response contains the destination URL. Reply 302 Location: <url>. Optionally add Referrer-Policy: no-referrer so the destination site doesn’t see your domain.

What to send on every resolve

Field	Required	What it is
`t`	yes	The `click_token` from the creative
`X-Api-Key` header	yes	Your widget API key; proves the call comes from your server
`uip`	yes	The visitor’s IP address
`uua`	yes	The visitor’s User-Agent
`uref`	yes	URL of the page the click happened on
`asn`	no	The visitor’s network ASN. On Cloudflare, expose `ip.src.asnum` with a Transform Rule header and forward it
`country`	no	ISO2 override; normally resolved from `uip`
`X-OT-Bot-Score` header	no	Cloudflare bot score, when your plan provides it
`X-OT-Verified-Bot` header	no	Cloudflare verified-bot flag (`1` or `true`)

uip, uua and uref must describe the visitor’s request to your site, not your server. Click validation, geo stats and uniqueness run on what you forward; clicks with missing or fabricated context are flagged and not paid. The optional fields let more of the fraud filtering work for your traffic, which keeps your placement attractive to advertisers.

Call the resolve endpoint from your server only, on every click, and never cache the response. One token resolves to one billable click; repeats redirect but don’t pay.

The response

{ "url": "https://...", "billable": true, "reason": "", "via": "proxy" }

url: where to redirect the visitor. Always present for a live token. null means the token expired: redirect to a page of your own instead.
billable: whether this click passed validation and counts toward earnings. Diagnostic only; redirect either way.
reason: why a click didn’t pay. Common values: duplicate (token already resolved), not_unique (same visitor and creator within the uniqueness window), stale_token, bot markers. ref_not_forwarded is a warning: the click still pays, but uref was empty and you should fix the integration.

Relay example

The route path (/go here) is your choice.

app.get('/go', async (req, res) => {
  const visitorIp = req.headers['cf-connecting-ip'] || req.ip;
  const url = 'https://otsync.com/re?t=' + encodeURIComponent(req.query.t || '')
    + '&uip=' + encodeURIComponent(visitorIp)
    + '&uua=' + encodeURIComponent(req.headers['user-agent'] || '')
    + '&uref=' + encodeURIComponent(req.headers['referer'] || '');

  const r = await fetch(url, { headers: { 'X-Api-Key': 'YOUR_WIDGET_API_KEY' } });
  const data = await r.json();
  if (!data.url) return res.redirect(302, '/');

  res.set('Referrer-Policy', 'no-referrer');
  res.redirect(302, data.url);
});

<?php
$visitorIp = $_SERVER['HTTP_CF_CONNECTING_IP'] ?? $_SERVER['REMOTE_ADDR'];
$url = 'https://otsync.com/re?t=' . urlencode($_GET['t'] ?? '')
     . '&uip=' . urlencode($visitorIp)
     . '&uua=' . urlencode($_SERVER['HTTP_USER_AGENT'] ?? '')
     . '&uref=' . urlencode($_SERVER['HTTP_REFERER'] ?? '');

$ch = curl_init($url);
curl_setopt_array($ch, [
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER     => ['X-Api-Key: YOUR_WIDGET_API_KEY'],
    CURLOPT_TIMEOUT        => 5,
]);
$data = json_decode((string) curl_exec($ch), true);
curl_close($ch);

$dest = $data['url'] ?? null;
if (!$dest) { header('Location: /', true, 302); exit; }

header('Referrer-Policy: no-referrer');
header('Location: ' . $dest, true, 302);
exit;

uref normally comes from the Referer header of the same-origin click. If your site sets a global no-referrer policy, append the page URL to your click links yourself (for example /go?t=...&p=<page URL>) and forward that value as uref. The widget form contains full copy-paste examples (page render plus relay) and a ready prompt for an AI assistant.

Which one to pick

The page ranks in search, or you want a clean outbound-link profile: Backend + First-party.
You render server-side and want the fastest backend setup: Backend (S2S).
Everything else: Widget.

​Widget

​Backend (S2S)

​Backend + First-party

​How it works

​What to send on every resolve

​The response

​Relay example

​Which one to pick

Widget

Backend (S2S)

Backend + First-party

How it works

What to send on every resolve

The response

Relay example

Which one to pick