Platform · CRM sync

Salesforce

Leads become Salesforce Leads, meetings become an Event and a Task, campaigns can be filled automatically, and lead status, opportunities, notes and history are read back. This page follows the Salesforce card under CRM Sync from top to bottom, with the setup guide the app shows.

Step 1 · Connect

Open Integrations
Settings → Workspace → Integrations, Salesforce tile, Connect Salesforce.
Sign in to Salesforce
Production login only: Meeton connects to login.salesforce.com, so a sandbox org cannot be connected. Sign in as the user Meeton should act as: everything is created and read as that user, so give it access to Leads, Contacts, Campaigns and Opportunities.
Back in Meeton
The tile reads Connected · set-up needed until you finish the CRM Sync page.

Step 2 · Initial setup: the external ID field

Meeton stores its contact ID in a custom field on the Lead. Set Up Custom Properties creates it in one click. If the connected user lacks Modify All Data or Modify Metadata, the app says so; ask a Salesforce admin for one of those, or create the field by hand:

Salesforce setup guide (manual)

In Salesforce, go to Setup → Object Manager → Lead → Fields & Relationships and click New.
Select Text as the data type and click Next.
For the Field Label, enter a name like DynaMeet Contact ID.
For the Length, enter 255.
Important: you can check the External ID box (this makes the field searchable), but do not check the Unique box.
Click Next, set your field-level security (defaults are fine), and click Next.
Click Save.
After saving, find the Field Name (it will look like DynaMeet_Contact_ID__c) and paste it into the External ID Field box in Meeton.

A field name that does not exist is refused with The specified ID field does not exist. Contact Sync and Activity Sync stay greyed out until the field is set.

Step 3 · Contact sync

Push leads

Sync new contacts to Salesforce as Leads when a visitor submits a form. Matched by email; a Task with the form details is added on the first sync. If the person already exists as a Contact and has no Lead, that Contact is updated instead of creating a duplicate Lead.

Add leads to campaign

Automatically enrol synced leads into a Salesforce campaign. The picker shows your most recent active campaigns; type to search all of them, inactive ones included. Greyed campaigns are ones the connected user can see but cannot add members to. Enrolment needs the Marketing User permission on the connected user; without it the card explains, keeps your choice, and resumes once an admin enables it.

Lead status

The initial status for new leads, or Use Salesforce default. A saved status that no longer exists in Salesforce is flagged.

Lead record type

Shown when your org uses record types on Leads. A record type can only be used if it is active and enabled for the connected user's profile; if the org requires one and the user has no default, the card reads Action needed until you pick it.

Merge strategy · language · attribution

As on the overview: fill empty only or overwrite, Japanese or English, and UTM and click-ID fields on the Lead.

Step 4 · Activity sync

Setting	Direction	What it does	Default
Meeting sync	To Salesforce	Creates a Salesforce Event and a Task when a meeting is booked via Meeton.	On
Meeton Email activity	To Salesforce	Creates Tasks for AI email events: Sent, Opened and Clicked (with the link URL). Plan-dependent.	Off
Import notes & meetings	From Salesforce	Pulls the lead's notes and meetings into Meeton as read-only history.	Off
Import emails	From Salesforce	Pulls the lead's email history into Meeton as read-only. No extra consent step, unlike HubSpot.	Off
Import deal amounts	From Salesforce	Reads opportunity amounts to calculate Pipeline influenced on the ROI dashboard, with a default currency for opportunities that carry none.	On

What is read back

Lead status. Disqualified, Closed - Not Converted, Unqualified and Junk mark the contact as disqualified in Meeton: follow-up email stops and lead notifications no longer fire.
Conversion and opportunities. Whether the lead was converted and the opportunity amounts, for the ROI dashboard. Meeton never creates opportunities.
Each synced lead is re-polled at most once an hour.

Pardot forms

Salesforce Pardot (Account Engagement) forms on your site are captured by the tag rather than by CRM sync. Under Settings → Setup → Installation the Salesforce Pardot setup card explains the two ways: a form handler whose form has the id pardot-form, which the tag detects on submit, or an iframe form that posts a thank-you code. Captured leads then follow the normal sync.

Test it

Send test lead fires a simulated visitor event with your current settings to the email address you type: the Lead appears in Salesforce with its Task, lands in the campaign if one is chosen, and takes the status and record type you set. A refusal names the Salesforce error, which is usually a permission.

Troubleshooting

Symptom	Likely cause	What to do
Cannot connect a sandbox	Only production login is supported	Connect a production org. Test with Send test lead and a test email address instead.
Some fields failed to create	The connected user lacks Modify All Data or Modify Metadata	Grant one, or create the field manually and paste its API name.
Leads can't be added to any campaign yet	The connected user is not a Marketing User	Have a Salesforce admin enable Marketing User on that user, then send a test lead again.
Action needed — leads can't be created yet	The org requires a record type and the user has no default	Pick the record type on the card.
Leads are created but the saved status is flagged	The status was removed from the Lead Status picklist	Select a current value or Use Salesforce default.
Someone appears as a Contact, not a Lead	They already existed as a Contact	Expected: Meeton updates the Contact rather than making a duplicate Lead.
Everything is Pending	The refresh token was revoked, or the user's password changed	Integrations → Needs reconnection; reconnect.

Frequently asked questions

Leads or Contacts?

Leads. A new person becomes a Lead; a person who already exists as a Contact is updated as a Contact. Lead conversion is read back, not performed by Meeton.

Which Salesforce edition do we need?

One with API access enabled for connected apps. Meeton asks for the standard api, refresh_token and offline_access scopes, and signs in through the production login.

Can we map our own Lead fields?

Yes: under Lead form → Import from Salesforce pick Lead fields to import as custom fields; they stay linked and write back to those fields.

Can the chat agent use Salesforce Knowledge?

Yes, once Salesforce is connected: Salesforce Knowledge appears under Chat → Knowledge → More sources. It is a knowledge source, separate from lead sync.