1. These fields are non-editable, foundational data points generated and maintained by the system during the lead's entire lifecycle (registration, assignment, application, and enrollment).
2. These fields are visible and utilized across key modules, including Lead Manager, Application Manager, and Opportunity Manager.
3. Understanding these system-generated fields is helpful for the users for building robust reports and configuring advanced filters within the CRM.
   

Navigation & Access

Core Feature Functionality

1. Lead Id: The unique, system-generated identifier for the lead record. Essential for all API interactions and referencing individual leads.
   
2. User Id: The internal unique ID for the lead record.
   
3. Lead Status: The verification status of the lead (e.g., Unverified, Verified).
   
4. Mobile verification status: The verification status of the mobile number (e.g., Not Verified, Verified).
   
5. Mobile Verified Through: Indicates the method used to verify the mobile number (e.g., OTP, Direct Link, Telephony, ChatBot, Whatsapp, Login OTP, Verification Link, Amplify).
   
6. Email verification status: The verification status of the email address (e.g., Not Verified, Verified).
   
7. Email Verified Through: Indicates the method used to verify the email address (e.g., Login OTP, Direct link, Verification Link, Click Event, ChatBot).
   
8. Registration channel: The source or channel through which the lead registered (e.g., Facebook, LinkedIn, etc).
   
9. Registration device: The type of device used by the applicant during registration (e.g., Desktop, Mobile, Tablet).
   
10. Widget Name: The name of the specific Webform (Widget) used by the applicant for enquiry or added a lead (only applicable when lead is added via widget).
    
11. Form Interested In: The specific Application Form the lead is interested in.
    
12. Form Initiated: If the lead has initiated the application form it will be marked as Yes else it will  be No.
    
13. Application Submitted: Once an application is submitted by the lead it will be marked as Yes else it will be No.
    
14. Payment Approved: When the Payment for an application form of a lead has been approved then the Payment Approved is shown as Yes else it is shown as No.
    
15. Lead Score: The calculated score assigned to the lead, typically based on actions, profile completeness, or lead quality rules.
    
16. Enrolment Status: Based on configurable conditions of the Application Stages and those conditions are fulfilled by the application of the lead it is marked as Yes else it is marked as No.
    
17. Alternate Mobile: The secondary contact number provided by the applicant.
    
18. Lead Owner/Teams: The Name of the counselor the lead is currently assigned to.
    
19. Created By: The Name of the counsellor who initially created the lead.
    
20. User registration Date: The date and time when the lead record was initially created.
    
21. Last Modified Date: The date and time of the last modification made to the lead.
    
22. Lead verification date: The date and time when the lead's email or mobile number was verified.
    
23. Assign / Re-Assigned by: The Name of the counselor or admin who performed the most recent lead assignment or re-assignment.
    
24. Lead Assignment Date: The date and time when the lead was most recently assigned to a counselor.
    
25. Re-assigned: A status indicating if the lead has been re-assigned to a new owner at least once (Yes/No).
    
26. Previous Lead Owner: The Name of the counselor who owned the lead immediately before the current assignment.
    
27. First Lead Owner: The Name of the very first counselor the lead was assigned to.
    
28. Lead Stage: The current primary stage of the lead (e.g., Hot, Cold, Application Submitted, etc.).
    
29. Lead Sub Stage: The current secondary stage within the primary Lead Stage, providing granular status detail.
    
30. Remark: The most recent manual note or comment added to the lead record.
    
31. Lead Follow-Up Date: The scheduled follow-up date set by the counselor for this lead.
    
32. Last Lead Follow-Up Date: The activity date of the last follow-up marked complete by the user. Only used when single follow-up configuration is enabled.
    
33. Last Lead Activity Date: The date and time of the last recorded activity performed by the student.
    
34. Last User Activity Date: The date and time of the last activity performed by a counselor on the lead record.
    
35. First User Touch Point Time: The date and time of the first interaction (e.g., first stage change or contact attempt) recorded by a counselor.
36. First User Touch Point Status: The status of the very first interaction recorded by a user/counselor.
37. Previous Lead Stage: The Lead Stage the lead was in immediately before the current stage.
    
38. First Lead Stage: The initial stage of the lead upon creation.
    
