# Question about aggregations and bucket counts (filter vs post\_filter)

**URL:** <https://discuss.elastic.co/t/question-about-aggregations-and-bucket-counts-filter-vs-post-filter/66180>\
**Category:** Elasticsearch\
**Created:** [November 15, 2016, 11:58pm UTC](https://discuss.elastic.co/t/question-about-aggregations-and-bucket-counts-filter-vs-post-filter/66180 "2016-11-15T23:58:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![midget2000x](https://avatars.discourse-cdn.com/v4/letter/m/bbe5ce/32.png) [@midget2000x](https://discuss.elastic.co/u/midget2000x)\
**Post date:** [November 15, 2016, 11:58pm UTC](https://discuss.elastic.co/t/question-about-aggregations-and-bucket-counts-filter-vs-post-filter/66180/1 "2016-11-15T23:58:56Z")

</div>

I'd love some guidance from those who've implemented bucket aggregation (or facets or whatever) on an e-commerce site.

Do you run the aggregations as filters (so that the buckets and counts update with each bucket choice) or as post-filters so that the aggregation buckets from the original search remain constant even after buckets are chosen?

Like in my image, if I chose "100-150" should aggs update to reflect only buckets available for the new result set? Or should aggs be left alone?

I understand that they can be run either way, but I'm wondering if there's a UX/UI "standard practice".

![](https://us1.discourse-cdn.com/elastic/original/2X/9/9a76a2cb2b0bf84606c958dbac0234961f499017.png)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 13, 2016, 11:59pm UTC](https://discuss.elastic.co/t/question-about-aggregations-and-bucket-counts-filter-vs-post-filter/66180/2 "2016-12-13T23:59:43Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.