Video engagement on the Salesforce activity timeline
Send a personalized video campaign from Zidi and every recipient is matched to a Salesforce Contact by email address, or created as one. When they watch, Zidi logs a completed Task against that Contact — so the rep sees the video in the same activity timeline as the calls and the emails, without opening another tool.
How to connect Salesforce
- 1
Open Integrations in Zidi
From your Zidi dashboard, open Integrations and pick the Salesforce card. Connecting is on the Pro plan.
- 2
Click Connect Salesforce
Zidi sends you to your Salesforce login and asks for two scopes: API access, and a refresh token so the connection survives without you signing in again.
- 3
Approve and come back
Salesforce returns you to Zidi, which stores the connection against your org's instance URL. There is nothing to install in Salesforce itself.
Zidi connects with OAuth from inside Zidi — nothing to install in Salesforce, no package, no admin deployment. Two limits are worth knowing before you start: the connection authorises against production orgs, so sandbox orgs are not supported, and you need a Salesforce user whose profile allows API access.
What syncs, and when
| What happens in Zidi | What appears in Salesforce |
|---|---|
| Campaign launched | Zidi looks the recipient up by email address and creates the Contact if the org does not have one. When your recipient row carries a company, Zidi finds or creates the matching Account and links the Contact to it. A completed Task records the personalized video link. |
| Recipient opens their video | A completed Task with the subject “Zidi: Video Page Opened” is added to the Contact. |
| Recipient finishes (95% or more) or clicks the CTA | A completed Task with the subject “Zidi: Video Engagement” records how far they watched and which milestones they passed — 25%, 50%, 80%, Completed, CTA Clicked. |
| A directly shared video is watched by an identified viewer | One Task is created the first time they cross 50% and then updated as they pass 80% and 100%. Its priority is raised to High from 80% onward. |
Every Task Zidi writes is created with the status Completed, because it is a record of something that already happened rather than work for a rep to do. Writes are queued rather than instant and engagement is debounced for about a minute per recipient, so a burst of activity produces one clean entry. Only identified viewers reach Salesforce at all: campaign recipients and people arriving on a tracked share link. Anonymous views stay in your Zidi analytics.
What a rep sees, and what Zidi never touches
Two Task subjects, and that is the whole vocabulary. A recipient opening their page produces Zidi: Video Page Opened. Finishing the video or clicking the call-to-action produces Zidi: Video Engagement, whose description carries the watch percentage and the milestones that were passed. A rep scanning the timeline can tell the two apart at a glance, and a report writer can filter on the subject without any custom setup.
Contacts, Accounts, Tasks — nothing else. Zidi finds a Contact by email address and creates one if the org has never seen that address. If the recipient row in your campaign carries a company name, Zidi finds or creates the Account with that name and links the Contact to it. Beyond that it writes no Leads, no Opportunities, no Events and no Campaign Members, so it cannot collide with the conversion process your team already runs or inflate anybody's pipeline numbers.
One entry per thing that happened. A Task with the same subject already created on that Contact today is updated rather than duplicated, and the Task written for a directly shared video is edited in place as the viewer passes 50%, 80% and 100%, with its priority raised to High from 80% onward. The result is an activity timeline you can still read after a week of campaigns.
What Zidi adds to Salesforce
A page per recipient. A Zidi campaign builds a personalized video page for each person on the list, with their name in the copy and your call-to-action under the player. Because each link belongs to one person, the watching that comes back is attributable: the Task on the Contact is about that Contact, not about an anonymous play on a shared URL.
The detail that does not fit in a Task. Salesforce gets the summary. Zidi keeps the rest: unique viewers, watch time, completion rate, the retention curve that shows where people dropped out, per-viewer heatmaps of what they replayed, and click tracking on the call-to-action. Use the timeline to spot who is worth a call, and Zidi to work out which thirty seconds of the video did the persuading.
Recording that fits between two calls. The Zidi Chrome extension records your screen, a tab or your camera in the browser, and the recording lands in the same library your campaigns draw from. Record a walkthrough after a discovery call, send it to the people who were not in the room, and read who watched it on their Contact records.
Salesforce integration questions
Which plan do I need?
Integrations are on the Zidi Pro plan. The check runs on the server, not just in the interface: once when you start the connection, again when Salesforce hands you back, and again every time Zidi is about to write. If a workspace drops off Pro the syncing stops and the connection stays in place, so upgrading again resumes it rather than making you reconnect.
Why does Zidi write no Leads?
Because Zidi matches people by email address, and the object that reliably carries an email address across every org is the Contact. Zidi finds or creates a Contact, adds the Account when your campaign supplies a company, and logs engagement against that Contact. It creates no Leads, no Opportunities and no Events, so it cannot interfere with whatever conversion process your team already runs.
Why is a sandbox org not supported?
Zidi's connect flow authorises against the production login host only, so sandbox orgs are not supported — a sandbox has nowhere to send you back from. Connect a production org. If you want to try the integration without touching live records, use a Zidi campaign with a single recipient you control — the writes are additive, and a Task on one Contact is easy to delete.
What does a rep actually see?
Completed Tasks on the Contact's activity timeline, in the same place the rep already looks for calls and emails. The subject says what happened, the description says which video it was and how far the person got, and the timestamp says when. Nothing is hidden behind a custom tab or a report the rep has to go and find.
Will this fill the timeline with duplicates?
No. Zidi looks for a Task with the same subject created on the Contact today and updates that one instead of adding another, so a person who opens their video five times in an afternoon leaves one entry. The direct-share Task is edited in place at 50%, 80% and 100% for the same reason.
Does anything come back from Salesforce into Zidi?
No. Everything moves one direction, Zidi into Salesforce. Zidi looks a Contact up by email address to match a recipient and never imports or browses your lists. One thing to know: when a campaign launches, the recipient's first name, last name and company (as Department) are written from your campaign list, so on a Contact your org already has, those values are updated to match the list. Beyond that Zidi writes only its own Tasks. Disconnect from Integrations in Zidi and the stored tokens are deleted; the Tasks already written stay where they are.
Still stuck? Email support@zidi.ai or contact our team.
Other Zidi integrations
HubSpotCampaign recipients become HubSpot contacts matched by email, and video engagement lands on the contact as five custom properties Zidi creates plus a note.
CopperPaste a Copper API key and the login email that made it. Recipients become People and engagement is logged as Activities on the contact.
ZapierZidi is a public app in the Zapier App Directory, with five triggers: video viewed, video uploaded, CTA clicked, campaign launched and watch threshold.
See every Zidi integration — CRMs, Zapier, Make, Slack, tracking pixels and embed guides.