Le Bon Rang received 1,690 clicks from the relaydle rail and 6 from the directory between September 1 and 28, 2026 (UTC). The result demonstrates referral delivery through a standard rail integration. It does not establish unique players, completed games or retention.
relaydle operates the referral exchange measured here. This is a delivery example from its own server records, not a creator testimonial or a forecast for a new member.
What did the rail send to Le Bon Rang?
Le Bon Rang is a daily ranking game. Its result screen uses the same recommendation and redirect system available to approved rail members. When someone finishes a participating game and clicks a recommendation, relaydle records the outbound redirect.
| Measurement | September 1 to 28, 2026 (UTC) |
|---|---|
| Received rail redirects | 1,690 |
| Received directory clicks | 6 |
| Combined received redirects | 1,696 |
| Destination rail matches | 1,038 |
| Destination-server confirmations | Not measured |
| Next-day returns | Not measured |
The directory and rail are separate channels. In this example almost all delivered clicks came from recommendations on other games' result screens, rather than from browsing the public directory.
What does a matched arrival tell a creator?
A destination rail match associates a redirect with a subsequent rail impression on the destination using a short-lived server-side address match. Le Bon Rang had 1,038 such matches in the period. This is a fallback attribution signal, not an authenticated landing report or a count of distinct people.
Repeat clicks remain repeat events. A match is not proof that a person completed a puzzle. The remaining redirects cannot be called lost players: a player may open a game without reaching its result-screen rail, and the fallback cannot match every visit.
Next-day returns were unmeasured in this snapshot. Optional authenticated destination reporting can confirm a landing and a return on the following UTC day. Missing reporting must stay unmeasured rather than appear as a zero-percent return rate.
Can another game expect the same result?
No fixed delivery volume is promised. A destination's recommendations depend on active traffic sources, language and country eligibility, source-specific click fit, and reciprocal participation. The network was concentrated in a small group of active games during this period. One game's result does not show that a new member with another audience will receive the same number of clicks.
How can a creator install the same integration?
First, submit a game for a free directory listing. Rail membership is a separate application and human review on the creator page.
After approval, use the setup email to sign in and open the installation checklist. Copy the game-specific widget snippet or API instructions into the result screen. Check that real result-screen visits register rail impressions, then watch outbound activity and reciprocal eligibility.
A game becomes eligible to receive recommendations after 30 rail views and 3 outbound clicks, with no waiting period. Approval and installation are separate steps. How the rail works explains recommendation order, exclusions and privacy.
Use received clicks as the initial delivery measure. Add destination-server reporting when you need confirmed landings and next-day return evidence. Compare weeks with the same metric definitions rather than treating repeated clicks as newly acquired people.