# Goal report **URL:** \ **Category:** Dashboards & Reporting\ **Tags:** enterprise\ **Created:** [August 11, 2025, 12:47pm UTC](https://community.hubspot.com/t/goal-report/137777 "2025-08-11T12:47:53Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Jaylin](https://avatars.discourse-cdn.com/v4/letter/j/49beb7/32.png) [@Jaylin](https://community.hubspot.com/u/Jaylin)\ **Post date:** [August 11, 2025, 12:47pm UTC](https://community.hubspot.com/t/goal-report/137777/1 "2025-08-11T12:47:53Z")
Hello HubSpot Community, i want to set the goal by team and person, for example, a team should have 5 customers as goal, and there 5 persons in the team, so each one should have 1 customer Goal. similar below: ![Jaylin_0-1754915906194.png](https://d2qpr2jzcazej7.cloudfront.net/original/2X/e/e0c830477fe876e1c6439c846b353b5a73840b86.png) after setted the goal, i can view the goal perfomance, and create a goal report by month. in another way, i can also creaed the goal by sigle-object report. the question is that the data between Goal report by month is different with Goal report by sigle- object report. The report data created through a single target is twice that of the monthly report. ![Jaylin_1-1754916379291.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/7/0/70f6c7c2e814bf8bb42f4bced6c05991d68e4e11.png) it seems the sigle-object report caculate twice (team+person). do you have some ideals about these? ---
**Author:** ![Raflab](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/raflab/32/59474_2.png) [@Raflab](https://community.hubspot.com/u/Raflab)\ **Post date:** [August 11, 2025, 4:35pm UTC](https://community.hubspot.com/t/goal-report/137777/2 "2025-08-11T16:35:54Z")
Hello! This is a very common point of confusion when building custom reports on the Goals object. Your diagnosis is exactly right: **the single-object report is double-counting by adding the team goal and the individual user goals together.** Let’s break down why this happens and how to fix it. ### Why This Happens: Team Goals vs. User Goals In HubSpot’s Goals tool, when you set goals for users and then assign them to a team, the **Team Goal** often acts as a summary or a container for the sum of the user goals. Based on your first screenshot, the “US” team goal for January is **20 units**. This isn’t a separate 20 units; it’s the sum of the goals for the individual reps on that team (4 reps x 5 units each = 20 units). - **Standard Goal Reports:** These reports are built to understand this hierarchy. They know to show you the total target (the Team Goal) and not add the user goals on top of it. - **Custom Single-Object Reports:** A custom report doesn’t automatically know this. When you tell it to “Sum the Target Amount,” it finds _every_ goal that fits its criteria and adds them all up. So, the calculation in your broken report is: (Sum of all User Goals) + (The Team Goal) = Double the actual target Your second screenshot shows this perfectly. The correct monthly goal is **15** , but your custom report calculates it as **30**. * * * ### The Solution: Filter Your Report by “Goal Type” To fix this, you just need to add a simple filter to your custom report to tell it _which_ level of goal you want it to count. Here’s how to do it: 1. Go to your HubSpot dashboard and find the problematic report. Click to **Edit** it. 2. In the report builder, go to the **Filters** tab. 3. You need to add a filter for the property **“Goal type.”** This property distinguishes between goals assigned to a team and goals assigned to a specific user. 4. Set the filter to **Goal type is any of User**. This tells the report to _only_ sum the goals that are assigned to individual users and to completely ignore the “Team” level goal. The total will now be correct because it’s only adding up the base numbers once. Alternatively, you could set the filter to **Goal type is any of Team**. This would also work and would show you the sum total without having to add up the individuals. For most reports, filtering by User is slightly more flexible, but either will solve the double-counting issue. By applying this one filter, your custom report’s data will match the standard monthly goal reports. Hope this clears things up! ---
**Author:** ![Jaylin](https://avatars.discourse-cdn.com/v4/letter/j/49beb7/32.png) [@Jaylin](https://community.hubspot.com/u/Jaylin)\ **Post date:** [August 12, 2025, 1:17am UTC](https://community.hubspot.com/t/goal-report/137777/3 "2025-08-12T01:17:30Z")
Hi Raflab, thanks for your replay! i followed your steps and add the [Goal type] filter, but there is no items named “user”. could you please tell me which one is right? ![Jaylin_0-1754961391346.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/c/a/caf15ab915192f339c596cfc8de5a6e14c304a99.png) ![Jaylin_1-1754961431295.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/7/4/74bf5069a1777b6e6eea84c4b555cebbc787c870.png) ---
**Author:** ![Raflab](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/raflab/32/59474_2.png) [@Raflab](https://community.hubspot.com/u/Raflab)\ **Post date:** [August 12, 2025, 9:32am UTC](https://community.hubspot.com/t/goal-report/137777/4 "2025-08-12T09:32:21Z")
My apologies, my previous advice was based on the property name, but I see now which filter you are using. ### The Diagnosis: You’re Using the Wrong “Goal Type” Filter The filter your screenshot shows, labeled **“Goal type”** , is for the **measurement** or **metric** of the goal (e.g., “are we tracking ‘Deals Created’ or ‘Sales Quota’ or ‘Calls made’?”). We need to use a _different_ property that identifies **who the goal is for** (an individual person or a whole team). The property you actually need to filter by is called **Contributor type**. ---
**Author:** ![Jaylin](https://avatars.discourse-cdn.com/v4/letter/j/49beb7/32.png) [@Jaylin](https://community.hubspot.com/u/Jaylin)\ **Post date:** [August 12, 2025, 9:39am UTC](https://community.hubspot.com/t/goal-report/137777/5 "2025-08-12T09:39:09Z")
that works! thank you! ---
**Author:** ![chighsmith](https://avatars.discourse-cdn.com/v4/letter/c/77aa72/32.png) [@chighsmith](https://community.hubspot.com/u/chighsmith)\ **Post date:** [August 11, 2025, 4:42pm UTC](https://community.hubspot.com/t/goal-report/137777/6 "2025-08-11T16:42:17Z")
Hi @Jaylin, Thank you for posting to the Community! I’d love to tag in some of our Reporting experts to take a look here - @KTownsend @louischausse and @OPerek-Clark - Do you have any suggestions on this? Cassie, Community Manager ---
**Author:** ![SanjayKumar](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/sanjaykumar/32/16943_2.png) [@SanjayKumar](https://community.hubspot.com/u/SanjayKumar)\ **Post date:** [August 13, 2025, 4:41am UTC](https://community.hubspot.com/t/goal-report/137777/7 "2025-08-13T04:41:10Z")
Hi @Jaylin What you’re seeing is likely due to how HubSpot counts progress when both team and individual goals are set for the same metric. In a single-object goal report, HubSpot adds up all goal contributions without filtering out overlap - so if a deal is counted for the individual, it’s also counted again for the team. This can make the total appear twice as high compared to a monthly goal report, which only counts the unique contribution once. Here are a few ways to handle it: 1. **Choose one goal type for reporting** - If you’re reporting monthly, either track only the team goal _or_ only the individual goals for that metric to avoid duplication. 2. **Separate dashboards** - Use one dashboard for team progress and a separate one for individual performance so the numbers aren’t combined in a way that inflates totals. 3. **Custom reporting filter** - In a custom report, apply filters to exclude either the team or individual entries when both exist for the same record. 4. **Know the limitation** - HubSpot currently doesn’t de-duplicate goal counts between team and individual goals in the single-object goal report. It’s expected behavior, not a bug. If your main aim is to compare progress, I’d recommend setting the goals separately and using custom dashboards to view them side-by-side - that way you can see both perspectives without the double-counting issue. Hope that clears up why you’re seeing the difference! Thank You!