Hour Based Attribution - Agent Module

MERITTO | AGENT MODULE

Hour Based Attribution

Set your agent windows by the hour — accurate, real-time, and calculated from the exact moment it matters.

Overview

This article explains the Hour Based Attribution feature in the Agent Module. You can now configure Attribution Windows in Hours in addition to Days — giving you more granular control over how long a lead, application, or genuine verification window stays active. This guide covers how to navigate to the settings, configure each field, understand how windows are calculated, and what to expect when you change a configuration.

Plan & Permissions

Vertical	Packages	Module	Feature Name
Higher Ed	All	User Manager	Agent Otp
Ed-Tech	All	User Manager	Agent Otp

What Has Changed

Here is a quick before-and-after summary of how attribution windows now work compared to before.

Before	After
Day-based only. No hour-level control.	Days or Hours toggle per field.
Runs on a midnight cron job.	Real-time scheduler — no midnight delay.
1 Day config could stretch 30+ hours depending on lead arrival time.	1 Day expires at 11:59 PM on the same calendar day.

Step-by-Step Flow

Step 1: Navigate to Attribution Window Settings

To update your Attribution Window configuration, open Settings and follow these steps.

Log in to Meritto.
Go to Settings.
Navigate to CRM > Agent > Attribution Window.

Step 2: Configure the Fields

The Attribution Window has three fields you can configure. Each field now has a Days / Hours toggle placed next to the numeric input. You can set each field independently.

Enter a positive whole number in the input field.
Use the toggle next to the field to select Days or Hours.
Click Save. Your settings will persist across sessions.

Note: Each field can be configured independently. For example, "Hold Existing Leads For" can be set to Hours while "Hold Application For" stays in Days.

Note: Only positive whole numbers are accepted. Decimal values are not allowed.

Step 3: How the Window is Calculated

Days mode: The window expires at the end of the same calendar day as the event — not at midnight of the following day.

Example: "Hold Existing Leads For" = 1 Day. Lead registers at 3:45 PM on April 20th. The window expires at 11:59 PM on April 20th.

Hours mode: The window is calculated from the exact timestamp of the event.

Example: "Mark a Lead Genuine Within" = 48 Hours. Lead attributed at 10:00 AM on April 20th. Agent has until 10:00 AM on April 22nd.

Example: "Hold Application For" = 6 Hours. Application initiated at 2:00 PM. Attribution expires at 8:00 PM the same day.

Note: This calculation logic applies to all new leads from the date of release. Existing leads will still work on the previous cron based logic.

Step 4: What Happens When You Change the Configuration

Attribution configuration changes are forward-looking only.

Leads captured before the configuration change will follow the old configuration.
Leads captured after the change will follow the new configuration.

Note: If you switch a field from Days to Hours and save, the value is now read in Hours. For example, 5 Days becomes 5 Hours. Update the number before saving if that is not what you intend.

Note: To ensure a smooth transition, we are automatically migrating all existing day-based configurations by adding 1 day (D+1). For example, if a college currently has 11 days configured, it will be migrated to 12 days. This is because under the old logic, 11 days effectively behaved like 12 days — so this migration maintains the same real-world behaviour.

Conclusion

Attribution Windows are no longer limited to days. With Hour Based Attribution, you can now configure each field — Hold Existing Leads For, Mark a Lead Genuine Within, and Hold Application For — in the unit that fits your workflow best. Set 6 hours for a fast campaign, 2 days for a standard lead cycle, or mix and match across fields. The control is now entirely yours.