LeadSquared

Overview

Signals writes leads captured on an ad platform or a form straight into LeadSquared, so they enter your sales process without an export step.

Signals maps each lead form field to a LeadSquared field and creates the record in the Leads module. The lead arrives with the platform lead ID attached, which is what lets you tie a LeadSquared record back to the ad that produced it.

This is the reverse of the LeadSquared source connector, which reads records out of LeadSquared to send to an ad platform.

Supported sources

Sources supported by LeadSquared

Category	Supported
Lead generation	Google Forms LinkedIn Lead Generation Forms Meta Lead Ads Snapchat Lead Generation Ads TikTok Lead Ads

Prerequisites

Before connecting LeadSquared, make sure you have:

• A LeadSquared account.
• An Access Key and a Secret Key belonging to a user with access to Leads and to the API. Administrator profiles have this by default; other profiles need it granted.
• A field in the Leads module to hold the lead ID from your source. Create it before you start.
• A Datahash Studio account with the target project selected.
• A lead generation source already connected in the same project.

Authentication

In Studio, open Destinations, find the CRM category, and click the LeadSquared tile. This connector uses key-based credentials rather than a sign-in, so the keys are yours to store and rotate.

1. Enter the Access Key and Secret Key.
2. Click Next.

Field	Where to find it
Access Key	In LeadSquared, open your profile menu in the top right, then Settings. Under API and Webhooks, open API Access Keys. The access key is shown there.
Secret Key	Same screen. Click Show Secret Key to reveal it, then copy it.

Caution

Treat both as credentials. Never share them outside the Datahash connection screen, and generate them against a service user rather than a person’s account where you can, so the connection does not break when someone leaves.

Configuration

Source and connection

1. Choose the source type, which is the lead platform or form the leads come from.
2. Select the connection name created when that source was set up.
3. Give this destination connection a name.

Leads are written to the Leads module. There is no module selection step on this connector.

Field mapping

The mapping screen puts your lead form fields on the left and the LeadSquared schema fields on the right.

LeadSquared enforces a rule of its own on top of the usual required fields: at least one of First Name, Last Name, Email Address, Phone or Mobile has to be mapped. A record with none of them is rejected by LeadSquared regardless of what else you send.

Two rules apply to every mapping on this connector.

• The lead ID from your source must be mapped. It is named after the platform the lead came from, for example Meta Lead ID or TikTok Lead ID, and it is the only field that has no substitute.
• Every field your CRM marks as required, shown with an asterisk in the mapping screen, must be mapped as well. An unmapped required field fails the record rather than the connection, so the setup will look healthy while leads quietly do not arrive.

Map as many further fields as you need. Anything you leave unmapped is simply not written.

Test connection and response preview

Click Test Connection before finishing. This sends a sample record into LeadSquared, so the test lead lands in your live CRM and someone will need to remove it afterwards. Once the test passes, click Finish.

Manage instance

To add another, open Manage Connections and click Add Instance, then work through the same steps. A CRM can hold several instances, so one connection per lead source is a reasonable pattern where the mapping differs between them.

To change one, click the connection name in Manage Connections, then the edit icon in the top right. Update the fields, click Test Connection and then Finish. Clicking Cancel keeps the previous configuration running; updates apply only after you finish.

Data & identifiers

Lead data is written into your own CRM, so nothing is hashed on the way. What arrives is what the lead form captured, in plain text, which means the CRM’s own access controls and retention rules are what govern it from that point on.

There is no fixed field specification for this destination. The fields available to map are whatever your lead form captured on one side and whatever your CRM schema exposes on the other, so the shape differs from one connection to the next.

Best practices

• Map more than one contact identifier where the form captures them. LeadSquared needs at least one, and a lead with only a name is hard to act on.
• Generate the keys against a service user rather than an individual, so the connection survives staff changes.
• Create the lead ID field in the Leads module before you begin.
• Map every field marked with an asterisk. Records missing one are rejected without the connection changing state.
• Remove the test record after Test Connection passes. It is a real lead in your live account.
• Rotate the keys periodically and update the connection afterwards.

Troubleshooting & FAQ

The keys are rejected. Check the secret key was copied in full after clicking Show Secret Key, and that the user the keys belong to has API access. Administrator profiles have it by default; others do not.

Leads are rejected with no obvious cause. LeadSquared requires at least one of First Name, Last Name, Email Address, Phone or Mobile. A record carrying none of them will not be accepted.

Leads are not arriving. Confirm the source is connected in the same project and receiving leads, and that the connection was finished rather than left open.

Some leads arrive and others do not. The ones failing are missing a value for a LeadSquared required field, or for all five contact fields.

A test lead is sitting in LeadSquared. That is the sample sent by Test Connection. Delete it manually.

Delivery stopped. The keys may have been rotated or the user deactivated. Generate fresh keys and update the connection.