Starbridge Salesforce integration: setup, sync, and account matching

This guide covers what the Starbridge Salesforce integration writes into records and the admin work required before anything syncs. It then covers how account matching determines what the integration can update and what reps see once it runs.

TL;DR: What is the Starbridge Salesforce integration?

The Starbridge Salesforce integration is a native, two-way connection. This means Starbridge writes to Salesforce, and Salesforce can write back to Starbridge.

The integration writes verified government and education contacts, enriched account data, and scores into Salesforce records, along with dated buying activity. It reads account ownership and account type back into Starbridge so each rep sees only their own territory.

What Starbridge syncs to Salesforce records

Account enrichment, account analysis and scores, and contacts are stored on standard Salesforce objects. Dated buying activity is stored on a custom object so each event keeps its own record.

Enrichment fills the fields Salesforce has no source for, including enrollment, population, budget amounts, and fiscal year start dates for the districts and agencies in your database.

Analysis and scoring build on that enrichment, covering propensity to spend and procurement approach. You can define an account score as a one-to-ten value or a red-yellow-green rating, or use a recommendation to contact the account now or nurture it. The result is written to the Account record.

Contacts are different because they change constantly. Starbridge finds net-new people at your target accounts, checks them against the contacts already in Salesforce, associates them with the right Account, and maintains them throughout the year.

Buying activity is where object choice matters. A meeting mention, a job change, an RFP, and a contract expiration all recur at the same account over time, so writing them to an Account field means each new entry erases the last. A custom object gives every event its own record associated with the Account, turning a single overwritten field into a history a rep can read.

Connecting Salesforce to Starbridge

The setup below has three steps for an admin with Setup access. The dedicated integration user in step two is strongly recommended rather than required.

1. Create three custom fields. Starbridge Account ID goes on the Account object as text. Starbridge Contact ID and Starbridge Is Active go on the Contact object, the first as text and the second as a checkbox. Salesforce appends __c to the API names, which is expected.
2. Create a dedicated integration user and permission set (strongly recommended). Give the user a Salesforce API Integration license, then build a permission set granting Read, Create, Edit, and View All Records on Accounts, Contacts, Leads, and Opportunities, plus Read and View All Records on Users. Also configure field-level Read and Edit access and include the system permission that approves uninstalled connected apps.
3. Authenticate and choose objects and fields. Connect as the integration user, then use the configuration guide to enable fields by use case. It recommends the fields each use case needs, so an admin can enable a whole use case in one action.

Two settings often catch teams out. Check the organization-wide default sharing for Contact before you finish. A restrictive Contact default blocks Starbridge from writing to contacts, no matter what the permission set allows, until you complete the extra sharing steps. Select the full set of use cases before you save. Every save starts a resync, and a large Salesforce org can spend hours on one.

Using a dedicated integration user rather than a personal login ensures the connection survives staff changes. When someone leaves, a connection authenticated under their profile starts failing, and you must reauthenticate as a new user with equivalent permissions to restore it.

Matching Salesforce accounts to government and education buyers

Starbridge matches each Salesforce Account to a government or education buyer using admin-mapped fields, then groups the results by match type for admin review. Only matches an admin has marked as reviewed are used by territories, buyer lists, and sync columns.

That review requirement is easy to miss during setup. An integration that looks connected produces little until someone works through the matching table.

Mapping of the fields drives match quality. The Account Name, State, and Starbridge Account ID fields are required.

Every optional detail you add improves the result, including Account Type, City, and Domain. Education and government records also carry unique identifiers such as NCES district IDs or IPEDS institution IDs, which produce the most reliable matches. Map them if your database includes them.

The results arrive grouped by how they were matched, which tells an admin how much scrutiny each group deserves. Accounts matched by a unique identifier or high-confidence AI need a spot check before bulk approval.

Medium-confidence matches deserve a closer look, since these are accounts where the name and state line up but a detail conflicts. The no-match group is usually correct rather than broken, because vendors, partners, and private companies in your CRM are not government or education buyers and should stay unmatched.

