[dynamic_help_sidebar root="leads"]

Field Intelligence – Feature Guide

/0 Comments/in , /by

1. Feature Overview

Field Intelligence provides tools for real-time reporting and visual analytics to help admins and managers monitor their field users’ productivity and movement throughout the day from the LeadSquared web app or mobile app. It includes the following key tools:

  • Distance Travelled Report – Track how far users travel each day using GPS-based calculations.
  • Field Force Insights – Get a breakdown of your users’ check-in/out status, working hours, routes, and device details directly from your LeadSquared Web and Mobile App.
  • My Teams – Monitor your team’s individual activity directly from your LeadSquared Mobile App and connect with them instantly via call, SMS, or WhatsApp.
  • Device Binding – Secure app access by binding each user to a single approved device.

With Field Intelligence, you can:

  • Visualize users’ daily routes, distance travelled, check-ins, tasks, activities and customer visits.
  • Understand how users’ work hours are spent: on travel, customer interaction, or idle time.
  • Contact the user directly from the LeadSquared Mobile App.
  • View user activity on an interactive map for better field oversight.
  • Ensure data security by binding a user to one device.
Note: Field Intelligence is not available by default. To enable it, contact us at support@leadsquared.com.
Distance Travelled Report Field Force Insights My Teams Device Binding
Availability Web Only Web & Mobile Mobile Only Web Only
Enablement Enabled automatically along with Field Intelligence Enabled automatically along with Field Intelligence Must be enabled separately after enabling Field Intelligence Must be enabled separately after enabling Field Intelligence
Access Admins, Sales Managers, Sales Group Managers / Reporting Managers, Sales Users (determined by the user’s role) Admins, Sales Managers, Sales Group Managers / Reporting Managers, Sales Users (determined by the user’s role) Sales Group Managers / Reporting Managers Admins

 

2. Prerequisites

  • Users must have the LeadSquared Mobile App installed on their device, and location permission access must be enabled. To know more, please refer to Location Tracking on LeadSquared Mobile.
  • Admins must enable location tracking permissions for their users:
  • To get data with highest location accuracy, refer to Measures to Ensure Higher Distance Computation Accuracy in Mobile App.
  • Ensure that Track Location is enabled for relevant Custom Activities.
  • On the mobile devices, users must have Notifications turned on for the LeadSquared Mobile App.
  • Enable user check-in in your account for location tracking and distance calculation:
  • All mobile users must Check-In/Check-Out daily for the system to effectively track their location and calculate the distance travelled during the day. Distance calculation will not be initiated for the day if the mobile user has not checked in.
  • Admins must set up an automation that automatically checks out users at the end of the day if they haven’t done it manually. Refer Auto Check-In/Check-Out for Mobile.
  • To post an activity on completing a task, associate an activity to a task type. To learn more, refer Task and Activity Completion.

 

3. Distance Travelled Report

The Distance Travelled Report helps you monitor the daily travel of your field users through GPS data captured by the LeadSquared Mobile App. Displayed in a tabular format, it consolidates travel information across users, enabling better estimation of travel expenses and reimbursements.

Leadsquared - Field Intelligence

 

4. Field Force Insights

When Field Intelligence is not enabled, the Location History Tracker Report lets you monitor your field sales users’ daily activities. With Field Intelligence, Field Force Insights provides admins and managers a detailed, real-time view of each user’s day on the LeadSquared Web and Mobile App.

It enables tracking of check-ins and check-outs, viewing live route maps and total distance travelled, monitoring time spent working, traveling, or on breaks, exporting user data, and accessing device details.

Leadsquared - Field Force Insights

 

5. My Teams

The My Teams feature on the LeadSquared Mobile App empowers sales group managers or reporting managers to monitor team performance in real time, right from their mobile device. With My Teams enabled, you can —

  • View check-in/check-out status and travel summaries of the users directly reporting to you.
  • Track KPIs of users such as leads added, tasks completed, and opportunities created.
  • Instantly contact the users via call, SMS, or WhatsApp.

