# Debugging IFTTT location triggers **URL:** \ **Category:** Akrasia\ **Created:** [November 27, 2018, 5:50pm UTC](https://forum.beeminder.com/t/debugging-ifttt-location-triggers/4591 "2018-11-27T17:50:34Z")\ **Posts on this page:** 1\ **Showing post:** 4
**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:** [December 1, 2018, 6:27pm UTC](https://forum.beeminder.com/t/debugging-ifttt-location-triggers/4591/4 "2018-12-01T18:27:45Z")
Obviously, we have no control over when (or if!) IFTTT decide to trigger a location-based recipe. But if you’re only meant to be able to do this goal once per day, we can change how multiple datapoints are interpreted. As @daerdemandt says, that’s probably setting the [aggregation method](https://forum.beeminder.com/t/documentation-of-aggregation-methods-would-be-nice/549/4) to `max`, which we can do beehind the scenes if you email [support@beeminder.com](mailto:support@beeminder.com) --- _[View the full topic](https://forum.beeminder.com/t/debugging-ifttt-location-triggers/4591)._