Tag contacts by how much of the video they watched
Zidi writes video engagement into ActiveCampaign as tags, which is the one thing automations can act on without any setup. A recipient who opens your video is tagged Watched Video; one who finishes it or presses the call-to-action is tagged High Engagement; everyone the campaign reaches carries Zidi Campaign from the moment it launches.
That turns a question people usually answer with spreadsheets and custom tracking code into a trigger you can build an automation on this afternoon.
How to connect ActiveCampaign
- 1
Copy your API URL and key from ActiveCampaign
In ActiveCampaign, open Settings and then Developer. The page shows an API URL that looks like https://youraccount.api-us1.com and a long API key beneath it. Copy both.
- 2
Paste them into the Zidi card
Open Integrations in Zidi, choose ActiveCampaign and paste the pair. There is no OAuth round trip and nothing to approve, so the connection is live as soon as the values are saved.
- 3
Launch a campaign and watch the tags arrive
The next launch creates or updates the contacts and applies the campaign tag. The engagement tags follow as people watch.
Zidi accepts the two hosts ActiveCampaign issues — the numbered developer host in the form youraccount.api-us1.com, and the hosted form youraccount.activehosted.com — and refuses anything else, so a mistyped domain is rejected at the point you save it rather than failing quietly later. The integration is on the Zidi Pro plan and the key is stored encrypted.
What syncs, and when
| What happens in Zidi | What appears in ActiveCampaign |
|---|---|
| Campaign launched | Each recipient is found by email address or created as a contact, carrying their first name, last name and phone number when your list holds one. A note records the personalized video link and the contact is tagged Zidi Campaign. |
| Recipient opens their video page | A note is added whose first line reads “Zidi Video Engagement” with your campaign name, recording that they opened the page, and the contact is tagged Watched Video. |
| Recipient finishes the video or clicks the call-to-action | A second note, opening with that same line, records how far they got and which milestones they passed, and the contact is tagged High Engagement. |
| Someone opens a directly shared video | ActiveCampaign is the only integration that will create a contact from a directly shared video rather than only from a campaign. One note is written when the viewer passes halfway and rewritten as they pass eighty per cent and finish. The contact is tagged Watched Video, and the tag is raised to High Engagement once they pass eighty per cent. |
ActiveCampaign notes have no subject field, so both notes are bodies beginning “Zidi Video Engagement”; the tags are what you filter and automate on, and the notes are the detail underneath. Tags are found or created by name, so the three Zidi tags appear in your tag list the first time each is needed and are reused after that. A contact keeps a tag once applied; Zidi never removes them, because the record of what someone did should not disappear when they do something else. Campaign engagement is held for about a minute per recipient before it is written, so scrubbing through a video produces one tag change rather than a dozen. Shared-link views are deduplicated per view and milestone instead of being held.
Why tags rather than custom fields
A tag is the thing ActiveCampaign automations were designed to start from. Dropping a percentage into a custom field means every automation you write has to compare numbers, and every teammate who builds one has to know which field to look at and what counts as a good score. A tag turns that into a single condition anybody can pick from a list: when the contact is tagged High Engagement, send the follow-up, notify the owner, add them to the deal pipeline. It also survives the messy reality of video, where somebody watches most of a demo on Monday and finishes it on Thursday, because the tag is applied the first time the threshold is crossed rather than being a value that keeps moving.
The notes are still there when you need the detail. Each one spells out the exact percentage and whether the button was pressed, so the automation stays simple and the rep still gets the specifics before they pick up the phone.
Three automations worth building first
Start with the follow-up nobody sends. An automation that waits for the High Engagement tag and then notifies the contact owner turns a watched video into a conversation on the same day, which is the entire point of sending video in the first place. Second, use Watched Video as a gentle nudge: a contact who opened the page but never came back is a different problem from one who never opened it, and deserves different copy rather than the same reminder. Third, put Zidi Campaign to work as a suppression rule so that people who are already in a video sequence are not swept into an unrelated broadcast the same week.
None of these need code or a tracking script on your site. The events come from Zidi's own player rather than from a pixel you have to install, so the data starts the moment the campaign launches and does not depend on where the video is embedded.
ActiveCampaign integration questions
Which tags does Zidi apply, exactly?
Three, and no others. Zidi Campaign is applied when a campaign launches and marks everyone it reached. Watched Video is applied the first time a recipient opens their page. High Engagement is applied when they finish the video or press the call-to-action on the campaign path, and once they pass eighty per cent on a shared link. They are created in your account the first time each is needed and reused after that, so your tag list gains three entries in total rather than one per campaign.
Do I need OAuth or an app from the marketplace?
No. The connection is an API URL and an API key copied from Settings and then Developer inside ActiveCampaign, which means there is nothing to approve and no listing to install. Zidi validates the host before saving, accepting the numbered developer domain and the hosted domain and rejecting anything else, so a typo fails immediately rather than halfway through your first campaign.
Will a contact ever lose a tag?
Not from Zidi. Tags record something that happened, so removing them would erase history that an automation may already have acted on. If you want a contact to move between states, build that in ActiveCampaign with your own tags and let the Zidi ones stay as the audit trail of what the person actually did.
What about people who watch a shared link rather than a campaign?
ActiveCampaign is the one integration where a directly shared video can create a contact, so long as Zidi can identify the viewer. A note is written when they pass halfway and rewritten as they get further, and the same tags are applied — Watched Video first, raised to High Engagement at eighty per cent rather than at the ninety-five the campaign path uses. Anonymous viewers are counted in Zidi analytics only, because there is no email address to hang a contact on.
Which plan do I need on the Zidi side?
Pro. The check runs on the server when the key is saved, and again before every write, so a workspace that leaves Pro stops syncing without losing its stored connection. Returning to Pro resumes the writes with no reconnection step.
Does the phone number really sync?
Only when your campaign list carries one. Zidi sends the first name, last name and phone it was given for that recipient, and leaves the fields alone when the list is silent about them. On a contact ActiveCampaign already has, those values are refreshed from the list at launch so the personalization in the video matches the record.
Still stuck? Email support@zidi.ai or contact our team.
Other Zidi integrations
Paste a Copper API key and the login email that made it. Recipients become People and engagement is logged as Activities on the contact.
Campaign recipients become HubSpot contacts matched by email, and video engagement lands on the contact as five custom properties Zidi creates plus a note.
Recipients are matched or created as Contacts; opens, completions and CTA clicks are logged as completed Tasks on the activity timeline.
Connect any of Zoho CRM's data-centre regions with OAuth. Recipients sync as Contacts and engagement is written as Notes on the contact.
Connect Close with OAuth. Recipients are matched by email and video engagement is written as note Activities on the record.
Connect with your Freshsales bundle alias and API key. Recipients sync as Contacts and engagement is written as Notes on the contact.
Pick a board, paste an API key, and each recipient becomes a board item whose updates record how far they watched and whether they clicked.
Zidi is a public app in the Zapier App Directory, with five triggers: video viewed, video uploaded, CTA clicked, campaign launched and watch threshold.
Paste 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.
Post 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.