Copper on your landing pages
Teams on Copper answer leads from Gmail. If the lead isn't in Copper yet, the sidebar is empty and the rep replies blind. Sending your LanderLab leads to Copper puts each one there as it's submitted, through Copper's own upsert: a returning prospect updates their existing lead, a new one creates it.
It suits teams that sell from Gmail and buy traffic to do it: coworking and commercial real estate brokers booking tours, agencies and consultancies running their own new-business ads, venues and service firms taking inquiries. LanderLab's webhook calls Copper's API directly, so there's no connector to pay for, and the lead carries its source, tags and campaign from the first second.
Copper leads, matched on email
Copper's developer API has an upsert for leads: it looks for a lead with a matching email and updates it, or creates the lead when there's none. Sending each submit that way means a prospect who fills your page twice stays one lead with the newest answers.
Copper only refuses when more than one lead already has that email, which tells you there's a duplicate to merge, not a lead to lose. Every lead is also kept in LanderLab's Leads tab.
In Gmail before the rep opens Copper
Copper lives in the Gmail sidebar. When the rep replies to the new lead, the record is right there: the team size they gave, the source, the campaign tag and the page they came from. The first reply can talk about their office or their event, not ask what they need.
Source, tags and campaign Copper can report on
Set every page lead to the Copper source you use for paid traffic, add tags like landing-page and the campaign name, and fill custom fields from hidden UTM fields and LL Variant ID. Copper's lead list and reports can then split new leads by source and campaign, and you see which ads bring tours that turn into leases, not just inquiries.
Keep Copper for inquiries worth a reply
If some inquiries aren't a fit (outside your city, under your minimum team size), put the rule in LanderLab Workflows (beta): a Filter or If node on that answer, then an HTTP Request node that makes the same call to Copper. The rest stay in LanderLab's Leads tab for another buyer or a later campaign, and the Runs view shows why each lead went where it did.
