Conversion Event Router — Case Study | brdz.net
Case study

A post office for “this visitor became a customer”

Performance marketing

Confidential 3–4 weeks Python FastAPI SQLite Telegram

Challenge

When a visitor from an ad became a customer, several websites needed to hear about it. Partners retried. Events arrived twice, or not at all. Someone had to grep logs to see why a lead “disappeared”.

Solution

A small always-on service: one URL for partners, a log of every incoming event, a forward to the right site, retries with backoff if that site is down, and a Telegram ping when something new lands. Duplicate retries are not treated as new customers.

Results

Lost “we never got the event” tickets dropped. Night-time partner retries no longer create ghost customers. The team looks at a health page instead of SSH. This is plumbing — unglamorous, and the reason the numbers in the CRM can be trusted.

One URL for partners Retry instead of silent loss Alert on each new event