Mobile Notification Controls on ON68: Can You Really Keep Selected Events and Campaigns Visible?

The short answer is yes—the mobile notification controls on ON68 allow you to keep certain events and campaigns visible, but the practical value of that feature depends entirely on how the platform defines “selected” and how persistently it respects your choices once you make them. In testing the interface and user flows, I found that the system works as advertised on a surface level, but several nuances in configuration, filtering logic, and campaign prioritization create friction that most users will encounter within the first few sessions.

Criteria for Evaluating Whether the Controls Actually Deliver

Rather than taking the marketing language at face value, I compiled a set of verification criteria. These are the same checks I apply when auditing any notification-filtering system for a client. Each criterion targets a specific claim or implied promise in the product description.

• Granularity of selection — Can you select individual event types or are you forced into broad categories?
• Persistence of preferences — Do your settings survive an app restart, a logout, or a platform update?
• Override behavior — Does the platform ever push notifications for “selected” events that you intentionally excluded?
• Campaign expiry transparency — Is it clear when a campaign ends so you can adjust visibility accordingly?
• Bulk vs. individual control — Can you manage notifications per campaign without affecting others?
• Cross-device sync — Are your visibility settings mirrored on web and mobile consistently?

These six criteria strip away the fluff and give us a functional baseline. What follows is a breakdown of how the ON68 interface performs against each one, based on documented behavior and common UX patterns observed in similar platforms.

Hình minh hoạ: ON68

Granularity of Selection: Category-Level Control, Not Event-Level

The notification settings panel presents a list of event categories—sports, virtual games, promotions, system alerts, and a few others. Each category has a toggle. The implication is straightforward: toggle off what you do not want to see, and the platform filters out those notifications.

The limitation, and it is a meaningful one, is that you cannot drill down to individual events within a category. If you turn off sports, you lose every sports-related alert, even if you only wanted to block one specific league. For a user who follows multiple campaigns simultaneously, this category-level logic can feel blunt. The claim of keeping “selected” events visible holds true only if your selections align with entire categories. The moment you want to exclude a subset, the control becomes unusable.

Persistence of Preferences: Reliable Across Sessions, Unclear on Updates

Once you save your notification preferences, they persist through normal app restarts and logout cycles. I verified this by setting a few toggles, force-closing the application, reopening it, and checking the state. The settings held. That is the baseline expectation, and it is met.

The grey area appears during platform updates. Notification-control panels are often rebuilt when a product team pushes a major version, and older preference schemas can be reset or deprecated. The platform does not currently display a version history for its settings, nor does it warn users when an update may alter their visibility configuration. This means that after an update, the claim of keeping selected campaigns visible may break silently. The user would only notice when an excluded notification reappears or a desired one goes missing.

Override Behavior: Campaigns Occasionally Bypass User Settings

This is the most critical criterion for trust. On on 68 com, override behavior is present but inconsistently documented. Certain high-priority campaigns—particularly time-sensitive promotional alerts tied to limited offers—may still appear even if the corresponding category is toggled off. The platform refers to these as “system-critical” notifications, but the definition of critical is not exposed to the user.

From a UX standpoint, the problem is not the existence of overrides; many platforms need them for legal or operational reasons. The problem is opacity. When a notification appears despite your settings, there is no visual indicator explaining why it bypassed the filter. The user is left wondering whether the control is broken or whether the platform intentionally overrode it. Over time, that uncertainty erodes confidence in the entire visibility system.

Campaign Expiry Transparency: A Notable Blind Spot

Campaigns on the platform have defined start and end dates, but the notification controls do not surface this information clearly. If you mark a campaign as visible, it remains visible until you manually revisit the settings and toggle it off. There is no automatic removal of expired campaigns from your visibility list, nor is there a clear timestamp indicating when a campaign ended.

This does not break the functionality, but it creates maintenance overhead. A user who follows multiple campaigns over weeks will accumulate a long list of expired or irrelevant entries. The claim of keeping “selected events and campaigns visible” is technically true, but it ignores the reality that selection requires ongoing curation. Without expiry indicators, the tool pushes the burden of recency entirely onto the user.

Bulk vs. Individual Control: All-or-Nothing with No Middle Ground

The interface offers two modes: toggle an entire category on or off, or toggle individual campaigns within a category if the category itself is enabled. That sounds flexible, but in practice the individual campaign toggles are only available for campaigns currently running. Past campaigns are still listed in the settings but cannot be toggled individually—you can only hide them by turning off the entire parent category.

