Salesforce

RubySig connects to your Salesforce org in two directions:

1. Salesforce → signatures. Each person's Title, Phone (or Mobile) and Department from their Salesforce user record go into their signature, ahead of what the mail directory says. Sales teams keep those fields current in the CRM long after the directory has gone stale.
2. Signatures → Salesforce. With Marketing Core Analytics, every signature banner that links somewhere becomes a Campaign in Salesforce carrying its click total to date, so the marketing team sees signature campaigns where they see every other campaign.

Both use one connection that a company admin approves once.

Note: RubySig keeps only a refresh token for the connection, encrypted, and never your Salesforce password. It reads user records and writes campaigns — nothing else. Disconnecting revokes the token and clears every Salesforce-sourced value from your signatures at once.

Connect

1. In the portal, open Integrations and click Connect Salesforce. If your org uses a My Domain, or you want to connect a sandbox, enter that login host first (for example acme.my.salesforce.com or test.salesforce.com).
2. Sign in to Salesforce as an administrator and click Allow.
3. You are returned to the portal. The first sync runs immediately and the card shows how many Salesforce users matched a mailbox.

How people are matched

By email address, exactly. A Salesforce user is matched to a mailbox when the user's Email equals one of the mailbox's addresses — its primary address or any alias. Nothing fuzzier: a wrong guess would put one person's title on another person's mail.

Someone whose Salesforce email is not one of their work addresses does not match, and their signature simply keeps its directory values. The Integrations card lists unmatched users after each sync so you can fix the email in Salesforce.

Syncs run every hour. Sync now runs one on demand.

What wins

For title, phone and department: the Salesforce value when it is set, otherwise the directory value. An empty Salesforce field does not blank anything. Phone uses the user's Phone, falling back to Mobile, and is formatted for display the same way directory numbers are.

Name, email address and company details are never taken from Salesforce.

Campaigns (Marketing Core Analytics)

Give a banner a link in Design → Banner link. Clicks on that banner in delivered mail are counted — a number per banner per day, and nothing else: RubySig records no recipient, address, device or cookie.

On the Integrations card, turn on Report banner clicks to Salesforce as campaigns. RubySig creates one Campaign per linked banner, named RubySig · <template name>, of type Email, and keeps its description updated with the click total and the click rate against signatures sent. Existing campaigns are updated in place; renaming a template does not create a duplicate.

Reporting runs hourly with the sync. Turn it off to stop updating; the campaigns stay in Salesforce as history.

Caution: Salesforce only lets Marketing Users create campaigns. The administrator who connects RubySig needs the Marketing User checkbox on their Salesforce user record, or the report fails with "entity type cannot be inserted: Campaign". Tick it, then turn reporting off and on again.

Tip: Campaigns use standard fields only, so nothing has to be installed in your org. If you want the click count in a dedicated field for reports, add a number field to Campaign and tell us its API name.

Disconnect

Integrations → Disconnect. The token is revoked at Salesforce, the connection is removed, and every Salesforce-sourced title, phone and department is cleared immediately — signatures fall back to the directory on the next message.

Troubleshooting