# Using fitbit and active minutes for logging a run

**URL:** <https://forum.beeminder.com/t/using-fitbit-and-active-minutes-for-logging-a-run/1956>\
**Category:** Newbee\
**Created:** [February 26, 2016, 3:09am UTC](https://forum.beeminder.com/t/using-fitbit-and-active-minutes-for-logging-a-run/1956 "2016-02-26T03:09:30Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![philip](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/philip/32/1505_2.png) [@philip](https://forum.beeminder.com/u/philip)\
**Post date:** [February 26, 2016, 6:20pm UTC](https://forum.beeminder.com/t/using-fitbit-and-active-minutes-for-logging-a-run/1956/2 "2016-02-26T18:20:06Z")

</div>

I think that’s a good argument for **frequency** goals, i.e. **do more often** not just **do more quantity**. That can be achieved with a custom [aggregation method](http://forum.beeminder.com/t/documentation-of-aggregation-methods-would-be-nice/549/4 "subscription required, or a nice email to support!") but I’m not sure that any of the fitbit measures would work even with a **nonzero** aggregation.

You might be better off creating a manual goal. Just give yourself a point for every day that you exercised, and don’t worry about the fitbit integration.

Set your slope to an achievable number of workouts per week. Probably not seven, so that you can catch up after the occasional day off!

---

_[View the full topic](https://forum.beeminder.com/t/using-fitbit-and-active-minutes-for-logging-a-run/1956)._