CRM
LeadSquared is the one CRM Attribi connects to where nobody can create the attribution fields programmatically, on any plan, because LeadSquared publishes no API for it. So the honest order of work is: you add sixteen custom fields to your Lead object once, Attribi checks them and names anything missing, and only then does data start moving. After that it runs unattended. Opportunities that reach a stage you count as won become closed-won conversions on every ad platform you have connected, carrying the amount and currency LeadSquared recorded, and campaign history travels back onto the Lead your sales team already opens.
No credit card required · 5-minute setup
An Opportunity that reaches a won stage becomes a closed-won conversion with its amount and currency attached. Stages that read as lost, rejected, cancelled or abandoned are never counted, and if your won stage carries a name that does not read as a win, you give us the exact names and those become the only ones that count.
List the Opportunity stage names your team treats as qualified and each one fires a qualified conversion. The match is exact and case sensitive, so Sales Qualified and sales qualified are two different things here. Leave the list empty and qualified reporting is simply off while won deals keep flowing.
Once the fields pass verification, Attribi fills the visitor id, the first touch source, campaign and time, the last touch source and campaign, and the touch count as leads convert. Until verification passes nothing is written at all, which is deliberate: a half-provisioned schema silently dropping values is worse than an obvious stop.
Two of the sixteen fields exist for your own landing page forms to fill with the ad click ID and the parameter it arrived on. Attribi never writes those two, it reads the pair back off the Lead when an Opportunity moves, which is what keeps click-level matching alive for a customer running no tracker.
LeadSquared runs on regional API hosts, so you paste yours along with an Access Key and Secret Key from your own account. There is no OAuth app for your IT team to review and no consent screen, and requests never leave the region your account lives in.
In LeadSquared open Settings, Customization, Lead Fields, and create the sixteen custom fields Attribi lists. They all use LeadSquared’s mx_ schema prefix. This is the same work on Basic as on Enterprise, because it is a limit of the platform and not of your plan. Do it before connecting and the verification step passes on the first try.
Paste your API host, such as api-in21.leadsquared.com, plus the Access Key and Secret Key from your LeadSquared account. Choose whether Attribi may create Leads that LeadSquared does not already hold, or should only enrich records you already own. Then click Provision fields. Attribi reads your live field schema and either confirms all sixteen or names the ones still missing.
Type your qualified Opportunity stage names in the connection panel, comma separated and spelled exactly as LeadSquared does. Won stages need nothing if yours are named conventionally. If they are not, send us the exact names during onboarding and they become the definitive list. There is no won-stage picker in the product yet, so this one step goes through us rather than a screen.
Stages Attribi supports for LeadSquared.
CRM
Freshsales ad attribution: won deals upload to your ad platforms in the deal’s own currency. Setup needs 16 custom fields you create by hand first.
CRM
Salesforce offline conversion tracking: won Opportunities upload to your ad platforms as revenue, matched on email and phone, using your own stage names.
Ad platform
Google Ads offline conversion tracking: send qualified leads and closed-won revenue from your CRM, so your account sees CRM-verified outcomes, not just form fills.
Because LeadSquared has no public API for creating custom fields, and that is true on Basic, Standard, Enterprise and Super CRM alike. It is a design decision of the platform rather than something you can upgrade past, and it is the reason this connection has the longest setup of any CRM Attribi supports. What Attribi does instead is verify: it reads your live Lead field schema, compares it against the sixteen it needs, and if any are missing it stops and lists them by name with the admin path. Nothing is written to LeadSquared until that check passes, so a partial setup fails loudly instead of quietly discarding half your attribution.
If you have given us your won stage names, those are the only stages that count, matched exactly. That is the setting to use when your pipeline ends somewhere like Booking Confirmed or Agreement Signed, and it is the same setting the Salesforce connection uses. If you have given us nothing, Attribi recognises the ordinary names, Closed Won, Won and Converted among them, and refuses anything that reads as lost, rejected, cancelled, disqualified or abandoned. A stage named only Closed is treated as not won, because on its own that word says nothing about the outcome. Two more things worth knowing: there is no won-stage picker in the product yet, so unusual names are configured with us at onboarding, and a won Opportunity with a blank or zero Amount is recorded but uploads no revenue conversion, because there is no figure to send.
Seven of the sixteen: the visitor id, first touch source, first touch campaign, first touch time, last touch source, last touch campaign, and the touchpoint count. Two more, the click ID and the click ID type, are meant to be filled by your own forms and read back by Attribi, which is how the pixel-less path works. The remaining seven, including the attribution path, the landing page, the referrer and the two touch mediums, are part of the canonical schema but are not written by Attribi today. Create all sixteen anyway, because verification checks for the full set and will not pass without them.
Only if you choose that when you connect. Full mode matches on email and creates the Lead when LeadSquared does not have one, then writes attribution onto it. Attribution only mode never creates anything: it looks the person up by email, updates the record if one exists, and does nothing at all if one does not. Either way the only fields Attribi writes are the mx_MTA_ ones you created for it, so your own data and your own automations are untouched.
Not for revenue. Qualified and closed-won outcomes are read out of LeadSquared on a schedule and uploaded to your ad platforms whether or not any script is installed, and a landing page form that captures the click ID keeps click-level matching too. What you give up without the script is the visit history: no page views and no multi-touch path, just the single touch Attribi can reconstruct from the Lead record. If you are running LeadSquared landing pages rather than your own, the click ID fields are the part worth setting up first.
Updated
Sign up and connect it from the Connections page.
Start FreeNo credit card · Free forever up to 1,000 visitors