Video engagement on the Salesforce activity timeline

Salesforce changed this in September 2025. An ordinary user can no longer authorise a connected app that nobody has installed in the org, and Zidi is a connected app. There is still no package to install and no metadata to deploy. What changed is who may click Allow the first time, and the permission that decides it is Approve Uninstalled Connected Apps.

The usual case: you are the one with the Zidi account. Connecting happens inside Zidi, on the Pro plan, and each person connects their own account — so the admin is usually not the one doing it. Ask them to give your Salesforce user Approve Uninstalled Connected Apps. A permission set is enough, and because this is a permission Salesforce means admins to hold, the point is to take it away again once Zidi is installed — after that nobody needs it. Connect from Zidi. Then ask them to open Setup, go to Connected Apps OAuth Usage, click Install in the Actions column beside Zidi, and Install again on the confirmation page. If your admin cannot see Zidi on that page yet, it is because nobody has been through the Salesforce authorisation screen for it. Do the connect above first, then have them look again.

If you are a Salesforce admin with your own Zidi account. You are normally not blocked, because the System Administrator standard profile already carries Approve Uninstalled Connected Apps. Connect from Zidi, then install the app for the org the same way. This is the shorter road, but only if you use Zidi yourself: an admin with no Zidi account has nothing to connect, which is why the path above exists. The one exception is an org running API Access Control, below.

After the install. Salesforce leaves an installed app on its default policy, All users may self-authorize, so your colleagues can then connect from their own Zidi accounts — each of them still on Zidi Pro. If your admin switches that policy to Admin approved users are pre-authorized, they have to pre-authorise those people through a profile or a permission set first.

Orgs with API Access Control are a separate case. That is an optional Salesforce feature, switched on through Salesforce Support, and it denies every app the org has not approved. Use Any API Client is the permission that clears it; Approve Uninstalled Connected Apps does not. You never reach a Salesforce error page here — you are sent straight back and Zidi reports the refusal on its own Integrations page, because Salesforce answers with error=OAUTH_APP_BLOCKED and the description this app is blocked by admin. The way through is for an admin to install Zidi and approve it for the users who need it, or to grant the person connecting Use Any API Client. Until one of those is done, an admin is turned away in such an org as well.

Two Task subjects carry campaign engagement. A recipient who opens their page and has not pressed play or clicked by the time Zidi syncs 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.

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.