Dear Roblox Staff and Community,
I ran an advertisement campaign from Sunday to Tuesday, spending the recommended 19 credits per day. However, my game’s player count remained stuck at around 20–25 concurrent players.
During this period, I noticed some suspicious behavior in my analytics and the advertisment was targeting “New Players”:
1.Achievement Discrepancy: The “Enlisted” achievement which is awarded automatically to anyone who joins the game was only earned by 10% of players yesterday, and the script works without any problem.
Badge Image
How many new players joined the game via the advertisment:
2.DataStore Anomalies: When checking my New Players DataStore, many users had either default starting cash (1,000) or no DataStore entry at all. (evidence + link given to roblox staff only)
This pattern suggests that a large number of users are clicking the ad, joining, and leaving within a fraction of a second. This lowers the ad’s effectiveness and wastes my daily credits. Adding an in-game script to restrict access will not resolve this issue, as the ad credits are already spent the moment they click and join. Has anyone else experienced this pattern, or could staff provide insight into bot detection/click validation for ad campaigns?
- My games Average Playtime is between 65-75 Minutes, i dont think thats by 1312 users my game would just have like 5-25 players in one day right?
The Game Link: Battle for Honor World War II | Play on Roblox
Expected behavior
Require Engagement Minimums for Ad Campaign MetricsCurrently:
An ad click and join are counted immediately upon loading, regardless of how long the user stays in the game.
I propose that player joins via advertisements should only be counted toward campaign metrics (or charged) if the player remains
in-game for at least 5 minutes and performs basic activity (e.g., character movement, completing an interaction).
This would help filter out automated bot activity, accidental misclicks, and instant join-and-leave tactics designed to drain ad budgets.
A private message is associated with this bug report