I’ve spoken before about how I used to be a frequent cheater, and eventually weaned myself off of it. I’d suggest putting in some thought about why you (a) want to do the thing and (b) then are inclined to cheat, even though that goes against your stated goals.
In my case, I usually found myself cheating for one of two reasons:
- I wasn’t actually interested in achieving the goal as written.
- I was trying to do too much or too many things at once.
There’s also a rare third case of “life happened in unexpected ways” - but in those cases, a quick email to support with an explanation usually resolved things.
The first case can happen for a variety of reasons: the data is something I don’t have direct control over, doing the action I’m beeminding doesn’t affect my end goal as expected, or I really just don’t care about my stated goal. Fixing the situation involves looking more closely at what I actually want and how I can get there. This forum is a good place to talk through that sort of question with others.
The second case is much more frequent for me, and fixing it involves looking at my life as a whole, not just one goal. To use an example from my own life: it wasn’t really reasonable to expect to maintain a large garden while in engineering school! No matter how much I wanted to, the reality of the situation was that I was rarely getting home before dark and didn’t have the energy even then. I kept telling myself I’d “catch up” on weekends, but actually what I did on weekends was sleep (and do homework). The most recent blog post about beeminding easy things is relevant here.
It’s possible to cheat most systems, if you’re creative enough about it (as @dreev illustrated). You can get some restriction on that through better systems, public accountability, and the like, but I suspect you’ll get more bang for your buck by addressing the reasons you’re inclined to cheat in the first place.