Create leads in SharpSpring and assign them to active lists automatically -- with custom fields, phone, and lead source pre-populated from your ad forms.
Connect SharpSpring with 4 lead sources
SharpSpring (now Constant Contact Lead Gen & CRM) organises contact data around Leads, Opportunities, and lifecycle stages -- a Lead is the unqualified inquiry, an Opportunity is the deal, and lifecycle stage tracks where the contact sits in your funnel. LeadSync connects via your SharpSpring Account ID and Secret Key (semicolon-delimited) and posts each Facebook, Google, LinkedIn, or TikTok lead via the createLeads JSON-RPC method to the SharpSpring API.
Setup is two values from your SharpSpring account (Settings › SharpSpring API). Paste them into LeadSync and the integration enumerates your Active Lists via the getActiveLists RPC method so you can pick which list the lead lands on. Active Lists in SharpSpring are the equivalent of audiences -- they're what your nurture campaigns and email sends key off.
SharpSpring's API doesn't expose a single "create lead and add to list" endpoint -- you have to chain two RPC calls. LeadSync handles this transparently: first createLeads with the lead's firstName, lastName, emailAddress, mobilePhoneNumber, city, and any mapped custom fields, then addListMember with the new lead's ID and the chosen list ID. If the first call fails, the second is skipped and the failure is logged so you can investigate.
The lead's description field is auto-populated with the form name and submission timestamp ("New FB Lead via [Form Name] at [Created At]") so your sales team can see exactly which ad form the lead came from when they open the record in SharpSpring -- no need to manually annotate or rely on an opaque source ID.
SharpSpring's standard Lead schema includes firstName, lastName, emailAddress, mobilePhoneNumber, city, plus a description text field for context. LeadSync writes to all of these by default. For the full-name case, the integration calls Utils::parseFullName to split the lead's name into firstName + lastName so SharpSpring email merge tags like {{contact.firstName}} work correctly without manual cleanup.
Beyond the standard fields, SharpSpring custom fields you have defined at the account level appear in the field mapping screen automatically. Map any lead form question to a SharpSpring custom field once, and the value flows into the lead record on every submission -- usable in workflow triggers, email merge tags, and segmentation across your Active Lists.
Set up your SharpSpring integration in under 60 seconds. Free 14-day trial, no credit card required.
Start Your Free Trial