Step by step guide to integrating Centrical with Salesforce for sales teams

So, your sales team is using Salesforce, but you want more out of it—like real-time coaching, contests, and performance nudges. That’s where Centrical comes in. It promises to amp up engagement and productivity by layering on game mechanics, micro-learning, and performance tracking. But getting Centrical talking to Salesforce isn’t always as easy as the sales deck makes it sound.

This guide is for admins, ops folks, and sales enablement leads who want the real steps for connecting Centrical to Salesforce—without getting lost in vendor hype or “strategic” hand-waving. We’ll go step by step, flag what matters, and call out what you can skip.

Why connect Centrical to Salesforce?

Quick reality check: Salesforce is where your sales data lives, but it’s not great at motivating reps or delivering coaching on the fly. Centrical can fill that gap—if you set up the integration right. Done well, you’ll get:

Automated updates from Salesforce activities (calls, opportunities, etc.) feeding into Centrical’s dashboards and competitions
Real-time feedback and “nudges” for reps based on the latest CRM data
Less manual admin, fewer spreadsheets

But: a sloppy integration means bad data, confusion, and annoyed reps. So let’s do it right.

Step 1: Get the basics lined up

Before you touch any settings, get your ducks in a row.

Check your licenses: You need access to both Centrical and Salesforce, obviously. For Salesforce, you’ll want admin rights—at least enough to manage connected apps and data permissions.
Talk to your Centrical rep: Centrical isn’t a plug-and-play Salesforce app. You’ll need an integration “module” or feature enabled. Confirm what’s in your contract.
Pick your data: Figure out which Salesforce objects you actually need in Centrical (Opportunities, Leads, Accounts, Activities, etc.). Don’t just sync everything—more is not better.
Map your fields: Decide which fields matter. Custom fields in Salesforce? Note them now.

Pro tip: Write down your must-haves and nice-to-haves before any calls with vendors or IT. It’ll keep you focused and help you push back on “default” settings that don’t fit.

Step 2: Set up API access in Salesforce

Centrical connects via Salesforce’s API. This is where most headaches happen, so slow down and follow these steps:

Create a Salesforce Integration User
Don’t use your personal admin account. Create a dedicated “Centrical Integration” user in Salesforce.
Give it only the permissions it needs—ideally, read access to relevant objects, maybe write if Centrical will push anything back.
Set up a Connected App
Go to Salesforce Setup > App Manager > New Connected App.
Fill in basics (name, email).
Enable OAuth settings. Add:
- Full access (full) or just Access and manage your data (api)—be as restrictive as possible.
- Set callback URL (get this from Centrical docs or your rep).
Save and wait for Salesforce to provision the app (can take 2-10 mins).
Grab your credentials
After saving, grab the Consumer Key and Consumer Secret.
Save these somewhere secure—don’t email them.
Whitelist IPs (if needed)
If your org uses IP restrictions, make sure Centrical’s servers are whitelisted. You’ll need their IPs—ask support; don’t guess.

Heads up: If your Salesforce org has strict security policies (MFA, IP restrictions, etc.), loop in your IT/security team now. Surprises here are the #1 cause of delays.

Step 3: Connect Centrical to Salesforce

Now, flip over to Centrical. This part varies a bit depending on your agreement and Centrical’s latest UI, but the core steps are the same.

Log into Centrical as an Admin
Navigate to Integrations
Usually found under Admin or Platform Settings.
Look for “Salesforce Integration” or similar wording.
Enter Salesforce Credentials
Plug in the Consumer Key, Consumer Secret, and the username/password for your dedicated integration user.
Enter the callback URL and any other required fields.
Authorize the Connection
You’ll be redirected to Salesforce to log in and approve permissions.
Double-check which permissions you’re granting—don’t just click “Allow” blindly.
Test the Connection
Centrical should tell you if the connection is successful.
If you get errors, check:
- API permissions
- IP whitelisting
- Correct credentials (no copy-paste typos)

Reality check: This is where things often break. Be patient, and don’t be afraid to escalate to Centrical support or your Salesforce admin. Sometimes you’ll hit bugs or undocumented “features.”

Step 4: Configure what data gets synced

Here’s where you can go overboard—or make life easier for everyone.

Choose objects and fields: Start with the basics—Opportunities, Leads, Accounts. Only add more if you have a clear use case.
Set sync frequency: Real-time is tempting, but daily or hourly is usually enough for most sales teams. Real-time syncs can cause API limits and weird edge-case issues.
Map fields: Centrical may have default mappings, but check them—especially if you use custom fields or non-standard objects.
Decide on direction: Usually, data flows from Salesforce to Centrical. If you want Centrical to push data back to Salesforce (rare), tread carefully and test in a sandbox first.

What to skip: Don’t sync every field “just in case.” More data means more confusion and more places for things to break. Start lean.

Step 5: Test with a sandbox (if you can)

If your org has a Salesforce sandbox (test environment), use it. Here’s why:

No risk to live data: Mistakes won’t affect real opportunities or reports.
Catch mapping errors: You’ll spot weird field mismatches or missing data early.
Train your team: You can test what Centrical displays before rolling it out.

If you don’t have a sandbox, be extra careful—test with a small, non-critical data set and double-check everything.

Step 6: Roll out to your sales team (the human bit)

Tech is only half the battle. If you skip this, expect confusion and eye rolls from your reps.

Communicate clearly: Tell the team what’s changing and why. “You’ll see contests and coaching based on real Salesforce data” is better than “new engagement solution.”
Demo the integration: Show what data flows from Salesforce to Centrical, and what reps are supposed to do.
Get feedback: There will be questions and some grumbling. Collect feedback, and be ready to tweak settings or data mappings.
Check for adoption: Use Centrical’s reporting to see if reps are logging in, participating in challenges, and seeing their updated metrics.

Pro tip: Don’t force everything at once. Start with a pilot group of reps or managers, iron out the kinks, then roll out to the full team.

Step 7: Monitor, maintain, and iterate

Integrations aren’t “set and forget.” Once you’re live:

Watch for sync failures: Set up alerts (if Centrical offers them) or check logs weekly.
Review usage: Are reps actually using Centrical? If not, figure out why.
Update mappings as your Salesforce changes: New fields, new processes—these can break the integration or make it less useful.
Audit permissions: Periodically check that the integration user doesn’t have more access than it needs.
Don’t chase every shiny feature: Stick to what actually helps your team hit their goals.

Common pitfalls (and how to dodge them)

Trying to sync everything: Resist the urge. More data = more problems.
Overcomplicating rewards/contests: If reps can’t figure out how to “win,” the whole thing flops.
Ignoring security policies: IT will not be amused if you blow past their rules. Always check before changing permissions.
Not involving end users: Tech for tech’s sake never works. Get reps and managers involved early.

Final thoughts: Keep it simple, keep it useful

Integrating Centrical with Salesforce can boost engagement and performance—but only if you set it up thoughtfully and keep things simple. Start with the basics, test carefully, and get honest feedback from your team. Don’t get distracted by every bell and whistle. Iterate as you go, and you’ll actually see the impact (without pulling your hair out).

Good luck—and don’t be afraid to push back on “default” settings. Your team will thank you.