Log every video view to the HubSpot contact
Launch a personalized video campaign from Zidi and every recipient becomes a HubSpot contact, matched on their email address. As they watch, their engagement lands on that contact as five properties Zidi creates for you, plus a note that spells out how far they got and whether they clicked.
How to connect HubSpot
- 1
Open Integrations in Zidi
From your Zidi dashboard, open Integrations and find the HubSpot card under Sales & CRM.
- 2
Click Connect HubSpot
HubSpot asks you to pick the account to connect and to approve four permissions: sign-in, reading contacts, writing contacts, and creating contact properties.
- 3
Approve and come back
HubSpot returns you to Zidi with the connection live. There are no API keys to copy and no field mapping to configure.
Connecting is on the Pro plan; a workspace on another plan sees the upgrade prompt instead of the HubSpot consent screen. The five zidi_ properties are not created at this point — Zidi adds them to your contact schema on your first campaign launch, so a freshly connected portal will not show them yet.
What syncs, and when
| What happens in Zidi | What appears in HubSpot |
|---|---|
| Campaign launched | Each recipient is found by email address, or created if HubSpot does not have them yet. Zidi sets zidi_personalized_url and writes a note holding their personalized video link. |
| Recipient opens their video | zidi_video_opened is ticked and zidi_last_viewed_at is stamped, and an “opened the personalized video page” note is added to the contact. |
| Recipient finishes (95% or more) or clicks the CTA | zidi_watch_percent, zidi_cta_clicked and zidi_last_viewed_at are updated, and a second note records the milestones reached: 25%, 50%, 80%, Completed, CTA Clicked. |
| A directly shared video is watched by an identified viewer | One note is written the first time they cross 50%, then edited in place at 80% and 100% — a full watch leaves one note, not three. |
Two details worth knowing. Writes are queued rather than instant, and engagement is debounced for about a minute per recipient, so a viewer who opens, scrubs and clicks in quick succession produces one tidy update instead of a burst. And a campaign leaves at most two engagement records per person: the milestone chain you see listed in the completion note is text inside that note, not a separate write for every percentage. Anonymous viewers are counted in your Zidi analytics and never reach HubSpot.
The five properties Zidi creates
Zidi adds five custom contact properties to your portal, in the Contact information group, the first time a campaign pushes to HubSpot. They are ordinary contact properties: filterable, usable in lists and workflows, and visible on any contact under View all properties when you search for “zidi”.
zidi_personalized_urlZidi Personalized URLSingle-line text- The campaign link built for that one recipient. Written when the campaign launches.
zidi_video_openedZidi Video OpenedCheckbox- Ticked the first time the recipient opens their video page.
zidi_watch_percentZidi Watch PercentNumber- How far through the video they got, as a whole number.
zidi_cta_clickedZidi CTA ClickedCheckbox- Ticked when they click the call-to-action button on the video page.
zidi_last_viewed_atZidi Last Viewed AtDate and time- When Zidi last saw them watching.
If a property already exists in your portal, Zidi leaves it alone rather than replacing it, so re-running a campaign never resets your schema. Nothing else in HubSpot is touched: no deals, no companies, no tickets, no tasks.
Build lists and workflows on it
HubSpot lists and workflows can filter on any contact property, and these five are contact properties like any other. That is the whole point of writing engagement as properties rather than leaving it inside a video tool: your existing automation can read it without anyone exporting a report.
Follow up with the people who nearly finished. Build an active list where zidi_watch_percent is greater than or equal to 80 and zidi_cta_clicked is false. Those are the contacts who watched the whole thing and did not act — the warmest follow-up you have, and the one a rep would otherwise never see.
Give a rep a task the moment someone clicks. Enrol contacts in a workflow when zidi_cta_clicked becomes true, and have the workflow create a task for the contact owner. The note Zidi wrote alongside it tells the rep which video it was and how much of it the person watched before clicking.
What Zidi adds to HubSpot
A page per recipient, not one link for everybody. 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. That page is what the personalized URL on the contact points at, which is why the engagement Zidi reports can be attributed to a named person rather than to an anonymous play count.
Watch data with the shape of the watching in it. Inside Zidi you get more than the percentage that reaches HubSpot: unique viewers, total watch time, completion rate, a retention curve that shows where people dropped, a per-viewer heatmap of what they replayed, and click tracking on the call-to-action. Use HubSpot for the segment, come back to Zidi when you want to know why the segment behaved that way.
Recording that starts where you already are. The Zidi Chrome extension records your screen, a tab or your camera without leaving the browser, and the recording lands in the same library your campaigns draw from. Record a walkthrough in the morning, send it to a list in the afternoon, and read the results on the contact records the same day.
HubSpot integration questions
Which HubSpot and Zidi plans do I need?
On the Zidi side, integrations are a Pro feature, and the check is server-side: it runs when you start the connection, when HubSpot sends you back, and again every time Zidi writes. Downgrade and the syncing stops without the connection being deleted. On the HubSpot side you need an account you can install an app into and the right to create contact properties.
Does Zidi create contacts I have not met yet?
Only on a campaign launch, and only for people you put on the recipient list. If someone watches a directly shared video and HubSpot has never heard of their email address, Zidi skips the write rather than inventing a contact. That is deliberate: your CRM should fill up with people you chose to email, not with everyone who happened to open a link.
Does it write to deals, companies or tickets?
No. Zidi touches contacts and notes, and nothing else. Company and job-title values only ever land on the contact record itself, and only when your campaign supplied them as tokens.
Does anything come back from HubSpot into Zidi?
No. The connection runs in one direction, Zidi into HubSpot. 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 are written from your campaign list, so on a contact HubSpot already has, those three values are updated to match the list. Everything else Zidi writes is its own zidi_ properties and notes.
What happens with anonymous viewers?
They are counted in your Zidi analytics — views, watch time, retention — and produce no HubSpot activity at all. Zidi writes for identified viewers only: campaign recipients, and people who arrive through a tracked share link that carries their identity.
How do I disconnect?
In Zidi, open Integrations, choose HubSpot and click Disconnect. Zidi asks HubSpot to revoke the token, then deletes the stored credentials and the portal id and marks the connection inactive. You can also remove Zidi from Connected Apps inside HubSpot; the effect is the same. Properties and notes already written stay on your contacts.
Still stuck? Email support@zidi.ai or contact our team.
Other Zidi integrations
SalesforceRecipients are matched or created as Contacts; opens, completions and CTA clicks are logged as completed Tasks on the activity timeline.
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.