Salesforce

Connect Salesforce so campaign recipients become Salesforce Contacts and their viewing shows up as completed Tasks.

Available on: Pro

Before you start

• A Salesforce edition with API access. Professional Edition needs Salesforce's paid API add-on (Salesforce Help).
• A production org. Sandbox orgs cannot connect, because Zidi signs in through the production Salesforce login only.
• A Zidi account on the Pro plan. A paid seat on a Pro team also counts.

Who can connect

Any Zidi user on Pro can connect Salesforce from their own account. Each connection belongs to one Zidi user, so each teammate connects separately.

Since September 2025, Salesforce stops most users from approving an app that is not yet installed in the org. The user needs the Approve Uninstalled Connected Apps permission. The System Administrator profile has it, and an admin can grant it to anyone.

1. A Salesforce admin, or a user with that permission, connects Zidi first.
2. The admin then opens Setup → Connected Apps OAuth Usage in Salesforce and clicks Install next to Zidi.
3. After that, other people in the org can usually connect.

If your org uses API Access Control, the admin must also approve Zidi for each user.

Connect Salesforce

1. In the sidebar, click Integrations.
2. Click the Salesforce card. If you are not a Salesforce admin, read the note under Not a Salesforce admin? on that page.
3. Click Connect Salesforce. Salesforce opens.
4. Sign in and allow access.
5. Salesforce sends you back to the Integrations page with the message "Salesforce connected successfully!".

Finish within 10 minutes and in the same browser. Open the Salesforce card to see your Instance and a Synced records count. Zidi renews its access automatically.

What syncs

• At campaign launch: Zidi finds each recipient's Contact by email, or creates one. It writes first and last name. On an existing Contact, the company from your list goes into Department. A new Contact is linked to an Account with the company's name, which Zidi finds or creates. If Zidi cannot find or create the Account, the company goes into Department instead. Zidi logs a completed Task "Zidi Campaign: campaign name" with the personal link in its description.
• While a recipient watches: at most two completed Tasks, "Zidi: Video Page Opened" and "Zidi: Video Engagement". A Task with the same subject on the same day is updated, not duplicated. There is no separate Task at 50% or 80%.
• Tracked share links: one Task per view, "Video Watched: title (n%)", created at 50% and updated at 80% and 100%. Priority is High from 80%. Viewers who are not already Contacts are skipped.

Zidi works with Contacts only. It never reads or writes Leads or Opportunities. How CRM sync works explains the timing.

The Zidi custom fields stay empty

When it pushes a campaign, Zidi tries to create five custom fields on the Contact object, such as Zidi_Watch_Percent__c and Zidi_Personalized_URL__c. If your user cannot create fields, they are simply not created. Either way, Zidi does not write values into them. The personal link and all engagement are in the Tasks. Do not build reports or flows on these fields.

Where to find it in Salesforce

Open a Contact and look at its activity history. If Tasks do not show, check that the Contact page layout includes activities.

Disconnect

1. In the sidebar, click Integrations, then the Salesforce card.
2. Click Disconnect Salesforce.

There is no confirmation step. Zidi disconnects at once and shows "Salesforce disconnected". Zidi also asks Salesforce to cancel its access and deletes its stored tokens. Contacts, Accounts, Tasks and the empty Zidi fields stay in Salesforce.

Troubleshooting

• A dialog says "Connecting Salesforce to Zidi is a Pro feature." Your plan is Free or Starter. Click Upgrade Plan, then connect again.
• "Salesforce blocked this connection because your org limits which apps can use its API. Ask your Salesforce admin to install Zidi under Setup → Connected Apps OAuth Usage and approve it for your user, then try again." Zidi is not installed in your org yet, or your org uses API Access Control. Ask your admin to follow Who can connect.
• "You cancelled the Salesforce connection. Nothing was changed." You declined on the Salesforce screen. Start again from the card.
• "CRM integrations need the Pro plan." Zidi checks your plan again when Salesforce sends you back, and you were not on Pro. Upgrade, then connect again.
• "That sign-in link expired or was opened in a different browser session. Please start the connection again." You came back signed in to a different Zidi account, or the return link was incomplete. Sign in to the right Zidi account and start again.
• "Could not connect Salesforce. Please try again." The sign-in took longer than 10 minutes, finished in another browser, or used a sandbox org or an edition without API access. Start again from the card and finish within 10 minutes in the same browser.
• "This integration is not available right now. Please contact support." Contact support.
• "Salesforce missing custom field 'Zidi_Personalized_URL__c'. Please disconnect and reconnect Salesforce, or create the field manually in Setup > Object Manager > Contact > Fields." The message names a Zidi field, but Zidi does not write that field. It means Salesforce refused one of the standard Contact fields Zidi writes: First Name, Last Name, Email, Department or Account. Ask your Salesforce admin to give your user edit access to those fields. Then open the campaign and click the CRM button (Synced to CRM or Sync Failed - Retry) to push again.
• The card shows Available again. Salesforce withdrew Zidi's access. Syncing has stopped. Connect again.
• A viewer is missing from Salesforce. Engagement and tracked-share Tasks only go to existing Contacts. Check that the email matches. Only campaign launch creates Contacts.