This mobile-only feature is especially useful for managers on the move, offering a quick snapshot of team activity and availability throughout the day.

Note: Once Field Intelligence is enabled, you must also enable My Teams separately. This feature is not available by default and will not be activated automatically with Field Intelligence.

Leadsquared - My Teams

 

6. Device Binding

Device Binding is a mobile security feature that locks each LeadSquared Mobile App login to a single, registered device. It safeguards sensitive business data, ensures accurate location tracking, and blocks unauthorized access. When a user logs in, their first device is automatically bound; any attempt to log in from another device is blocked until an admin approves or resets the binding.

Leadsquared - Device Binding

 

Any Questions?

We’d love to answer your questions or hear your own unique use cases. Feel free to share your experiences in the comments section below.

Logger Parameters in UDS

/0 Comments/in , , /by

1. Feature Overview

By default, users can only search UDS logs using a Request ID, making it difficult to trace business-critical records such as Loan ID, Customer ID, or Phone Number when issues arise. This slows down investigations, increases developer dependency, and delays resolution.

Logger Parameter solves this by allowing users to define up to three custom key-value pairs (like Loan ID, Applicant ID, or Phone Number) along with the Request ID.

This empowers admins to instantly locate relevant records, reduce error resolution time, and minimize reliance on developers. As a result, it helps maintain data integrity, prevent workflow disruptions, and ensure a smoother experience.

Note: Logger Parameters are available in new versions of UDS flows. Older flows and Lead Capture connectors will include this feature in upcoming releases.

 

2. Configure Logger Parameter

2.1 Access Advanced Options

Logger Parameters are available under Flow Advanced Options. Navigate to UDS App>Flow card(â‹® menu)>Advanced Options>Logger Parameter.

Note: Advanced Options are a request-only feature. Contact your account administrator or support@leadsquared.com to enable them.

2.2 Add Logger Parameters

Up to three keys can be configured. Parameters can be mapped using dropdowns or custom mappings.

Keys may be selected from:

  • Request data fields
  • Headers
  • Query parameters
  • Action response fields.
Note: Logger parameters won’t capture mapped values if encryption (webhook or action request response) is enabled.

2.3 Save Configuration

Once parameters are added and saved, they are automatically logged with every request.

navigate to and configure logger parameters

2.4 Custom Mapping

You can define custom keys in Logger Parameters to capture specific values from the incoming request.

For example, you can capture values from the request URL’s query string in Logger Parameters. If the incoming request is:

https://webhook.leadsquared.com/api/v2/uds?entityType=Loan&partnerId=ACME001

You can configure the Logger Parameters as follows:

Key Name Source Custom Key
EntityType Query entityType
PartnerId Query partnerId

custom mapping logger

 

3. Using Logger Parameters in Logs

On the Logs screen, search is available for Request ID by default, and Logger Parameters will appear as additional searchable fields.

Notes

  • A maximum of three Logger Parameters can be configured per flow.
  • Only exact matches are supported in searches.

logger navigating to logs

 

Any Questions?

Did you find this article helpful? Please let us know any feedback you may have in the comments section below. We’d love to hear from you and help you out!

How to Secure Sensitive Data with Field-Level Encryption

/0 Comments/in /by

1. Feature Overview

LeadSquared’s Field-Level and File-Level Encryption (FLE) enhances data security by encrypting sensitive information at the individual field level. This ensures that critical data, such as identification numbers, attached documents or financial details, remain protected from everyone outside your organization.

This feature enables secure storage and access to sensitive data across Leads, Opportunities, and Activities. Encryption can be applied to both system and custom fields, as well as Lead CFS. Additionally, LeadSquared supports Bring Your Own Key (BYOK) through AWS Key Management Service (KMS), allowing organizations to manage and control their own encryption keys for advanced security and compliance.

Example

