Connecting Glimpze to Salesforce

Every completed call and every finished chat becomes an activity on the right person in your Salesforce org — carrying the summary, the transcript, the visitor's form answers, and a link back to the full record in Glimpze.

Glimpze writes to standard Salesforce objects only. There is no managed package to install, no namespace, and no AppExchange listing involved.

Three kinds of record, and nothing else.

• A Contact for each visitor who gives an email address — name and email only. If a Contact with that email already exists, Glimpze leaves it alone rather than claiming it.
• A Task for each completed call, logged the way Salesforce logs a call (TaskSubtype = Call), with duration, direction and outcome in Salesforce's own fields — so reports and list views built on them keep working.
• A Task for each finished chat, carrying the full transcript and the answers the visitor typed into your widget forms.

Chats are recorded as Tasks because a Task is the one activity type every Salesforce org has, and it puts the conversation on the Contact's Activity timeline where your team is already looking. The alternative — a custom object — would mean installing a package in your org.

• Subject — Glimpze Call • Jane Doe or Glimpze Chat • Jane Doe. If a visitor returns and carries on, the continuation is a second record ending (part 2).
• Description — a link back to Glimpze, the visitor's form answers, the AI summary and key points, the call details, and the transcript.
• Related To — the Contact, so the record appears on their Activity timeline.
• Date — when the call or conversation happened, not when it synced.
• Status — always Completed. These are records of things that already happened, never to-dos assigned to your team.

Long conversations are trimmed to fit Salesforce's 32,000-character limit on the Description field. Glimpze keeps the opening and the ending — where the outcome usually is — and marks the gap with a link to the full record.

• After a call ends — about ten minutes later, once any recording has finished processing.
• After a chat goes quiet — about thirty minutes after the last message, so nothing is written mid-conversation.
• If the visitor returns — a second record, marked as a continuation of the first.

Records are delivered in batches every few minutes, so a short delay is normal and expected.

• No Leads, Opportunities or Accounts. Contacts and activities only.
• No record for an anonymous visitor. Without an email there is nobody to attach the activity to, so it is skipped rather than guessed at. On most sites this is the majority of conversations.
• No claiming of existing Contacts. A visitor can type any address into a chat window. If your duplicate rules say a Contact already exists for it, Glimpze skips the write rather than attaching a stranger's conversation to one of your people. If you would rather match existing records, ask us and we can change it for your account.
• No edits to anything Glimpze did not create. Existing fields on your Contacts are never overwritten, and a name is only filled in where the field is empty.
• No deletion. Records written to Salesforce stay there. Deleting a visitor in Glimpze does not remove activities that have already been delivered.

Glimpze connects through an app you create in your own Salesforce org, so your data never depends on an app owned by us. A Salesforce administrator does this once, in about five minutes.

1. In Salesforce: Setup → External Client App Manager → New External Client App.
2. Leave Distribution State as Local — the app lives in your org and needs no package.
3. Under API (Enable OAuth Settings), tick Enable OAuth.
4. Paste the callback URL shown in Glimpze, exactly as given, with no trailing slash.
5. Select only two scopes: api and refresh_token.
6. Under Flow Enablement, tick Enable Authorization Code and Credentials Flow. Leave the other four unchecked, and leave its sub-option “Require user credentials in the POST body” unchecked as well — you sign in on Salesforce's own page, and Glimpze never sees your password.
7. Under Security, require a secret for the Web Server Flow and require PKCE.
8. Save, then open Settings → OAuth Settings → Consumer Key and Secret.

A newly created app takes up to ten minutes to activate. Connecting before then fails as though the key were wrong — wait, then try again.

In Glimpze, open Integrations → Salesforce, paste the Consumer Key and Secret, press Save, then press Connect. The person who connects must be a Salesforce administrator: Salesforce blocks everyone else from approving an app.

• Sync to Salesforce — the master switch. While it is off, nothing is written, even though the connection is live.
• Sync chat conversations — choose calls only, or calls and chats. Needs the master switch to be on.
• Field mappings — send answers from your Glimpze forms into Salesforce contact fields, for example a “Company” question into the Contact's Department field.
• Disconnect — revokes access immediately and deletes the stored credentials. Records already in Salesforce are untouched.

• On a person — open the Contact, then the Activity tab. Glimpze records appear under Past Activity.
• All of them — App Launcher → Tasks, then switch the list view to All Activities.

The default Tasks view is My Tasks, and Glimpze's records are unassigned — so that view looks empty even when the sync is working perfectly. Switch the list view before concluding nothing arrived.

The Salesforce panel in Glimpze shows what synced, what is queued, and what was deliberately skipped, broken down by reason.

Skipped records are not errors. The two common reasons are a visitor who never gave an email address, and a Contact your duplicate rules say already exists. Both are the integration behaving as designed.