Clear before you install
How the rail works.
relaydle is a free referral exchange for daily games. A player finishes one game, sees a short list of other human-approved games, and chooses whether to open one. Joining the directory does not commit you to adding the rail.
Current network
Games participating now
Only active, approved rail members appear here. The results below cover 2026-08-17 to 2026-09-15. Daily audience is the creator's estimate when supplied, otherwise the average number of completed-game rail views per day over this period.
Recommendation order
How each rail is calculated
There is no single order shared by the whole network. Each source game gets its own slate, recalculated from the last 30 days of player activity. Paid placement and a creator's audience estimate do not affect it.
Build the eligible list
Your own game is removed, and you can exclude any member in the dashboard. Country-specific games appear only when the player's country or page language makes them relevant. Games matching the page language form the first tier.
Themes set the starting fit
Before a source and destination have enough history together, their expected click fit starts from how theme pairs perform across the network. Geography to trivia can learn a different fit from sports to trivia.
Each sender learns separately
We compare which games are shown and clicked for every source-to-destination pair, correcting for card position. A destination clicked by DailyMetro players rises on DailyMetro's rail, not automatically on every rail.
Clicks meet lasting quality
The final value combines the chance that this source's players click with the chance that referred players return to the destination on a later day. The model keeps testing uncertain options, and refreshes every hour.
Referral context has one extra rule. If the host tells relaydle which game sent the player, that game is placed at the end because the player just left it. Its forced position is not used to train the order.
Data and privacy
What the integration sends
The widget calls relaydle with credentials: "omit". It does not set or read cookies, localStorage, advertising IDs, account IDs, or the host page query string.
When recommendations load
- Your public game ID and placement name
- The page path, with query parameters and fragments removed
- The page language and optional country or referring-game context supplied by the host
- The destination IDs displayed, their positions, and whether the widget or API was used
When a player clicks
- A unique click token records the source, destination, placement, position, and date
- The destination receives ordinary UTM attribution plus the
rcclick token - relaydle stores the click event. It does not build a profile of the player
Short-lived server safeguards
- Impressions are deduplicated with a one-way hash of request data that expires after 10 minutes
- For games without server confirmation, a destination-specific HMAC of the IP address can match a click to a completed game
- That temporary match expires after six hours and is deleted as soon as it matches. The raw IP address and user agent are not stored in the ledger
Optional arrival API
- A destination server can submit the
rctoken to confirm a landing - Submitting it again on a later day can measure a return, at most once per UTC day
- This is optional. If a game preserves the token for later visits, that game must explain and govern its own storage choice
API mode uses the same recommendation and redirect endpoints. It returns JSON instead of drawing cards, so it collects no extra category of data.
No commitment
Review the fit first.
You can discuss the referral fit, join the directory, or inspect the API without adding a widget or tracking to your site. The rail starts only after a separate application and approval.