Suppose your sales team collects customers’ PAN Numbers and Bank Account Details in LeadSquared. With Field-Level Encryption enabled, when a PAN Number like ABCPD1234F is entered, it’s stored encrypted (e.g., M7p9aZ1Qw==).

Leadsquared - Field Level Encryption

 

2. Prerequisites

  • Field-Level Encryption is not available by default. Reach out to support@leadsquared.com to get it enabled.
  • You must be an Admin to configure Field-Level Encryption.
  • If you’d like to control your own Encryption Key instead of generating from LeadSquared directly, you can get it through AWS Key Management Service (KMS).

 

3. How It Works

  1. The admin configures the Encryption Key in the Key Management page and selects the fields to be encrypted in the Web App Settings.
  2. When a user enters data into an encrypted field (including fields in Leads, Opportunities, or Activities), the CRM automatically encrypts the data before saving it.
  3. The encrypted value is securely stored in the database or storage system.
  4. When user accesses the record, LeadSquared decrypts the data using the configured encryption key (including BYOK if enabled via AWS KMS).

 

4. What Can Be Encrypted

Field-Level Encryption can protect the following types of sensitive data (non-exhaustive list):

Full Name, Phone/Mobile, Email, Address, PAN, Aadhar, ABHA, DL, Voter ID, SSN, Passport, Bank & Credit Card Info, Vehicle Plate Number, etc.

Entity Maximum Fields Supported Fields & Data Types
Lead / Object 10 fields per type System Fields: First Name, Last Name, Phone, Mobile, Email, Facebook, Google Plus, Google Talk User, LinkedIn, Latitude, Longitude, Skype Name, Twitter

Default Custom Fields: Address 1, Address 2, City, State, Country, Zip, Job Title, Company

Custom Fields: Text, Number, Email, Phone, Date, CFS
Opportunity 10 fields per type Custom & CFS Fields: Text, Number, Email, Phone, Date
Custom Activity 10 fields per type Custom & CFS Fields: Text, Number, Email, Phone, Date
Sales Activity 10 fields Custom Fields: String, Number, Date
File Maximum File Size: 2 GB All file types

 

5. Field-Level Encryption Settings

To access Field-Level Encryption Settings, navigate to Settings>Data Management & Privacy>Field Level Encryption.

Leadsquared - Field Level Encryption

5.1 Key Management

Once Field-Level Encryption is enabled, the admin can configure the encryption by entering an Encryption Key which can either be directly generated from here or be imported from any Key Management System. This key is used to convert data (like a customer’s phone number or ID) into unreadable encrypted text when stored in the database, and to decrypt it back into readable form for authorized users.

Leadsquared - Field Level Encryption

5.1.1 Key Generation

If you select the Generate Key option, then the Encryption Key will be automatically generated. If required, you can change the key periodically by clicking the Rotate Key option. Once you update the new key, the ability to make changes to the key will be restricted for 90 days.

Leadsquared - Field Level Encryption

5.1.2 Key Import

if you select the Import Key option, you can Bring Your Own Key (BYOK) through AWS Key Management Service (KMS) copied from AWS Key Management Service (KMS) and click Import Key. If required, you can import a new key periodically by clicking the Import Key option. Once you update the new key, the ability to import a new key will be restricted for 90 days.

Leadsquared - Field Level Encryption

5.2 Encryption Key History

View a log of all the updates that were made to the encryption key. Here you can see –

  • Key Version – The version of the key based on the number of times it was updated
  • Created Via – The method through which the encryption key was entered
    • Key Generation – Either Key Generation or Manual Key Rotation
    • Key Import – Import
  • Created On – The date and time when the encryption key was created
  • Created By – The admin user who created the encryption key

Leadsquared - Field Level Encryption

5.3 Encrypted Fields

View the Lead, Opportunity and Activity fields marked for encryption in dedicated tabs. The tabs contain grids with the following details –

  • Field Name – Name of the field
  • Schema Name – Unique identifier assigned to a field
  • Field Type – Either Custom or System (specific to Lead Fields)
  • Data Type – Text, Number, Email, Phone or Date
  • Encryption Status – Either Encrypted or Queued for Encryption (Encrypting)

