# Reporting Configuration
#### New Activations of these settings will be Disabled as of December 25, 2025.
### Attribute All Goal Completions
• **Default Behavior** (ON): attributes each goal completion separately.
**Example**:
In the same scenario, attribution includes touchpoints leading up to both the January 1st and January 6th goals, providing a more comprehensive view of how touchpoints contribute to successive completions.
**Example**:
A user completes a “Purchase” goal on January 1st and again on January 6th. Attribution by default will only consider the touchpoints leading up to the January 1st goal, while touchpoints associated with the January 6th goal are ignored.
**Why is this useful?**
When enabled, this setting ensures all meaningful touchpoints are attributed to multiple goal completions, such as repeat purchases or recurring engagement. This is especially important for businesses with long-term customer interactions or multiple milestones (e.g., SaaS subscriptions or recurring purchases). If disabled, only the first goal completion and its touchpoints are used, which may overlook the impact of subsequent interactions.
### Use First Goal Date In Attribution
This setting controls how similar goal actions on the same date are attributed.
• **Enabled** (ON): For each goal completion attribution date's are limted to the first goal action date
• **Disabled** (OFF - **Default**): Attribution ends at each goal completion's action date
#### **Scenario**:
When ON, if a user clicks on several LinkedIn and Google ads and submits a contact form multiple times in *one* day:
• With this setting **OFF**, use each goal's completion date in the attribution window
• With this setting **ON**, truncate attribution windows to end at the first goal completion date in a journey for all goals analyzed. This automatically turns on attributing all goal completions.
**Caution**: Do not enable this if you only want the first goal completion -- turn off attributing all goal completions. If you have multiple MQLs per journey this will still pick those up into the report.
#### Why Use It?
You want to breakdown and aggregate all goal completions, but you need to limit attribution window analysis to the first goal completion date.
### Add 24 Hour Buffer To Attribution Date
This setting ensures touchpoints that occur shortly after the goal completion date are still attributed, addressing scenarios where timing discrepancies might otherwise exclude valid interactions.
• **Enabled** (ON): Adds a 24-hour buffer to the attribution goal date, treating it as if it extends into the next day.
• **Disabled** (OFF - **Default**): No buffer is applied, and touchpoints after the goal completion date are excluded.
#### **Scenario**:
Imagine a deal is created on **January 1st**, and the user has a website session on **January 2nd**.
• With this setting **OFF**, the website session would not be attributed to the deal because it occurred after the creation date.
• With this setting **ON**, the 24-hour buffer allows the session to still be attributed to the deal, recognizing it as part of the user journey leading to the conversion.
### Use Opportunity Contact Role In Attribution
This setting determines whether only contacts explicitly tied to a deal (via their opportunity contact role) are included in attribution.
• **Enabled** (ON): Only touchpoints from contacts assigned a role in the deal are attributed.
• **Disabled** (OFF - **Default**): All user touchpoints leading up to the deal are attributed, regardless of their role.
#### Scenario:
If a deal involves a primary decision-maker and other team members interacting with your content:
• With this setting **OFF**, touchpoints from all users (e.g., decision-makers and general employees) are attributed to the deal.
• With this setting **ON**, only the touchpoints from users explicitly assigned a role in the deal are attributed, ensuring a more focused view.
### Use Primary Opportunity Contact Role In Attribution
This setting refines attribution further by focusing solely on the primary contact role for a deal.
• **Enabled** (ON): Only touchpoints from the primary contact assigned to the deal are attributed.
• **Disabled** (OFF): Behavior depends on the useOpportunityContactRoleInAttribution setting—either all roles or no role-specific filtering is applied.
#### Scenario:
If a deal has multiple contacts (e.g., a manager and team members):
• With this setting **ON**, touchpoints from the primary decision-maker (e.g., the manager) are attributed.
• With this setting **OFF**, touchpoints from all assigned roles may be included, depending on the broader configuration.
### Include Company Level Actions In Attribution
This setting determines whether **company-level actions** (not tied to specific users) are included in attribution.
• **Enabled** (ON): Includes company-level actions in attribution (e.g., company-wide email campaigns or organizational-level engagement).
• **Disabled** (OFF - **Default**): Excludes company-level actions, focusing solely on individual user touchpoints.
#### **Scenario**:
If a B2B company sends a marketing email to the entire organization and a deal is later created:
• With this setting **ON**, the email is attributed to the deal as a touchpoint, providing insight into how organizational-level actions influenced the outcome.
• With this setting **OFF**, only individual user actions (e.g., website visits or form submissions) are attributed.
### Include Actions From Future Dates
Allow reports to show actions from future dates
• **Enabled** (ON): Show all future actions in the time range of the report.
• **Disabled** (OFF - **Default**): Only show past actions in the time range of the report.
### Starting Month of Fiscal Year
• **Default Setting**: January
Specify the starting month of the fiscal year your analytics data will be shown in.\
\
• **Why is this useful?**
Allows you to change the starting month to align with your fiscal calendar automatically in reporting. Useful when evaluating quarterly and anual trends.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.hockeystack.com/marketing-intelligence/settings/reporting-configuration.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.