Zidi + Copper
Put video engagement on the Copper timeline. Campaign recipients become People automatically, and Zidi logs an activity when the recipient opens the video but has not started it when Zidi syncs, and a completed activity when they finish or click the CTA — milestones are listed in that completed activity. With Copper activities and automations turned on, Zidi records opened, 50%, 80%, completed and CTA clicked as separate activities instead. Connecting takes one sign-in with Copper.
Connect in three steps
Open the Copper card
In Zidi, go to Integrations → Copper CRM and click Connect with Copper. (Pro plan required.)
Authorize Zidi in Copper
Sign in to Copper and authorize Zidi. Copper sends you back, and the card shows the connection signed in via Copper. An API key still works as a fallback, but API-key connections are being retired.
Done
Launch a campaign or share a tracked link — People and activities appear in Copper as viewers engage. Nothing to map.
Step-by-step instructions are in the Copper setup guide in the Zidi docs.
What lands in Copper
| When | In Copper |
|---|---|
| Campaign launched | Each recipient is matched by work email or created as a Person; an activity records the campaign name and the recipient's personalized video link |
| Recipient opens their video page | If they have not started the video or clicked the CTA by the time Zidi syncs, about a minute after their last activity, an activity records that they opened the page. A recipient who presses play straight away gets no opened activity; with activities and automations turned on, one is logged either way |
| Watch milestones (50 / 80 / 100%) | On a directly shared video one activity, “Watched ‘<video>’ — 50% viewed (1m 12s)”, is written at halfway and edited in place at 80% and at the end — one entry per viewer per day, never a pile of duplicates. With activities and automations turned on, 50%, 80% and the end are logged as separate activities instead |
| CTA clicked / video finished | A completed activity is written for the campaign recipient, and the milestones they passed — 25%, 50%, 80%, Completed, CTA Clicked — are listed inside it rather than logged one by one, unless activities and automations are turned on |
| Tracked share viewed | Identified viewers get that shared-video activity; the Person is created if Copper does not know the email yet |
Everything is written through Copper's own API with the key you provide — no browser extension, no shared login, and the key is stored encrypted. Zidi only creates People for identified viewers, so your Copper account never fills with anonymous traffic.
Troubleshooting
“Invalid API key or email”?
The email must belong to the Copper user who generated the API key — Copper checks the pair together. Generate the key under Settings → Integrations → API Keys and enter that user's login email in Zidi.
No activity is showing up?
Activities are written for identified viewers only: campaign recipients and tracked-share viewers. Anonymous visits to a public share page are not sent to Copper. Also check that the campaign was launched after connecting.
Worried about Copper's API limits?
Zidi paces campaign pushes to stay within Copper's per-user rate limit, so a large recipient list syncs a little slower rather than failing.
Why does one viewing leave only one activity?
On the tracked-share path Zidi writes a single activity when the viewer passes half the recording, then rewrites that same activity as they reach eighty per cent and the end. Somebody who watches a long walkthrough across three sittings within a day therefore leaves one entry saying how far they finally got, rather than three that each tell you part of the story. With activities and automations turned on, half, eighty per cent and the end are logged as separate activities instead.
How do I disconnect?
In Zidi, open Integrations → Copper → Disconnect. Zidi discards its stored access immediately. If you connected by signing in with Copper, also remove Zidi in Copper under Settings → Integrations → Active Integrations; if you connected with an API key, revoke that key in Copper's API Keys settings.
Still stuck? Email support@zidi.ai or use the contact form.
Other Zidi integrations
HubSpotCampaign recipients become HubSpot contacts matched by email, and engagement lands on the contact as five custom properties Zidi creates plus up to two notes.
SalesforceRecipients are matched or created as Contacts; video engagement is logged as completed Tasks on the activity timeline.
ZohoConnect any of Zoho CRM's data-centre regions with OAuth. Recipients sync as Contacts and engagement is written as Notes on the contact.
ActiveCampaignConnect with your API URL and key. Recipients sync as Contacts with Notes, and Zidi applies engagement tags such as Watched Video and High Engagement.
CloseConnect Close with OAuth. Recipients are matched by email and video engagement is written as note Activities on the record.
FreshsalesConnect with your Freshsales bundle alias and API key. Recipients sync as Contacts and engagement is written as Notes on the contact.
Monday.comPick a board, paste an API key, and each recipient becomes a board item whose updates record how far they watched and whether they clicked.
ZapierZidi is a public app in the Zapier App Directory, with five triggers: video viewed, video uploaded, CTA clicked, campaign launched and watch threshold.
MakePaste a Make.com webhook URL and Zidi posts the same five events to it, each carrying an idempotency key your scenario can use to ignore retries.
SlackPost to one Slack channel when a video is viewed, a CTA is clicked, a campaign launches or a viewer crosses 50, 80 or 100 percent.
See every Zidi integration — CRMs, Zapier, Make, Slack, tracking pixels and embed guides.