# Journey Report date filter limitations

**URL:** <https://community.hubspot.com/t/journey-report-date-filter-limitations/91635>\
**Category:** HubSpot Ideas\
**Tags:** reports\
**Created:** [October 11, 2023, 10:32pm UTC](https://community.hubspot.com/t/journey-report-date-filter-limitations/91635 "2023-10-11T22:32:49Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![christa](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/christa/32/35493_2.png) [@christa](https://community.hubspot.com/u/christa)\
**Post date:** [October 11, 2023, 10:32pm UTC](https://community.hubspot.com/t/journey-report-date-filter-limitations/91635/1 "2023-10-11T22:32:49Z")

</div>

Make the journey report date range flexible (if you want to limit a date range on certain actions, only apply it to that stage, not the report)  
Discovered today that when you use the page views URL as one of the stages in your journey the main date range filter at the top of the report is limited.

Hubspot in general limits page view activity to only the last 31 days.  
So even though you may be interested in contacts entering the journey that have existed in your Hubspot instance (create date) for longer than 31 days, it is impossible to include them in the journey when using a page view activity as a stage due to the ENTIRE journey date range being limited to 31 days.  
This message appears when doing so

 ![christa_0-1697063501418.jpeg](https://d2qpr2jzcazej7.cloudfront.net/original/3X/f/a/fa97a8bf6aa450b72c5ab3eddbbbef1b2051c522.jpeg)

---

<div class="post-metadata">

**Author:** ![ICajamarca](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/icajamarca/32/228212_2.png) [@ICajamarca](https://community.hubspot.com/u/ICajamarca)\
**Post date:** [November 22, 2023, 5:38pm UTC](https://community.hubspot.com/t/journey-report-date-filter-limitations/91635/2 "2023-11-22T17:38:06Z")

</div>

Definitely needed!

---

<div class="post-metadata">

**Author:** ![dmastin](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/dmastin/32/33826_2.png) [@dmastin](https://community.hubspot.com/u/dmastin)\
**Post date:** [December 20, 2023, 5:37am UTC](https://community.hubspot.com/t/journey-report-date-filter-limitations/91635/3 "2023-12-20T05:37:26Z")

</div>

Clarifying how the date range works:

The report can support up to 20 million events (e.g. a user clicking a link in an email or viewing a page is one event) or 36 months of data, whichever comes first. In order to protect our system, our filters automatically prompt you to lower the date range if the event definition / the journey you’re trying to run is too broad and would exceed our limits, _especially_ if the event limit would exceed 20 million events. This happens sometimes with customers who get a lot of web traffic **and** have a large date range set for the journey report, which could explain why you’re seeing this “31 day date range” limit.

Hope this helps -- definitely reach out to support if you need more assistance.

---

<div class="post-metadata">

**Author:** ![christa](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/christa/32/35493_2.png) [@christa](https://community.hubspot.com/u/christa)\
**Post date:** [December 26, 2023, 7:57pm UTC](https://community.hubspot.com/t/journey-report-date-filter-limitations/91635/4 "2023-12-26T19:57:34Z")

</div>

@dmastin support has been contacted and that is the reason this idea was posted. Support was agreed this is an obstacle with no other method to get the data points we were after. What you provided makes sense for the action/stage/step date limitation BUT does not make sense for the entry into the journey.  
**The main part of this ask is to NOT limit the date range to qualify for ‘entry’ into the journey.**  
If a contact has a create date or a ‘became a lead date’ or some other date value further in the past than the last 31 days for the action of a page view, that person would not be able to join the journey. The limitation requires us to start in the parameter of 31 days when utilizing certain events. It is fine enough to **limit ONLY that event in the journey** but when the entire journey is only allowed that timeline it makes the report less usable/valuable for digging into data.

---

<div class="post-metadata">

**Author:** ![christa](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/christa/32/35493_2.png) [@christa](https://community.hubspot.com/u/christa)\
**Post date:** [April 11, 2024, 8:33pm UTC](https://community.hubspot.com/t/journey-report-date-filter-limitations/91635/5 "2024-04-11T20:33:42Z")

</div>

If anyone is still feeling the pains of limitations on customer journey reports like we are, please upvote this new idea/post [https://community.hubspot.com/t5/HubSpot-Ideas/Customer-Journey-Report-improvements/idi-p/958940#M176237](https://community.hubspot.com/t5/HubSpot-Ideas/Customer-Journey-Report-improvements/idi-p/958940#M176237)
