API reference gaps in Traffic
Endpoints in this subsystem with no dedicated auto-generated reference page yet.
The auto-generated API reference is built from the OpenAPI schema and covers most of this product's admin surface. One endpoint in Traffic isn't represented there yet:
GET /api/admin/clicks-report
The filterable, paginated clicks report described in
Check a campaign's clicks for fraud has no
reference page of its own. getStats
documents a different, wider endpoint (GET /api/admin/stats) — funnel/attribution aggregates,
not this row-level click log — so don't mistake one for the other.
Query parameters: click_id, external_click_id, country, source, domain, code,
unique_only, ad_platform, fraud_only, period_from, period_to, page, page_size,
link_domain, link_codes, account_scope, account_id. Add format=csv to stream every
filtered row (ignoring pagination) as a CSV download instead of a JSON page.
Response shape: rows (one entry per click: timestamp, click id, external click id, country,
source, domain, code, subnet, unique flag, converted flag, plus the phase-2 capture — user agent,
referrer host, UTM source/medium/campaign, derived ad platform, derived fraud flag), total,
page, page_size, totals (clicks/unique/converted/fraud), trend (per-day click
counts), sources, platforms.
What's next
Back to Traffic, clicks & redirect for the tasks this endpoint supports.
Hide a partner smart link's real address from the visitor
Turn on the relay proxy so a partner smart-link URL never appears in the visitor's redirect chain — with an automatic fallback if the partner's server is slow or down.
Troubleshooting
Common symptoms in the click/redirect pipeline, their real cause, and where to look in code.