Copper CRM integration

Copper CRM lead source, captured automatically.

Copper has a Source field on every lead. It only holds what someone picks from the list. Capture the real source, landing page, and full page journey instead, and let Zapier write it straight into Copper.

Connects via the Copper Zapier connector Writes Copper’s standard Source field One line of code
What Copper captures, and what it misses

Copper has a Source field. It holds one word.

Copper lives inside Gmail and Google Workspace, so most leads land in the CRM the moment a sales rep replies. That is the strength and the gap. The Source field on a Copper lead is a single value picked from a list. It tells you the bucket. It does not tell you the campaign, the page they arrived on, or the pages they read before they got in touch.

What Copper’s Source field holds

A channel, picked from a list

  • A single value: Referral, Web, Inbound, Other
  • Set by whoever creates the lead, often after the fact
  • Useful for a pipeline view, useless for a budget decision
What it leaves out

The part that tells you what worked

  • The campaign behind the click, in plain language
  • The landing page they arrived on
  • The pages they read before they reached out, ending on the page that converted them

Short version: Lead Source records the source, landing page and journey when the form is submitted, then hands the lead to Zapier so Copper’s own Source field carries something real.

How the connection works

Captured on your site. Written into Copper through Zapier.

Copper has a live Zapier connector, and it is the cleanest of the CRMs we connect this way. Its Create or Update Lead action exposes Copper’s standard Source and Tags fields directly, so the real source lands in the field your team already reads.

  1. 01
    Lead Source captures the visitor’s real source, campaign, landing page and full page journey from the moment they arrive. UTMs, referrer, click IDs, the whole session.
  2. 02
    When the visitor submits your form, Lead Source records the lead in your own dashboard and sends it to Zapier.
  3. 03
    Your Zap runs Copper’s Create or Update Lead action. You map the captured source into Copper’s standard Source field, add the campaign and landing page as Tags or notes, and Copper has a lead with the real story attached.
  4. 04
    Because the write happens at submission, the value is set before a rep ever opens the record. No one has to remember to pick a source from the list.
The captured record

What your sales team sees in Copper.

Sample data, not a real customer. This is the shape of the record that arrives when a form is submitted and the Zap fires.

SAMPLE · captured lead → Copper at submission
Copper lead created
Lena Brandt
Founder · Aster Studio
SourceLinkedIn
campaignBrand & web design
landed/services/branding
journey/services/branding → /work → /contact
Tagslinkedin · branding · inbound
Source field filled. Campaign and journey on the record.
Safe setup pattern

Live in three steps.

No invented menus, no custom-field gymnastics. Just the verified Copper Zapier action and the standard fields it exposes.

01

Drop the snippet on your site

Put the Lead Source script before the closing </head> on any page that carries a form. It starts recording the source, landing page and journey for every visitor.

02

Connect Lead Source to Copper in Zapier

Create a Zap with Lead Source as the trigger (new captured lead) and Copper’s Create or Update Lead action as the step. Authorise Copper once.

03

Map source into the Source field

Map the captured source to Copper’s standard Source field, and the campaign and landing page to Tags or a note. Send a test submission with a UTM and watch the lead land in Copper with the real source attached.

Integration details verified against Copper’s Zapier connector on 30 June 2026. We confirmed the Create or Update Lead action exists and exposes the standard Source and Tags fields. We did not test writes to arbitrary custom fields on Copper records.

When this isn’t the right fit

When Copper isn’t the right home for this.

A few situations where this setup is the wrong call, said plainly.

  • You need the source written to a bespoke custom field on Copper rather than the standard Source field. That custom-field write is not something we have verified, so we will not promise it.
  • Most of your leads come in by phone or in person rather than a web form. Lead Source captures web form submissions, so phone-first pipelines see less of the benefit.
  • You want the source to overwrite values your reps have already entered by hand. We write at submission for new leads and leave existing records alone.
Common questions

Questions, answered.

Does Copper already have a lead source field?

Yes. Copper has a standard Source field on every lead, plus Tags. It holds a single value someone picks, so it tells you the channel and stops there. Lead Source fills that Source field through Zapier with the real source captured at form submission, and adds the campaign and landing page as Tags or a note.

Can you write the source into Copper's standard Source field?

Yes. Copper's Create or Update Lead action in Zapier exposes the standard Source and Tags fields directly, so the real source lands where your team already looks. We have not verified writes to bespoke custom fields, so we only promise the standard Source and Tags.

Do I need a paid Zapier plan to connect Copper?

Copper's connector is a standard Zapier app, so a free Zapier plan can run a basic Zap. If your lead volume is high, Zapier's own task limits may push you to a paid tier, but that is a Zapier choice, not a Copper one.

See your real Copper lead sources.

Free to start. Connect Copper through Zapier in minutes.

Track your Copper leads free &rarr;

Free to start &middot; no card