Duplicates get their own treatment. When several Salesforce accounts match one buyer, Starbridge classifies them using name similarity, domain comparison, and a language model. The admin then merges the true duplicates. Distinct sub-entities, such as a department or a campus, stay under the parent account instead.

Narrow the matching table with the rule filter, which excludes accounts from matching before review begins, instead of reviewing every record. Excluding international accounts and private sector records upfront keeps the table focused on the accounts that actually matter.

Keeping Salesforce account and contact data current

Enrichment stays current through scheduled sync columns. Admins customize the write behavior for each field: write-if-empty fills missing details while preserving existing values, and overwrite refreshes the fields selected for updates.

Choose overwrite for anything Starbridge maintains, such as scores, enrollment, and analysis, because a stale score is worse than no score. Choose write-if-empty for fields your reps curate themselves to keep the sync from erasing a note someone added after a call.

Contacts follow their own logic: Starbridge works down a chain of lookups. It checks the Starbridge Contact ID it wrote earlier, then a normalized email within the matched account, then first and last name within that account, then last name and phone for contacts with no email on file.

A record is created only when every lookup misses.

When it detects that a director has left a district, it sets Starbridge Is Active to false rather than deleting anything, so your team keeps the history and still has a clean field to filter campaigns against.

Two guardrails keep a sync from making a mess. Starbridge requires the account lookup to return a record before it creates a contact, so no contacts are created without a linked account. A lookup rule matching Starbridge Account ID to the Starbridge buyer identifier keeps the sync from creating duplicate accounts. Test the sync on the first five rows, check the Salesforce records, then run the rest.

Contact and account data decays continuously, so the cleanup is never finished. The sync keeps records current after the initial cleanup.

Using Starbridge means reps open a Salesforce account and immediately see who to call and what the district is spending. They also see what was discussed in its last board meeting and whether a competitor’s contract is ending. Nobody has to export a list to a spreadsheet to find out.

Mantra Health tripled its data enrichment coverage through the two-way Salesforce sync, enriching more than 3,000 accounts so every rep works from the same view of what each campus is investing in week to week.

Territories, alerts, and rep workflows in Salesforce

Once accounts are matched, Starbridge reads ownership from Salesforce and gives each rep a feed limited to the accounts they own. Reassigning an account moves its buying activity to the new owner overnight, without an admin needing to touch Starbridge.

That ownership link is what makes alerting safe to turn on. A Salesforce workflow that creates a task when a new buying activity record appears reaches the right rep by design, because the record is associated with an Account that already has an owner.

The rest is typical Salesforce work. A list view filtered on the Starbridge score gives reps a ranked queue instead of an alphabetical one.

A report joining buying activity records to closed opportunities shows which indicator types show up most often ahead of won deals. Sequence activity written back as native Salesforce activity lets the team see which outreach touched a contact first and most recently.

The connection runs in the other direction too.

Starbridge shows each buyer’s Salesforce account type on the buyer page, whether customer, prospect, or your own equivalent, with a single click through to the Salesforce record. A rep researching a district can immediately see that it is already a customer rather than pitching it cold.

Configure one of those workflows before the first full sync. Enriched records that nothing acts on show well in a review and leave the pipeline unchanged.

Getting the Salesforce integration right

Create the custom fields, then the integration user and its permission set, then enable every use case you expect to need in a single pass. Then give account matching the review time it deserves rather than bulk-approving it. Each stage depends on the one before it, so an admin who skips ahead ends up redoing the earlier work.

After that, start with the smallest workflow that will help a rep. Writing account scores to the Account object and filtering a list view on that score changes how a rep opens their day, and it needs no custom object. Contact enrichment is the natural next step, and a custom object for recurring buying activity is worth the setup work once reps are already acting on the first feed.

To see what the sync would put on your own Salesforce records, book a demo and bring an account your team is working on now.