39. Zone: The geographic zone of the lead.
40. IP Address: The IP address automatically captured when the user submitted a form or registered.
    
41. Current Url: The URL of the page the applicant was on when they performed the latest registration or form submission.
    
42. Primary Registration Campaign: The primary marketing campaign that led to the registration.
    
43. Secondary Registration Campaign: The secondary marketing campaign associated with the lead.
    
44. Tertiary Registration Campaign: The tertiary marketing campaign associated with the lead.
    
45. Latest Registration Campaign: The most recent marketing campaign associated with the lead.
    
46. Publisher Name: The name of the publisher (e.g., Google Ads, Direct, etc) associated with the lead's registration source.
    
47. Primary Traffic Channel: The traffic channel associated with the primary publisher that brought the lead to the system during their first registration.
    
48. Secondary Traffic Channel: Captures the traffic channel for a lead’s second interaction; this updates only if the source, lead origin, or publisher changes, otherwise it remains as it was before.
    
49. Tertiary Traffic Channel: Captures the traffic category for a lead’s third interaction; this updates only if the source, lead origin, or publisher changes, otherwise it remains as it was before.
    
50. Latest Traffic Channel: Displays the most current traffic channel value, matching the Primary for first-time registrations and updating as a lead reaches a Secondary, Tertiary and subsequent registrations.
    
51. Campaign Instance: Categorises a registration as a Primary Instance for the lead's first interaction, as a Secondary Instance for the second interaction, or as a Tertiary Instance. Instance for the third interaction using an existing email or mobile ID.
52. Secondary Registration Date: The date and time of the secondary campaign touchpoint.
    
53. Tertiary Registration Date: The date and time of the tertiary campaign touchpoint.
    
54. Latest Registration Date: The date and time of the latest campaign touchpoint.
    
55. Registered Country: The specific country at the exact time of the lead's registration.
    
56. State: The state at the exact time of the lead's registration.
    
57. City: The city at the exact time of the lead's registration.
    
58. Re-assigned On: The specific date and time when the lead was most recently reassigned to a new counsellor.
    
59. First User Activity Date: The timestamp of the very first manual interaction, such as a call, note, or stage change, performed by a counselor on the lead record.
    
60. Registration Attempt Date: The date and time when a user first initiated the registration process, regardless of when the record was successfully created in the system.
    
61. Lead Age: A dynamic, system-calculated value representing the total elapsed time since the lead's registration, displayed in days (d).
    
62. Account Status: The status of the account, either Blocked or Unblocked; a blocked account prevents the lead from accessing their Student Applicant Dashboard.
    
63. Registration Attempts: The total count of times a lead has attempted to register based on the system's registration attempt configuration.
    
64. Lead Strength (Percentile): The percentile ranking of a lead's score within the entire lead pool indicates their relative interest and likelihood to convert.
    
65. Registered Mobile: The primary mobile number provided and recorded by the lead at the time of registration.
    
66. Registered Email: The primary email address provided and recorded by the lead at the time of registration.
    
67. Lead Response: A field that updates based on the lead's current status and configuration, and based on that lead be visible to the agent.
68. Lead origin: The primary source or origin channel of the lead (e.g., Online, Offline, Webform (Widget) etc.).
    
69. Lead Type (Secondary): The secondary source or origin channel of the lead.
    
70. Lead Type (Tertiary): The tertiary source or origin channel of the lead.
    
71. Lead Origin (Latest): The most recent source or origin channel of the lead.
    
72. Followup Count: The total number of follow-ups recorded against this lead.
    
73. Stage Change Count: The total number of times the Lead Stage has been changed for this lead.
    
74. Notes Count: The total number of notes added to the lead record.
    
75. Outbound Missed: The count of unsuccessful outbound call attempts.
    
76. Outbound Success: The count of successful outbound call attempts.
    
77. Inbound Missed: The count of missed inbound call attempts.
    
78. Inbound Success: The count of successful inbound communication attempts (e.g., answered inbound calls).
    
79. Total Outbound: The total number of outbound call attempts (Missed + Success).
    
80. Total Inbound: The total number of inbound call attempts (Missed + Success).
    
81. Campaign Missed: The count of attempts missed related to marketing campaigns.
    
82. Campaign Success: The count of successful attempts related to marketing campaigns.
    