Leadsquared -Field Level Encryption

 

6. Select Fields to be Encrypted

After configuring the Encryption Key, the admin must select the relevant Lead / Object, Lead CFS, Opportunity and Activity Fields to be encrypted from the Web App Settings.

Note:

  • There is a hard limit of 10 encrypted fields per Lead / Object, Opportunity, or Activity Type. If you attempt encrypt a field on reaching this limit, you will face an error.
  • When you enable encryption for an existing field, the system creates an encryption request that will be processed in the background. However, for newly created fields, encryption is applied immediately once you select the Encrypt Field option during field creation.
  • File Level encryption is supported only for the files stored in LeadSquared storage and it is applicable only to the files uploaded to CFS and Attachments after the enabling the encryption.

6.1 Encrypt a Lead / Object Field and Custom Field Set (CFS) Field

To secure a lead field –

  1. Navigate to Settings>Leads>Lead Fields.
  2. Click the Leadsquared - Actions Actions icon alongside the relevant system or custom lead field and select Edit.
  3. On the Edit Lead Field page, under Lead Field Properties, check the box alongside Encrypt Field.

Similarly, to secure a Lead CFS field –

  1. Click the Leadsquared - Actions Actions icon alongside the relevant custom field set and select Edit.
  2. On the Edit Lead Field page, under Lead Field Properties, check the box alongside Encrypt Field.

Leadsquared - Field Level Encryption

6.2 Encrypt an Opportunity Field

To secure an opportunity field within an opportunity type –

  1. Navigate to Settings>Opportunities>Opportunity Types.
  2. Click the Leadsquared - Actions Actions icon alongside the relevant opportunity type and select Edit.
  3. On the Field Configuration Tab in the Update Opportunity Type popup, click the Leadsquared - Actions Actions icon alongside the relevant field.
  4. Check the box alongside Encrypt Field.

Leadsquared - Field Level Encryption

6.3 Encrypt an Activity Field

To secure an activity field –

  1. Navigate to Settings>Leads>Custom Activities & Scores.
  2. Click the Leadsquared - Edit Icon Edit icon alongside the relevant activity type.
  3. On the second page of the Update Custom Activity Type popup, click the Leadsquared - Actions Actions icon alongside the relevant field.
  4. Check the box alongside Encrypt Field.

Leadsquared - Field Level Encryption

 

7. View Request History

To see the details about your existing field encryption request, navigate to Settings>Profile>Request History.

Leadsquared - Field Level Encryption

 

8. Limitations

  • Global & Quick Search: The Quick Search, Global Search, and Advanced Search features may not function correctly while encryption is in progress.
  • Advanced Search: Only the operators Equals, Not Equal, Contains Data, and Does Not Contain Data are supported. All other operators are not available for encrypted fields.
  • Search Limitations During Encryption: The Quick Search, Global Search, and Advanced Search features may not function correctly while encryption is in progress.
  • Sort/Filter: Sorting and filtering are disabled for encrypted fields.
  • Reporting: In some cases, encrypted fields may display ciphertext if the report or integration does not handle decryption.
  • Uniqueness: Only the system fields Email, Phone, and Mobile can be marked as unique if encrypted. Any other field marked as unique cannot be encrypted.
  • Uniqueness Criteria Impact: If unique fields (such as Phone, Mobile, or Email) are marked for encryption, the uniqueness validation will not work until the encryption process is complete. This can lead to duplicate records being created. It is strongly recommended to pause record creation and updates while encryption is in progress on unique fields to avoid data inconsistencies.
  • Audit: Historical audit records created before encryption was enabled will remain unencrypted. Encryption applies only to new audit entries generated after the field has been encrypted.

 

Any Questions?

Did you find this article helpful? Please let us know any feedback you may have in the comments section below. We’d love to hear from you and help you out!