Routy

Traffic Source — Webhooks

The Webhooks tab is the default view when you open a traffic source. This is where you push conversion events from Routy out to your other tools.

What a webhook is

A webhook is an automatic message Routy sends to a URL you choose, every time a conversion happens on this traffic source. Instead of you logging in somewhere to check results, Routy delivers each conversion in real time to wherever you need it — Zapier, Google Ads, Facebook Ads, a custom endpoint, an analytics tool, and so on.

In short: conversion happens in Routy → Routy calls your webhook URL → your tool receives the data.

The webhooks list

Each row is one webhook configured for this traffic source:

Column Meaning
Name A label you give the webhook so you recognise it.
Status Enabled — active, fires on matching conversions. Disabled — configured but not sending.
Conversion Type Which conversion events trigger it. "All" means every type, including new ones added later.
HTTP Method How the data is sent — POST or GET.

Use search, the status / conversion-type filters, and column settings to manage a long list. Each row also has a ⚠ issue indicator if Routy has detected a delivery problem — click it to see the details.

Adding a webhook

Click Add to open the Create Webhook form. It has two steps.

Step 1 — Source

  • Traffic Source — fixed to the source you're on.
  • Event Source — where the conversions come from. Pick All, Google Ads, Facebook Ads, or Custom.
    • If you choose Custom, enter your own source value. Tip: put utm_source in your landing-page URL (e.g. outbrain, taboola) so Routy can tell custom sources apart.

Step 2 — Details

  • Name — something recognisable, e.g. Google Ads – FTD (2–100 characters).

  • Conversion Events — pick one or more conversion types. Leave it empty to fire on all events (including conversion types added in the future).

  • Webhook URL — the endpoint that receives the call. You can drop tokens into the URL to pass conversion data — type ${ and pick from the list. Available tokens:

    ${clickId} · ${trafficSourceId} · ${affiliateId} · ${accountId} · ${eventTime} · ${eventName} · ${eventValue} · ${conversionId} · ${id} · ${status} · ${attempts} · ${createdAt} · ${updatedAt}

  • HTTP Method — POST for most services (recommended), or GET.

Save and the webhook appears in the list. You can Edit it any time from its row.

Testing a webhook

You have two ways to check a webhook works before relying on it:

  • Simulate (on the webhook's row) — sends a test conversion event straight to that webhook's URL, so you can confirm the receiving tool gets it.
  • Send (top of the page) — manually trigger a webhook delivery using one or more real Click IDs (UUIDs, comma-separated). Useful for pushing a specific click through on demand.

Delivery history

Click History on a webhook's row to open its Logs — every delivery attempt for that webhook, with status (success / failed / pending), retry/attempt info, and the ability to resend failed deliveries.

Setup Guide (new to webhooks?)

If you're setting webhooks up for the first time, Add can open a 5-step Setup Guide that walks you through a typical Zapier + Google Ads flow:

  1. Create a Zapier webhook — in Zapier, add a Zap with a Webhooks by Zapier → Catch Hook trigger and copy the URL it gives you.
  2. Add the webhook in Routy — paste that URL into the Create Webhook form here.
  3. Simulate a conversion — send a test event and continue the Zap setup in Zapier (Send Offline Conversion → connect Google Ads, map GCLID, pick the conversion action).
  4. Connect to Zapier — map the timestamp, value, and currency fields.
  5. Turn on & verify — switch the Zap on. Real conversions can take 24 hours or more to appear; check Zap History for successes.

Common questions

"My webhook isn't sending anything"

Check its Status is Enabled, and that the Conversion Events you selected actually match the conversions coming in (or leave events empty to catch all). Then use Simulate to confirm the URL itself is reachable.

"How do I know if deliveries are failing?"

Open History on the webhook's row — failed attempts are listed there and can be resent. A ⚠ indicator on the row also flags detected problems.

"Should I use POST or GET?"

POST for most services — it's the default and what tools like Zapier expect. Use GET only if the receiving endpoint specifically requires it.

"What's the difference between Simulate and Send?"

Simulate sends fake test data to one webhook. Send triggers delivery using real Click IDs you provide.