Portals and Landing Pages Pro are modular and can be altered, extended, or enhanced using JavaScript. They can be extended to accommodate additional functionality like –
Portals and Landing Pages Pro broadcast specific engagement activities during the lead journey which can be subscribed to and posted to the respective analytics service.
Integrating third-party chatbot services.
Fetching/Updating data from external databases or apps using JavaScript.
Overriding the style of a specific component inside the designer using your own custom scripts.
2. Integrating Google Analytics and Facebook Pixel on Portals
On integration, both Google Analytics and Facebook Pixel track pageviews, visitor count, and other basic events. However, in order to track custom engagement or conversion activities, you must write custom push events specific to the analytics service.
Paste the script obtained in the Inside Head and End of Body sections as per the specifications.
4. Troubleshooting
4.1 Frequent Issues Encountered
Wrong trigger configuration: The conditions you have targeted must be present for the expected trigger behaviour.
Extra specific triggers: Triggers must not be too specific. Example: A URL trigger that is set to fire on http://www.example.com will not fire if the URL is https://www.example.com . Use a common fragment for the trigger criteria, such as “example.com”.
4.2 Issues Encountered with Facebook Pixel
Refer to the following checklist to ensure that Pixel is firing properly.
Check whether your raw pixel fires match. If you’re using Facebook pixel, you can check how many times your specific standard events were triggered in your pixel dashboard.
If your raw pixel fires match but there’s a discrepancy in conversion values, check your currency, decimal places, and other variables in your purchase event codes.
Do not use a combination of conditional and unconditional firing with your tags. Also, expect minor discrepancies while using conditional firing.
If Facebook is reporting more conversions than your other analytics tools, use the Pixel Helper tool to check for duplicate pixel fires, which can sometimes be caused by redirects.
The tools mentioned below can be used to debug Google Analytics and Facebook Pixel.
Facebook Pixel Helper – Works in the background to look for conversions or Facebook pixels and provides real-time feedback on the implementation.
Google Tag Assistant Recordings – Validates, diagnoses, and troubleshoots issues with your Google Analytics implementation in real-time. You can record typical user flows through your website and get an immediate analysis of your setup. Google Tag Assistant Recordings can help you find missing or mangled tags, invalid events, filters, and much more.
5. Overriding the Style of Portal and Landing Page Pro Components with Custom Scripts
You can use custom JavaScript to override a style property of a component that is not available in configurations. To override the CSS properties of a component, use its class name. The properties will be applied to all components with the class name. If you want to isolate this to a specific component, set a custom class name to the component and use this class with JavaScript to style it.
Select a portal component and tag it with a custom CSS class name –
Click the Advanced dropdown and enter a value in the Custom class name field.
Use this class name in your custom scripts to isolate and override its style and behavior without affecting any other components in the portal.
6. Extending Portals with Custom Behaviour
Portals track various engagement events performed by leads. You can consume these events via custom scripts and –
Post them to –
Analytics services like Google Analytics
Advertisement services like Facebook Ads
Display a pop-up message on the portal, etc.
Trigger
Event Name
Event Payload
When a user logs in to the portal successfully
LSQ_FORM_LOGIN_SUCCESS
Login method – otp, password
When a user initiates portal login
LSQ_FORM_LOGIN_INITIATED
Login method – otp, password
When a user fails portal login
LSQ_FORM_LOGIN_FAILURE
Login method – otp, password
When a user verifies email or phone number through OTP on the portal during registration
LSQ_OTP_VERIFIED
Verification type – signup, login
When a user initiates portal registration
LSQ_FORM_SIGNUP_INITIATED
Sign up method – otp, password
When a user registers on the portal successfully
LSQ_FORM_SIGNUP_SUCCESS
Sign up method – otp, password
When a user fails to register on the portal
LSQ_FORM_SIGNUP_FAILURE
Sign up method – otp, password
When a user raises forgot password request through the portals successfully
LSQ_FORM_FORGOTPASSWORD_SUCCESS
–
When a user fails to raise forgot password request through the portals
LSQ_FORM_FORGOTPASSWORD_FAILURE
–
When a user resets the portal password successfully
LSQ_FORM_RESETPASSWORD_SUCCESS
–
When a user fails to reset the portal password
LSQ_FORM_RESETPASSWORD_FAILED
–
When a form is loaded on the portal
LSQ_FORM_LOAD_COMPLETE
form name
When a form is saved on the portal, use the lsqformsubmissionsuccessateachstep event on .lsq-external-form-container, like this:
document.querySelector(".lsq-external-form-container").addEventListener('lsqformsubmissionsuccessateachstep', () => {
console.log("Form saved on the portal.");
});
There will be no event payload.
When a form is submitted on the portal
LSQ_FORM_SUBMITTED
form name
When a form is saved as a draft on the portal
LSQ_FORM_SAVE_AS_DRAFT_COMPLETE
formName, portalId, TabId, FormId
When a user initiates payment via a payment gateway through forms on the portal
LSQ_PAYMENT_INITIATED
form name, product name, payment gateway, currency
When a user fails to complete payment via a payment gateway through forms on the portal
LSQ_PAYMENT_FAILED
form name, product name, payment gateway, currency
When a user completes a payment via a payment gateway through forms on the portal
LSQ_PAYMENT_COMPLETED
form name, product name, payment gateway, currency
When a form is saved on the portal, use the lsqformsubmissionsuccessateachstep event on .lsq-external-form-container, like this:
document.querySelector(".lsq-external-form-container").addEventListener('lsqformsubmissionsuccessateachstep', () => {
console.log("Form saved on the portal.");
});
The event payload will be:
Common event payloads to be used in all triggers –
lead id – Prospect Id of the lead performing the action
portal id – Id of the portal on which the action was performed
timestamp – The time stamp at which the action was performed
page title – Name or title of the portal page on which the action was performed
page path – Absolute path or URL of the portal page on which the action was performed
origin – default value of the portal
These events can be consumed via custom scripts written at the Portal Designer > Configurations > Script: a) Inside Head <head> b) End of body <body>
window.addEventListener("LSQ_FORM_SIGNUP_SUCCESS", (event) => {
console.log("Printed when user has registered.", event.detail);
// Your logic goes here. Push Google Analytics / Facebook Pixel events here or any other custom behaviour you intend to achieve.
// Example: Track a Google Analytics Event
//gtag('event','portal_sign_up',{'event_category':'admission_portal', 'event_label':'2022_admission'});
// Example: Track a Facebook Pixel Event
//fbq('track','ViewContent',{content_name:'Sign Up Form'});
});
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!
https://help.leadsquared.com/wp-content/uploads/2026/04/340-x-156-300x138-1.webp00Dharshana Santhanamhttps://help.leadsquared.com/wp-content/uploads/2026/04/340-x-156-300x138-1.webpDharshana Santhanam2022-07-27 17:52:562026-05-20 00:31:05Using Scripts in Portals and Landing Pages Pro for Google Analytics, FB Pixel, Chatbots and Other Custom Behaviour
LeadSquared SMS Connectors facilitates customer support and other marketing efforts through simple, secure and reliable text messages. This connector lets you integrate popular SMS providers with your LeadSquared account to send automated, one-to-one and bulk SMSes to leads and opportunities in India, directly from LeadSquared.
The following SMS providers are currently supported –
Important Note: In this article, we’ve used Gupshup as an example to demonstrate the installation and set-up process. The steps remain the same for all the other SMS providers, unless stated otherwise.
2. Prerequisites
To enable an SMS provider’s connector on your account, contact your account manager or write to support@leadsquared.com.
You must be an administrator user of your Leadsquared account.
Set up the connector by providing your SMS provider’s account details (Transactional and Promotional usernames, API Keys and Tokens, passwords, Principal Entity ID, DLT-approved Sender ID, etc.). Once it’s set up, create and configure the DLT-approved SMS templates you’ll be using to message your leads. After these templates are configured, send SMSes to your leads.
Search for the SMS connector you want to install*, and click Install.
Alternatively, you can find the connector on the left panel, under SMS.
Then, click Configure.
On the Configure SMS Connector pop-up, no further action is required on this page. To configure the connector, navigate to Apps>Configure SMS Connector.
5. Configure the Connector
Once the connector is installed, navigate to Apps>Configure SMS Connector, and provide the following details for the SMS provider you’re looking to configure –
Transactional Username and Password – Your Gupshup Transactional SMS (order confirmation, account creation confirmation, etc.) account’s username and password.
Promotional Username and Password – Your Gupshup Promotional SMS (ongoing offers, product launches, etc.) account’s username and password.
Principal Entity ID – Your Gupshup account’s Entity ID. To know how to obtain this ID, contact your Gupshup account manager or refer to Entity Registration – DLT Platform.
Transactional API Key – Your Transactional account’s (order confirmation, account creation confirmation, etc.) API Key.
Promotional API Key – Your Promotional account’s (ongoing offers, product launches, etc.) API Key.
DLT Principle Entity ID – Your Karix account’s Entity ID. To know how to obtain this ID, contact your Karix account manager or refer to Entity Registration – DLT Platform.
DLT Principle Entity ID – Your Route Mobile account’s Entity ID. To obtain this ID, contact your Route Mobile account manager or refer to Entity Registration – DLT Platform.
Principle Entity ID – Your Infobip account’s Entity ID. To know how to obtain this ID, contact your Infobip account manager or refer to Entity Registration – DLT Platform.
Single SMS API key – Provide Transaction Route API Key.
Bulk SMS API key – For campaigns with an alphabetical sender, use the Transactional route API key. For campaigns with a numeric sender, use the Promotional route API key.
Note: When creating an SMS Template for MSG91 in LeadSquared, you’ll need to provide the Slug that’s generated when creating an SMS Template in your MSG91 account. To know more, refer to How to Get the Slug for MSG91 Templates.
DLT Entity ID – Your Pinnacle account’s Entity ID. To know how to obtain this ID, contact your Pinnacle account manager or refer to Pinnacle DLT Details.
Username – Name of the user that’s creating the campaign.
Keyword – The keyword associated with the SMS campaign you’re creating. To know more, refer to How does SMS marketing work?
DLT Entity ID – The account Entity ID that’s registered with the DLT platform. To know how to obtain this ID, contact your Airtel account manager or refer to Airtel DLT FAQs.
Campaign Title – The title of the SMS campaign you’re creating.
Circle Name – The circle in which the campaign is going to be carried out.
DLT TM ID – Your account’s Telemarketer ID.
Bulk Username – Your account’s username for bulk SMS campaigns.
Bulk Password – Your account’s password for bulk SMS campaigns.
App ID – The application ID that’s associated with an enterprise, which was provided by Sinch India.
User ID – The authentication user ID provided by Sinch India.
Password – The User ID authentication password provided by Sinch India.
DLT Principal Entity ID – Your Sinch India account’s Entity ID. To know how to obtain this ID, contact your Sinch account manager, or read Sinch DLT Registration.
How to get Username and Password –
On your Enablex account, all API Credentials are paired to a Project. You will first need to Create a Project to receive these API credentials. Once the Project is created, you can find the Access Credentials by referring to SMS API v1.0 References.
Username – Your V-Connect account’s Profile ID/Username.
API Key – A user-specific API key is generated for every request. Pass the key for the relevant request.
DLT PE ID – Your V-Connect account’s Entity ID. To obtain this ID, contact your V-Connect account manager, or refer to Add Principal Entity ID.
Once you’re done, click Save & Next.
5.2 Activity Creation
When SMSes are sent to your lead, an activity is posted automatically against that lead. Here, configure the activity creation method for the SMS activity.
Async API – This is the recommended method. If you’ve selected this method, enter your LeadSquared account’s Async API URL and API Key. To obtain both these values, navigate to My Profile>Settings>API and Webhooks>Async API.
Sync API – This method is selected by default. To post limited SMS activities against your lead, select Sync API.
Note:
Through the Sync API method, the activity creation process happens without any delays. But activity creation or tracking may fail during peak hours and when there’s high traffic to our servers. To work around this potential issue, we recommend you use the Async API method.
Async APIs must be enabled on your LeadSquared account for the Async method to work.
5.3 Sender Management
To add your SMS account’s Sender IDs, click Add New, and on the Add Sender ID pop-up, enter the following details –
Sender ID – Your SMS account’s DLT approved sender Id. To obtain this Id, contact your account manager.
Name – A name to identify the Sender ID (e.g., Promotional, Transactional, etc.). This is primarily for internal references. This is optional.
Sender Distribution – Select the users to whom the Sender ID will be assigned –
Based on Role – Select the LeadSquared user roles (e.g., Administrator, Marketing User, etc.) to whom you want to assign the Sender ID.
Advanced (User Level) – Select a boolean user field that’s configured in your account. If the selected user field contains the value “True” for any user, the Sender ID will be assigned to them.
To add multiple Sender IDs, repeat the steps mentioned above. Once you’re done, click Save, and click Save & Next.
5.4 Permissions
Configure the permissions you want to grant users for the Send SMS action (Single and Bulk). This action will be configured on the following pages –
Manage Leads page grid
Manage Opportunities page grid
Lead List
Automation Page
You can also configure permission you want to grant users for managing templates and reports. This action will be configured on the following pages –
Manage Templates (the SMS template creation screen)
Manage Reports (the SMS Reports screen)
Under Functionality, click on the page for which you want to configure the permissions.
On the Send SMS pop-up, provide the following details –
Action Label – Enter the display name of the SMS action (e.g., Send Text – Gupshup, Send Bulk Text – Karix, etc.). The limit on the number of characters you can add is 25.
Campaign Size – This is applicable only when sending bulk SMSes. You can send SMSes to up to 200 leads through the Lead Grid, and up to to 4 lakh (400,000) bulk SMSes through the Manage Lists page in one go.
Permission – Select if you want to enable users to Send SMS based on their user role or based on the values entered in a user boolean field.
Based on Role – Select the LeadSquared user roles based on which you want to grant Send SMS permissions.
Advanced (User Level) – Select a boolean user field that’s configured in your account. If the selected user field contains the value “True” for any user, they’ll be able to access the Send SMS action.
To disable the action for your users on any page, under Enable/Disable, disable the slider. The action cannot be disabled for the Manage Templates and Manage Reports screens.
Note: To configure the send SMS action on the Manage Opportunities grid, copy the Configurable Action Url, and use it to create a new Custom Opportunity Actions. To know more, contact your account manager or write to suport@leadsquared.com.
5.5 Advanced Settings
Compliance
The SMSes you send to your leads must meet regulatory compliance standards set by TRAI. You can either choose Opt-out or Opt-in as the compliance type. Once you select the type, from the list of boolean lead fields (e.g., ‘Do Not SMS’) available in your account, select an opt-out/opt-in field.
Leads for whom the value of the Opt-out field is set to ‘True’ will not receive any SMS. Alternatively, leads for whom the value of the Opt-in field is set to ‘True’ will receive SMSes.
Date and Time Related Details
Timezone – Select the timezone your LeadSquared account should follow when sending SMSes to leads.
Date/Time Format – Select the date and time format your LeadSquared account should follow when sending SMSes to leads.
You can define business hours during which SMSes can be sent to your leads. This step is optional.
Alongside Business Hours, enable the slider.
From the Schedule dropdowns, define the business hours.
From the Select Sender IDs dropdown, select the senders to whom this business hour definition will be applied.
Note: If Business Hours are defined, your users will not be able to send any messages outside these defined hours.
Other Details
From the Other Phone Field dropdown, select the default phone field in which the lead’s phone number is stored in your account. Once you’re done, click Save & Close.
Note: To ensure a higher deliverability rate for your SMS campaigns, ensure phone control validations are enabled for this phone number field. To learn more, see Control Phone Number Format.
6. Manage Templates
After the SMS connector is set up, add DLT Approved SMS templates which you’ll be using to message your leads.
Note:
The SMS templates you add here must be registered and approved on your SMS provider’s account.
Navigate to Apps>Manage Templates. This is the action label name you’ve configured for the Manage Templates screen (e.g., Manage Templates – Gupshup, etc.).
On the Manage Templates screen, click Add Template.
On the Add/Edit Template pop-up, enter the following details –
Category – Select the LeadSquared category type for the SMS template.
Lead – Select this if you’re using this template to send messages to leads (e.g., offers, promotions, etc.).
Opportunity – Select this if you’re using this template to send messages to opportunities (e.g., offers, promotions, etc.).
Activity – Select this if you’re using this template to send notifications about an activity (e.g., Payments, Document Collections, etc.).
Task – Select this if you’re using this template to send notifications about a task (e.g., Appointment Reminders, Follow Ups, etc.).
User – Select this if you’re using this template to send messages to users (e.g., Reminders, Company Wide Announcements, etc.).
Template Name – Provide a name for the template.
Source Availability – Select if the template should be available to send Single SMS, Bulk SMSes and SMS through Automations. You can select all three sources if required. It is mandatory to select at least one source.
SenderId – Your DLT approved Sender Id.
Template Type – Choose if the template is –
Transactional – Order confirmation, account creation confirmation, etc.
Promotional – Ongoing offers, product launches, etc.
Service Implicit – OTPs, informational messages, bookings, etc. These messages are not intended for marketing purposes.
Service Explicit – Discounts, updates, etc. These messages are for marketing purposes.
DLT Template Id – The DLT approved template Id. To get your template approved, and to obtain this Id, please reach out to your SMS provider’s account manager.
Content – Enter the DLT approved Template content/message here.
Add Variable – To add mail merge fields, click Add Variable. Variables in LeadSquared are defined as {{var}} i.e, the variable name is enclosed within two curly brackets. If the approved template contains a mail merge field “{#var#}”, then the LeadSquared mail merge value can only replace “{#var#}”, without changing anything else in the template. For e.g., “Hi {#var#}, hope you’re doing well!” can only be replaced by, “Hi @{Lead:FirstName,}, hope you’re doing well!”. We also support Custom Variables. You can use this to mail merge custom variables like the Company Name, website URLs, etc.
Once you’re done entering all the details, click Save.
Note: The maximum character limit for the DLT variables is 30 (as mandated by DLT). This is including spaces.
On the Manage Templates screen –
To edit an existing template, alongside the template, click .
To delete an existing template, alongside the template, click .
Alongside the lead you want to message, hover your cursor over . From the available options, under Messaging, click the messaging action label you’ve configured (e.g., Send Text – Gupshup, etc.).
On the Send Text pop-up –
Select the Sender Id through the From dropdown.
Under Message Body, click Select a Template, and from the list of available templates, select the one you want to use.
If there are custom variables available, check if the relevant values are mapped to each variable.
Once you’re done, click Send.
Note: The steps to send one-to-one SMS to your opportunities are the same as the ones listed above. To message your opportunities, navigate to Leads>Manage Opportunities.
Alternatively, you can also send one-to-one SMSes from the Lead Details page. To do this, hover your cursor over the Lead Actions button, and under the Messaging option, click the messaging action label you’ve configured (e.g., Send Text – Gupshup, etc.).
8. Send Bulk SMS
You can send bulk SMSes to your leads from the Manage Leads page and the Manage Lists page.
Note: At present, you can send bulk SMSes only through the following SMS connectors –
Alongside the leads you want to send the SMS to, select the checkboxes..
Hover your cursor over the Actions menu. From the available options, under Messaging, click the messaging action label you’ve configured (e.g., Send Bulk Texts – Gupshup, etc.).
On the Send Bulk Text pop-up, enter the following details –
Campaign Details
Alongside Sending messages to…, check if the correct number field has been selected. You can select multiple number lead fields.
From the From dropdown, select the Sender Id.
Alongside Campaign Name, provide a relevant name for the SMS campaign.
Under Message Body, click Select a Template, and from the list of available templates, select the one you want to use.
Alternatively, to select a template, click .
Once you’re done, click Save & Next.
Custom Params
If there are custom variables available in the template, check if the relevant values are mapped to each variable.
To edit the value for a variable, click .
Once you’re done, click Save & Next.
Review and Send – On this tab, review if all the SMS details are correct.
Once all the details are verified, click Send.
On the send SMS confirmation screen, click Yes. The SMS is sent to all the selected leads.
Alongside the list you want to send the SMS to, hover your cursor over . From the available options, under Messaging, click the messaging action label you’ve configured (e.g., Send Bulk Texts – Gupshup, etc.).
Alternatively, open a list and from the List Actions menu, click Messaging, and click the action label you’ve configured.
On the Send Bulk Text pop-up, enter the following details –
Campaign Details
Alongside Sending messages to…, check if the correct number field has been selected. You can select multiple number lead fields.
From the From dropdown, select the Sender Id.
Alongside Campaign Name, provide a relevant name for the SMS campaign.
Under Message Body, click Select a Template, and from the list of available templates, select the one you want to use.
Alternatively, to select a template, click .
Once you’re done, click Save & Next.
Custom Params
If there are custom variables available in the template, check if the relevant values are mapped to each variable.
To edit the value for a variable, click .
Once you’re done, click Save & Next.
Review and Send – On this tab, review if all the SMS details are correct.
Once all the details are verified, click Send.
On the send SMS confirmation screen, click Yes. The SMS is sent to all the selected leads.
After selecting the type of automation and the trigger, click the add icon, click Messaging, and click the messaging action label you’ve configured (e.g., Send Automation Texts – Gupshup, etc.).
After entering the required details and selecting a template, click Send SMS.
To mail merge multiple LeadSquared phone fields, click the Add Another Number button. Filter by the entity type under which the phone field is present, and use the search box to find and add the field. In the example below, we’ve mail merged the Lead Owner phone field to the automation.
Note: You can send SMS via automation through this connector only for automations created using a Lead, Opportunity, Activity, Task, or User triggers.
10. View Reports
To view the reports and logs of all the SMSes sent through the SMS connector –
Navigate to Apps>Manage Reports – SMS Connector.
You can sort the report by the following filters –
Usage Reports – The logs of the total one-to-one as well as bulk messages sent through the connector.
Templates – Filter the reports on the basis of the templates used when sending the messages.
Message Source/User Wise – Filter the reports on the basis of the message source (Automation, Bulk and One-to-one messages).
Select Date – Select the time interval for which you want to view the SMS logs data. You can select a maximum date range of up to 90-days in the past.
Cumulative – This will render the report as a pie chart.
Timeline – This will render the report as a bar graph.
For pie charts, to populate the details section, click any part of the chart.
For bar graphs, if you delete any element, the display of the graph gets updated accordingly.
Campaign Reports – The logs of all the bulk messages sent through the connector. This option will only show up if the connector supports bulk messaging.
Select Date – Select the time interval for which you want to view the SMS logs data. You can select a maximum date range of up to 90-days in the past.
Status – Filter by the campaign status (All, Success, Error, and Partial Error).
To view detailed logs of a campaign, click on the campaign. Alternatively, click the icon. On the Batch Details screen, you can perform the following actions –
To view the API details, under Batch ID (the List Id), click the entry.
To view the status of the messages triggered, under Triggered, alongside the Batch Id you want to view the details for, click the number.
Message Triggered – The total number of leads to whom the messages were triggered.
Sent – The total number of successful messages sent to the SMS provider.
Messages Billable – Every block of 160 characters in a SMS is considered as a one SMS. For e.g., if you send one SMS that contains 340 characters, it is considered as 3 messages (160+160+20) under the Messages Billable header.
Error – Any internal LeadSquared errors (e.g., server errors, etc.) that cause the Send SMS action to fail will get logged under the Errors column.
Invalid – The following scenarios when sending SMSes will get logged under the Invalid column –
Formatting issues with the lead’s phone numbers
Empty or missing lead phone numbers
Sending SMS outside the configured Business Hours
If the DLT variable lenght exceeds the configured limit
Opted Out – The total number of messages sent to leads who have opted out of receiving messages.
Note: To download/export a report, under Actions, click . The report contains the Lead Id, Phone Numbers, Opportunity Id, Message Content, Status Message, Message Type and Message Count of all the leads to whom the message was sent.
Alternatively, click on the Batch Id to download a report that contains the Lead Phone Number and Message content of the SMS sent to leads.
11. SMS Activities
You can track the SMS sent, from the Lead Details and Manage Activities pages. We automatically post SMS Sent activities in real-time.
11.1 Lead Details
To view more details, click the SMS Sent link for each activity.
11.2 Manage Activities
You can also view the list of leads with SMS activities. Be sure to select SMS Sent from the Activity Type drop.
You can use the Advanced Search feature to filter SMS based on different fields, such as campaigns, date-time fields, etc.
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!
https://help.leadsquared.com/wp-content/uploads/2026/04/340-x-156-300x138-1.webp00Sri Sudhanhttps://help.leadsquared.com/wp-content/uploads/2026/04/340-x-156-300x138-1.webpSri Sudhan2022-07-27 16:56:332024-06-28 16:39:02LeadSquared SMS Connectors – India
Sticky and Non-Sticky are two distinct types of Rulesets you can create to configure Goals. They determine how the goal achievements are calculated and attributed to your sales reps/users. Each type of Ruleset caters to a specific kind of use case.
As a general rule of thumb, Non-Sticky Rulesets are helpful when achievements must be reverted, such as in the case of almost all revenue goals (that include returns and refunds).
Sticky Rulesets are helpful when achievements have to be retained, such as in the cases of lead/opportunity stage and owner changes, where regardless of the future lead stage of the lead/opportunity or the future owner, you still want to credit the sales reps responsible for previous stage transitions.
When to Use a Sticky and Non-Sticky Ruleset?
Let’s say you want to track the number of leads your users convert into customers. You define a goal rule (count of leads) and add the condition – lead stage is ‘Customer’.
Your users start changing lead stages to ‘Customer’ and racking up their achievements.
Now, let’s assume you have a different set of users working on changing the lead’s stage from ‘Customer’ to ‘Upsell’. When these users change a lead’s stage to ‘Upsell’, the condition of your goal rule (lead stage is ‘Customer’) is no longer satisfied. The achievements attributed to your users will now be removed (Non-Sticky Ruleset) because the lead stage is no longer ‘Customer’. However, your users still deserve the credit for converting those leads into customers.
Enter Sticky and Non-Sticky! With Sticky Rulesets, the system ensures that the achievement isn’t removed from the user, even when the stage is changed to ‘Upsell’ by the next team. The system maintains an audit trail of all changes, and ensures that achievements stick (or are retained), even if the current state of the record has changed.
Example – Lead Stage Conversion
Let’s assume you have two teams, Team Customer and Team Upsell. You want to define 2 sets of lead conversion Goals where,
Team Customer must convert X number of prospects into customers
Team Upsell must convert X number of customers to upsells
Configurations
You set up these Goals using 2 different Rulesets –
The first Ruleset attributes achievements to ‘Team Customers’, based on the count of leads in stage ‘Customer’.
The next Ruleset attributes achievements to ‘Team Upsells’, based on the count of leads in stage ‘Upsell’.
Achievements
On the 1st of August, 1 new lead enters the system (the lead’s stage is Prospect).
Your sales rep from ‘Team Customer’, Ari, starts converting the lead from a prospect to a customer –
By the 2nd of August, thanks to Ari, the lead is now a customer.
Modified On Date
Leads Converted
Leads in Stage ‘Customer’
Expected Achievement
2nd August
1
1
1
On the 3rd of August, your rep from ‘Team Upsell’, Bob, converts the lead from a customers to an upsell –
Modified On Date
Leads Converted
Lead in Stage ‘Upsell’
Expected Achievement
3rd August
1
1
1
Why Non-Sticky Rulesets won’t work here
On the 3rd of August, with a Non-Sticky Ruleset, here’s what Ari’s achievements look like –
Modified On Date
Leads Converted
Leads in Stage – Customer
Actual Achievement
2nd August
1
0
0
Why is Ari’s total achievement 0?
Because the condition ‘Lead Stage is Customer’ is no longer met (Bob changed the lead stage to upsell).
Enter Sticky Rulesets
Here’s where Sticky Rulesets come in. When you make the Ruleset Sticky, on the 3rd of August, even though the current lead stage is upsell, Ari’s previous achievements will ‘stick’. His achievements will still look like this –
Modified On Date
Leads Converted
Leads in Stage – Customer
Actual Achievement
2nd August
1
0
1
https://help.leadsquared.com/wp-content/uploads/2026/04/340-x-156-300x138-1.webp00Vir Singhhttps://help.leadsquared.com/wp-content/uploads/2026/04/340-x-156-300x138-1.webpVir Singh2022-07-29 18:49:292026-04-15 12:25:23Sticky vs. Non-Sticky Rulesets
Portals allow you to fill out lengthy applications with multi-step forms. This article shows you how to save a form’s progress in each step, and how to open a specific tab when the user revisits the form after dropping off.
This is applicable to multi-step forms used within the LeadSquared application and also for forms embedded in the Portals feature.
Select the Portal you need to view and click Continue Editing.
Click on the General settings dropdown and select the relevant Form.
Click and select the page to be integrated with the Process.
Click the Integrate dropdown and select Process.
Select the LSQ Process you just published.
Click Publish to Test.
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!
https://help.leadsquared.com/wp-content/uploads/2026/04/340-x-156-300x138-1.webp00Dharshana Santhanamhttps://help.leadsquared.com/wp-content/uploads/2026/04/340-x-156-300x138-1.webpDharshana Santhanam2022-07-27 17:18:532026-04-15 13:36:35How to Save Progress for Multi-Step Forms in LeadSquared Portals
After you post a custom activity on a lead, you can lock the activity to prevent users from updating or deleting it. This is useful for activities that contain computed values, such as incentives, loans, or interest rates, or critical customer data, such as passport or Aadhaar copies. When required, you can unlock these locked activities.
Note: This setting locks and unlocks individual custom activities posted on a lead, and NOT the entire activity type. For example, as shown in the GIF below, you can lock only the “Document Collection” custom activity posted on the lead Leah, not all “Document Collection” custom activities posted in your account.
2. Prerequisite
You must be an account Admin to configure this feature.
3. How it Works
When you create or update a custom activity, on the Create/Update Custom Activity Type pop-up, enable the Lock Activity setting and select the user roles whose activity edit access you want to revoke.
Then, pass the Lock an Activity API to lock the custom activity type on which you enabled the Lock Activity setting.
Alongside the custom activity you want to lock, click the edit icon.
The steps below also apply when creating a new custom activity.
On the Update Custom Activity Type pop-up, enable the Lock Activity checkbox.
Then, select the user roles for which you want to lock the activity. Users in these roles can’t edit or delete the activity after it is locked.
Once you’re done, click Next, then click Save on the final screen.
Then, pass the Lock a Custom Activity API. After the API call succeeds, the selected user roles can’t edit or delete this custom activity posted on a lead.
Alongside the custom activity you want to unlock, click the edit icon.
On the Update Custom Activity Type pop-up, disable the Lock Activity checkbox.
Once you’re done, click Next, and click Save on the final screen.
Then, pass the Unlock a Custom Activity API. After the API call succeeds, the selected user roles will be able to edit this custom activity posted on a lead.
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!
https://help.leadsquared.com/wp-content/uploads/2026/04/340-x-156-300x138-1.webp00Sri Sudhanhttps://help.leadsquared.com/wp-content/uploads/2026/04/340-x-156-300x138-1.webpSri Sudhan2022-07-04 16:43:272026-07-07 16:48:05Lock and Unlock Custom Activities
and then Configurations.
.
slider. The action cannot be disabled for the Manage Templates and Manage Reports screens.
slider.
.
.
. From the available options, under Messaging, click the messaging action label you’ve configured (e.g., Send Text – Gupshup, etc.).
checkboxes..
.
. From the available options, under Messaging, click the messaging action label you’ve configured (e.g., Send Bulk Texts – Gupshup, etc.).
icon, click Messaging, and click the messaging action label you’ve configured (e.g., Send Automation Texts – Gupshup, etc.).
icon. On the Batch Details screen, you can perform the following actions –
. The report contains the Lead Id, Phone Numbers, Opportunity Id, Message Content, Status Message, Message Type and Message Count of all the leads to whom the message was sent.
and select Live Edit.
.
and select Show Form.
