Skip to Content
Developer DocsTroubleshootingOverview

If something looks wrong, scan the table below first — most issues match one of these symptoms exactly.

Find your symptom

SymptomPage
A click on a short link didn’t appear in analyticsTracking issues
A signup happened but no lead event was recordedTracking issues
A sale was tracked but no partner got the commissionTracking issues
Browser console shows a CORS error from api.revroute.ruTracking issues
The webhook fires from the dashboard test but not from real eventsWebhook not firing
My endpoint receives the webhook but the signature check failsWebhook not firing
The dashboard says my webhook is “disabled”Webhook not firing
Webhook deliveries time outWebhook not firing
API call returns 401 / 403API errors
API call returns 422API errors
API call returns 429API errors
Random 5xx from the APIAPI errors
Custom domain is stuck on “Verifying DNS”Domain config
SSL certificate is pending for hoursDomain config
CNAME conflicts with an existing DNS recordDomain config
Subdomain works in browser but redirects don’t fireDomain config

General debugging steps

Before opening a support ticket, three commands solve most issues:

# 1. Make sure the API key is valid and you're hitting the right workspace curl https://api.revroute.ru/workspaces/proj_xxx \ -H "Authorization: Bearer $REVROUTE_API_KEY" # 2. Check the redirect path for your short link curl -I https://revroute.ru/your-key # 3. Inspect what the analytics script actually sent # Open DevTools → Network → filter "api.revroute.ru"

If a request fails, the response body always contains an error.code and error.message. Copy both into your support ticket — that gets you to root cause in one round-trip.

Where to look in the dashboard

  • Events tab (/<workspace>/events) — every click, lead, and sale in real time, with the raw payload
  • Webhook logs (/<workspace>/settings/webhooks/<id> → Logs) — every delivery attempt with request and response bodies
  • API logs (/<workspace>/settings/tokens/<id> → Logs) — recent requests made with a specific API key, status codes, and timings

These three views resolve ~80% of “why isn’t this working” questions before you have to read code.

Status page and known issues

  • Status: status.revroute.ru 
  • Incident history: the status page also lists past incidents — if your problem started at a specific time, check there first.

If everything in the dashboard looks healthy and the status page is green, the issue is almost certainly in your configuration. Walk through the relevant page below.

Last updated on