Wintracker for WordPress

Shows live casino wins and stats from the Wintracker API on casino, game and provider pages: latest wins, biggest wins, top multipliers and stats cards, as shortcodes or PHP functions.

Setup

1. Install wintracker-wp.zip from the latest release (Plugins → Add New → Upload, or extract it into wp-content/plugins/wintracker-wp/) and activate Wintracker. From then on it updates itself from this repository (below).

2. Paste the API key under Wintracker → Settings and save: the page tests the key right away. The same page has Test connection and Clear cache buttons.

   Alternatively, define the key in wp-config.php. It then overrides the settings page and stays out of the database (and its backups):

   define( 'WINTRACKER_API_KEY', 'wt_…' );

Keys are created by the Wintracker admin (php bin/api-key.php create "casinos.example"), one per site.

How it works

• Server-side only. Every call is a wp_remote_get from WordPress with the key in the X-Api-Key header, so the key never reaches the browser.
• Cache: 60 s. Each distinct widget configuration is cached in a transient for 60 seconds (the API refreshes at most once a minute). Raise it with the wintracker_cache_ttl filter; it never goes below 60.
• Snapshots for outages. The last good response of each widget is also kept as a snapshot (7 days by default, wintracker_snapshot_ttl filter). Each snapshot is overwritten on every successful refresh, so the plugin stores only one small entry per widget configuration (at most 100 wins), never a history.
• Graceful fallback. If the API times out, returns 5xx/401/429 or invalid JSON, the widget shows its snapshot and the plugin pauses API calls for a minute (longer when the API sends Retry-After, up to 15 min), so an outage does not slow every page view. Without a snapshot the widget renders nothing.
• Wrong arguments (unknown casino slug, game id) render nothing; logged-in editors see the reason in an HTML comment (``) in the page source.
• Stylesheet only where needed. assets/wintracker.css (about 5 KB, less gzipped) loads only on pages that show a widget: in <head> for posts with a Wintracker shortcode, otherwise in the footer when the widget renders.

Shortcode builder

Wintracker → Shortcode builder in wp-admin (for anyone who can edit posts): pick the widget, the casino and provider from lists loaded from the API, search games by name, set the options, see a live preview, and copy the shortcode or the PHP call. The same page has a reference of every shortcode and attribute.

Shortcodes

Wins attributes

casino, provider and game combine, e.g. one game at one casino.

Stats attributes

Fields without a value (e.g. no RTP known) are left out.

Win details read, for example: biggest win "Gates of Olympus · Pragmatic Play · 3 days ago", top multiplier "€530.00 on a €0.50 bet · Gates of Olympus · Pragmatic Play · 2 weeks ago", last win "€12.40 · 31× · Book of Dead". What the card is about is left out (no game name on a game card) and the casino is added on provider and game cards. They cost up to three more cached API calls per card (wins.php, limit=1).

Examples

Casino review page:

[wintracker_stats casino="bizzo"]
[wintracker_biggest_wins casino="bizzo" period="week" title="Biggest wins at Bizzo this week"]
[wintracker_latest_wins casino="bizzo" limit="20"]

Provider page:

[wintracker_stats provider="pragmaticplay"]
[wintracker_top_multipliers provider="pragmaticplay" period="month" layout="cards" limit="8"]

Game page:

[wintracker_stats game="685" layout="list"]
[wintracker_biggest_wins game="685" period="month"]
[wintracker_latest_wins game="685" casino="bizzo" layout="list"]

Sidebar: [wintracker_latest_wins layout="list" columns="game,win,time" limit="5" images="no"]

PHP functions

Each takes the same arguments as its shortcode and returns HTML:

echo wintracker_latest_wins( array( 'casino' => 'bizzo', 'limit' => 20 ) );
echo wintracker_biggest_wins( array( 'provider' => 'pragmaticplay', 'period' => 'week' ) );
echo wintracker_top_multipliers( array( 'game' => 685, 'layout' => 'cards' ) );
echo wintracker_wins( array( 'sort' => 'amount', 'period' => 'month' ) );
echo wintracker_stats( array( 'casino' => 'bizzo' ) );

Raw data for custom markup (cached the same way, null when unavailable):

$data  = wintracker_get_wins( array( 'casino' => 'bizzo', 'sort' => 'amount', 'period' => 'week' ) ); // ['wins' => [...], 'meta' => [...]]
$stats = wintracker_get_stats( 'game', 685 ); // wins, total_won_eur, biggest_win_eur, top_multiplier, last_win_at, rtp, …

Templates that call these functions get the stylesheet in the footer. To load it in <head> instead:

add_action( 'wp_enqueue_scripts', function () {
    if ( is_singular( 'casino' ) ) { // the post types that show widgets
        wintracker_enqueue_style();
    }
} );

Finding slugs and ids

The widgets take Wintracker's own identifiers:

• casinos: slug from /api/v1/casinos.php (e.g. bizzo)
• providers: slug from /api/v1/providers.php?q=prag
• games: id from /api/v1/games.php?q=elvis (the API has no game slugs)

Customising

• CSS: override the custom properties, e.g. body .wintracker { --wt-accent: #0a7d3b; --wt-radius: 4px; }, or turn the stylesheet off with add_filter( 'wintracker_load_css', '__return_false' ); and style the .wintracker classes in the theme.
• Templates: copy any file from templates/ to <theme>/wintracker/ (e.g. wintracker/wins-cards.php) and edit it.
• Filters: wintracker_cache_ttl, wintracker_snapshot_ttl, wintracker_timeout (default 5 s), wintracker_label, wintracker_money, wintracker_template, wintracker_html, wintracker_load_css.

Updates from GitHub

The plugin updates through the normal wp-admin screens, from this repository's releases: update notice on Plugins and Dashboard → Updates, "View details" with the release notes, one-click update, and WordPress's "Enable auto-updates" link.

Shipping a new version: raise Version: and WINTRACKER_VERSION in wintracker.php (they must match) and merge to the default branch. The Release workflow lints the PHP, builds wintracker-wp.zip and publishes release vX.Y.Z. Sites see it within a few hours, or right away with the Check for updates link under Wintracker on the Plugins screen, or Dashboard → Updates → Check again. Pushes that don't change the version publish nothing.

Optional wp-config.php constants:

define( 'WINTRACKER_AUTO_UPDATE', true );   // install new versions automatically on this site (false: never)
define( 'WINTRACKER_GITHUB_TOKEN', '…' );   // read-only GitHub token: only needed if the repository becomes private,
                                            // or if many sites share one IP (GitHub allows 60 anonymous requests/hour)

Without WINTRACKER_AUTO_UPDATE, each site's own "Enable auto-updates" link decides. The token is sent only to api.github.com / codeload.github.com for this repository.

What is stored in the database

No custom tables and nothing per visitor. Two small options in wp_options:

Everything else is a transient, which WordPress keeps in wp_options too (or in Redis/Memcached when the site has a persistent object cache), each with an expiry:

So the database holds at most two copies per distinct widget configuration (casino + sort + period + …, not per page: ten pages with the same shortcode share one entry), and none of them is autoloaded. Snapshots of widgets nobody shows any more expire after 7 days. Deactivating leaves them to expire; uninstalling deletes them and the two options.

Notes

• A game stats card needs two cached API calls: games.php has no id filter, so the plugin gets the game's name from wins.php?game=ID and then finds that id in games.php?q=NAME. Merged game ids resolve to the surviving game.
• Uninstalling the plugin deletes its cached responses and snapshots.