When a player says they played but never got their prize, you need answers fast, and digging through data exports or opening a support request slows everything down.
Player Logs lets you look up a single player and see everything recorded about them across your Minigames (formerly Adact) campaigns: their gameplay history, the prizes they were awarded, and every webhook event their participation triggered. It all lives inside the Minigames dashboard, so you can check a player's full history without leaving the platform.
This guide will walk you through how to search for a player, read their results, and export the data you need.
How to Look Up a Player
Search for Your Player
Search for a player by any identifier you have on hand, then choose which campaigns to look in.
- From the top navigation bar in your Minigames dashboard, click Player Logs.
- Under Search by, choose the identifier type you want to search with. See the table below for what each option matches.
- Enter the player's identifier in the Search value field.
- Under Select campaigns, choose the campaigns you want to search. All of your account's campaigns are listed and selected by default, so narrow the selection if you only need to check specific campaigns.
- Click Search.
| Search type | What it matches |
|---|---|
| The player's registered email address | |
| Code | The player's CID (player code) |
| Phone Number | The player's phone number |
| Integration Unique ID | An identifier from an external system you have connected |
| Optimove Customer ID | The player's Optimove customer ID |
Review the Results
Results appear as a list of campaign cards, one for every campaign where the player was found. Each card header shows:
- The campaign name and ID
- How many gameplays and webhook events the player has in that campaign
- Click anywhere on a campaign card header to expand it.
- Review the player data panel at the top of the card.
- Switch between the Gameplay Logs and Webhook History tabs to see the player's activity.
Player Data Panel
The panel at the top of each expanded card summarizes everything recorded about the player for that campaign.
| Field | Description |
|---|---|
| Player ID | The player's internal Minigames record ID |
| Registered email, if captured | |
| Full Name / Phone Number | If captured during registration |
| CID | The player's Optimove customer ID / code |
| Total Gameplays | How many times the player has played this campaign |
| Leaderboard Name | The player's leaderboard alias, if set |
| Highest Score | Their best score across all plays, if the game is scored |
| Max Allowed Gameplays | Shown only for campaigns with dynamic play limits. Displays the player's individual override, or the campaign default if no override has been set. |
Gameplay Logs Tab
The Gameplay Logs tab shows a paginated table of every gameplay session the player had in this campaign, newest first. These columns are always visible:
| Column | What it shows |
|---|---|
| Gameplay ID | The unique ID for this gameplay session |
| CID | The Optimove customer ID passed at the time of play |
| Game Start Date | When the session began |
| End Date | When the session ended |
| Duration | Length of the session, in seconds |
| Unexpected Finish | Whether the game ended abnormally, for example, if the player closed the browser mid-game |
| Prize Name | The prize awarded in this session, if any |
| Prize Code | The prize's redemption code, if one was issued |
You can add more columns using the column selector on the table:
| Column | What it shows |
|---|---|
| Score | Points scored in this session |
| Result | The outcome value recorded by the game |
| Tag | The Tag Manager tag assigned to this gameplay, if any |
| Referrer | How the player arrived at the campaign |
| Leaderboard Name | The player's leaderboard alias as recorded at the time of this play |
| IP Address | The player's IP address at the time of play |
| Client Info (Browser) | The player's browser User-Agent string |
| Created At | When the gameplay record was created |
Webhook History Tab
The Webhook History tab shows every webhook event fired for this player in this campaign.
| Column | What it shows |
|---|---|
| Event ID | The unique ID for this webhook event |
| Type | The event type |
| Status | Whether the call succeeded (success), failed (error), or is still outstanding (pending) |
| Gameplay ID | The gameplay session this event relates to |
| Created At | When the event was sent |
| Error Message / Details | If the call failed, the error message and the full error response returned by your backend API |
Use the Filter by type dropdown to narrow the list to a specific event type. The dropdown only shows event types that exist for this player in this campaign.
When a webhook fails, the error details field shows the exact payload and error code your backend returned. This is usually the fastest way to diagnose an integration issue. To set up or manage the webhooks that appear here, see How to Configure Multiple Webhooks per Brand in Minigames.
Export the Data
You can export results for every campaign at once, or for a single campaign.
Export All Campaigns
- When results are showing, click Export All above the campaign cards.
- In the export window, choose which gameplay columns to include. Player information (email, first name, last name, and phone number) is always included.
- Choose a file format:
- Excel (XLSX) — exports each campaign to a separate sheet in one workbook.
- CSV — combines all campaigns into a single file.
Export a Single Campaign
- On the campaign card header, click Export.
- Choose Excel (XLSX) or CSV to download the gameplay data for that campaign only.
Use Case Examples
- Missing prize complaints: A player says they played but didn't receive a prize. Check exactly what was awarded and whether the notification webhook succeeded or failed.
- Play limit checks: Confirm how many times a player has participated in a campaign and whether they have plays remaining.
- Webhook troubleshooting: Your team is debugging a webhook integration. Review the raw error message and error details your backend returned for every failed event.
- Cross-campaign history: See a player's full history across multiple campaigns at once, without downloading a full data export.