83. Total Campaign: The total number of attempts related to marketing campaigns (Missed + Success).
    
84. Utm Adgroupid: The platform Ad Group ID captured from the UTM parameters.
85. Utm Creativeid: The platform Creative ID captured from the UTM parameters.
86. Utm Device: The device type (e.g., 'c' for desktop, 'm' for mobile) captured from the UTM parameters.
87. Utm Network: The ad network type captured from the UTM parameters.
88. Utm Campaignid: The Campaign ID captured from the UTM parameters.

1. Utm Matchtype: The keyword match type (e.g., 'e' for exact) captured from the UTM parameters
2. Utm Keyword: The specific keyword that triggered the ad, captured from the UTM parameters.
3. Utm Placement: The site where the ad was shown, captured from the UTM parameters.
4. Gclid: The Google Click Identifier used for connecting ad performance data.
5. Fbclid: The Facebook Click Identifier used for connecting ad performance data.
6. Fbleadid: The Facebook Lead Ad Identifier used for connecting lead generation data.
   

Calender Pro Filters:

These filters are directly tied to the event lifecycle managed within the Calendar Pro module. They query the activity table to determine a lead's current nurturing status.

1. Event List: This filter fetches leads based on the specific types of events configured in the system (e.g., Followup, Counseling Call, Campus Visit, Personal Interview). It allows users to segment leads who have a particular category of interaction scheduled or recorded.
2. Event Status: This determines the current state of a lead’s follow-up. It categorizes leads into segments such as Upcoming (future-dated), Overdue (past-dated but not closed), or Completed. It is a vital tool for counselors to prioritize their daily task lists.
3. Event Scheduled Date: This queries the planned date of the event. It is primarily used for timeline-based filtering, allowing users to view leads with activities scheduled for today, this week, or any custom date range.

Lead Engagement Filters

These are "system-trigger" fields used to monitor counselor productivity and the transition of a lead from a passive record to an active prospect.

1. Lead Engaged Status: This is a binary status (Engaged/Unengaged). A lead is marked as "Engaged" only when a user performs a manual action, specifically adding a Note or scheduling an Event/Follow-up.
   

Note: This filter is frequently used in combination with the Team/Owner filter to audit whether a counselor has initiated contact with their assigned bucket of leads.

1. Lead Engagement Date: This captures the first-instance timestamp (date and time) of the engagement trigger mentioned above. It provides a baseline for "Speed to Lead" reporting, showing exactly when the first meaningful interaction occurred after the lead entered the system. Summary for Internal KB Integration.
   

When documenting these for users, we should emphasize that these values are automated based on behavior. If a counselor has not added a note or scheduled a task, the lead will remain "Unengaged" with no "Engagement Date," even if the lead has been assigned to them for several days.

Data Management Filters

1. Lead Merged: This is a binary (Yes/No) filter used for data hygiene. When duplicate leads are consolidated, this flag identifies the primary record or reflects the merge status. It allows users to exclude merged records from lists to ensure accurate, unique lead counts in reporting.
   

Business Relevance

Leveraging the details captured in these system fields provides significant benefits for analysis and workflow management across all enrollment stages:

1. Enabling Performance Analysis: Fields like Lead Score, Stage Change Count, and Total Call Duration provide the critical metadata needed for in-depth performance analysis. Their availability across the Lead, Application, and Opportunity modules ensures end-to-end reporting, enabling your organization to measure the true cost of conversion and optimize resource allocation.
2. Ensuring Workflow Transparency: Fields such as Lead Assignment Date, Last Lead Follow-Up Date, and Previous Lead Owner ensure transparent lead ownership and activity tracking. This allows your team to quickly assess lead history and prioritize follow-up efforts based on the last recorded interaction.
3. Supporting Data Exchange and Integration: Fields like Lead Id, Field Keys, and UTM parameters provide the necessary structural identifiers for accurate data exchange and connecting your CRM data back to your external marketing platforms (like Google Ads or Facebook) for precise ROI measurement and campaign attribution.
   

Conclusion

These system fields provide the foundational data points necessary for every advanced operation within the Meritto Lead module. By leveraging the specific details found in these fields, you can build highly targeted reports, automate workflows, and optimize your overall lead management strategy.