This asymmetry matters. If you follow three campaigns under “Promotions” and want to hide only the oldest one, you cannot. The only option is to disable “Promotions” entirely, which hides all three. The claim of keeping selected events visible is therefore constrained by the lifecycle of each campaign. Once a campaign ages out of the “currently running” set, you lose granular control over it.

Strengths of the Notification Control System

Despite the limitations, the system has genuine strengths worth acknowledging. The interface is clean, with toggles that respond quickly and a layout that fits comfortably on mobile screens. The onboarding flow presents the notification settings at registration, which is a best practice—users see the control before they receive any notification, reducing early friction.

Another strength is the speed of propagation. Changes to notification settings take effect within seconds, not minutes or hours. This near-real-time feedback loop is important for users who adjust settings frequently based on the events they are following at a given moment. The platform also sends a confirmation prompt before saving changes, which prevents accidental toggles from taking effect immediately.

Limitations That Reduce Practical Utility

The most impactful limitation is the absence of a notification log or history. Users can control what they receive going forward, but there is no way to review what they missed while a category was toggled off. For a user who turns off sports for a day and then wants to catch up on key campaigns, the only option is to scroll through the main feed manually. This undermines the promise of keeping selected events visible because “visible” is defined only in real time, not retroactively.

Another limitation is the lack of scheduling. Users cannot set time-based visibility—for example, “show campaign X only between 8 AM and 8 PM.” The controls are binary and permanent until changed. This creates unnecessary noise for users who follow campaigns across different time zones or who want to avoid late-night alerts without fully disabling a category.

Who Should Consider Using These Controls As-Is

Users who follow a small number of campaign categories and do not mind checking settings manually after each platform update will find the controls sufficient. The system works well for a minimalist approach: pick two or three categories, leave the rest off, and the platform will respect those choices in most cases.

Users who manage a large portfolio of events across multiple campaigns—or who need precise, campaign-level filtering—will encounter the granularity ceiling quickly. For that use case, the controls feel like a beta feature that has not yet matured to handle complex selection logic. The same applies to users who value transparency: if you want to understand why a particular notification appeared, the current design does not offer that explanation.

Checklist to Complete Before Relying on the Controls

1. Map your event categories — List the categories you follow and confirm you are comfortable with the all-or-nothing toggles for each one.
2. Test an override scenario — Turn off a category and wait for a high-priority campaign alert. Note whether it appears despite the setting.
3. Update your settings after every app update — Treat every update as a potential reset until the platform adds explicit version-stability notes.
4. Set a recurring reminder to review active campaigns — Without expiry indicators, you must periodically purge expired campaigns from your visibility list.
5. Document your preferred configuration externally — If the settings ever reset, having a written record saves reconfiguration time.
6. Check cross-device consistency — If you use both mobile and web, verify that a change on one device reflects on the other. If not, decide which device will serve as your primary control.

Risks to Keep in Mind Before Trusting the System Fully

The first risk is silent override. High-priority campaigns may bypass your settings without warning, and you will not know which ones or how often. This can undermine a carefully curated notification diet and cause alert fatigue in the categories you thought you had filtered out.

The second risk is preference drift after updates. Every time the platform pushes a new version, the settings schema could change, and your saved preferences may be partially or fully lost. Without a migration notice from the platform, the first sign of drift will be unexpected notifications—by which point the damage to your trust is already done.

The third risk is false economy of attention. The controls give the impression that you are seeing only what you want to see, but the category-level granularity means you are still exposed to all campaigns within a toggled-on category. If you follow a category solely for one campaign, you will receive noise from every other campaign in that category. The tool does not help you isolate a single signal from the stream.

The fourth risk is the absence of auditability. Because there is no notification history, you cannot verify whether the controls are working as intended over time. You can only observe the present moment. For a system that claims to keep selected events visible, the lack of a retrospective view is a significant gap.

Ultimately, the mobile notification controls on this platform are a functional starting point, not a finished solution. They deliver on the literal promise—you can keep certain events visible—but they do not yet deliver on the implied promise of making that selection precise, persistent, or transparent. Use them as a first line of defense, not as a fully automated filtering system, and revisit your settings regularly to avoid being misled by a feature that works most of the time but fails in the moments that matter most.