If you’re tired of copy-pasting data between Salesforce and your sales enablement tools, you’re not alone. This guide is for people who actually use Salesforce and want their data to just work in Attention—without spending all day troubleshooting. If you want a real-world walkthrough instead of vague promises, you’re in the right spot.
Let’s get your Salesforce setup talking to Attention so you can spend less time on admin and more time actually selling.
What You Need Before You Start
Don’t skip this part—missing something here means you’ll be stuck before you even start.
- Salesforce admin access: You’ll need the ability to create and manage connected apps.
- Attention account: Make sure you have admin rights on your Attention workspace.
- A clear idea of what data you want to sync: Leads? Opportunities? Notes? Decide now or you’ll regret it later.
- (Optional) Test environment: If you have a Salesforce sandbox, use it first. Trust me.
Step 1: Map Out What to Sync
Before clicking anything, get clear on your must-have data. Most people just want contacts, leads, and maybe deal notes. The more fields you try to sync, the more headaches you’ll have. Start small; you can always expand later.
Pro tip: Make a simple spreadsheet or doc listing: - Salesforce object (e.g., Lead, Contact) - Fields you care about (e.g., Name, Email, Stage) - Which direction you want data to flow (Salesforce → Attention, or both ways)
This avoids surprises when you see weird data in your Attention dashboard.
Step 2: Set Up a Connected App in Salesforce
If you want Attention to pull (or push) data, Salesforce needs to know about it.
- Log into Salesforce with an admin account.
- Go to Setup (the gear icon in the top right).
- In the search bar, type “App Manager” and open it.
- Click New Connected App.
- Fill out the basics (Name, API Name, Email).
- In “API (Enable OAuth Settings)”:
- Check Enable OAuth Settings.
- Set the Callback URL (Attention’s docs will give you this, or it’s in their integration setup screen).
- Add the following OAuth scopes:
Access and manage your data (api)Perform requests on your behalf at any time (refresh_token, offline_access)
- Save and continue.
- Wait for Salesforce to provision the app (can take a few minutes).
You’ll need: - Consumer Key - Consumer Secret
Keep these somewhere safe—you’ll need them for Attention.
Step 3: Connect Salesforce in Attention
Now hop over to Attention.
- Go to Settings → Integrations.
- Choose Salesforce from the list.
- When prompted, enter the Consumer Key and Consumer Secret from your connected app.
- Input the Callback URL (should match what you put in Salesforce).
- Authenticate—Salesforce will ask you to approve the connection.
If you get an error here, double-check: - You copied the keys right (no extra spaces). - The user connecting has access to the data you want. - The callback URLs exactly match.
Don’t overthink the permissions: Start with read-only if you’re nervous. You can always open it up later.
Step 4: Configure What Gets Synced
Attention will usually offer a mapping screen. Here’s where people make things too complicated.
- Start with the basics: Name, Email, Phone, Stage.
- Map only the fields you need right now.
- Choose sync direction: one-way (Salesforce → Attention) or two-way. Unless you really need two-way, stick with one-way to avoid nasty overwrites.
Common pitfalls: - Mapping custom fields with weird names—test first. - Syncing “everything” and ending up with clutter. - Forgetting to exclude junk/test data.
Pro tip: Use filters to exclude inactive leads or test records. This keeps your Attention dashboards clean.
Step 5: Test with a Handful of Records
This is where reality hits.
- Pick 2-3 real (but safe) records—nothing sensitive, no test garbage.
- Change something in Salesforce (like updating a phone number).
- Watch for it to show up in Attention. Most syncs happen in minutes, not seconds.
- Try syncing back if you went two-way. Make sure nothing gets overwritten by mistake.
If it works, great. If not, triple-check your field mappings and permissions. It’s often something tiny.
Step 6: Roll Out to the Team
Once you trust the sync, you’re ready for more users.
- Communicate what’s changing: Let your team know which fields are now synced and where to look.
- Set expectations: Not every field updates instantly. There’s usually a short delay.
- Monitor for weirdness: For the first week, keep an eye out for duplicate records, missing data, or sync errors.
If someone reports a problem, check: - Is it a permission issue? - Was the field mapped properly? - Is it just a delay (wait 5–10 minutes)?
Step 7: Keep It Simple, Iterate Later
The urge to sync every possible field is real. Resist it.
- Keep your integration as lean as possible.
- Add new field mappings or objects only after you see real need.
- Document what you’ve configured (future you will thank you).
What’s worth ignoring (for now): - Super niche Salesforce objects nobody uses. - Trying to sync attachments or files. These are often a pain and break easily. - Overly complex two-way sync rules—start basic, then layer on complexity if you must.
Honest Takes: What Works, What Doesn’t
- Works well: Standard objects (Leads, Contacts, Opportunities), basic fields, one-way sync.
- Hits rough patches: Custom objects, fields with weird formats, two-way sync (especially with lots of users editing at once).
- Ignore the hype: No integration is truly “set it and forget it.” You’ll need to check on things from time to time.
Biggest gotcha: Permissions. If the Salesforce user you connect with can’t see a field, it won’t sync. Double-check profiles/sharing rules.
Wrapping Up
That’s it. Don’t let the “seamless” marketing fool you—good integrations are simple ones. Start small, test with real data, and grow from there. If something doesn’t work, it’s usually a mapping or permission hiccup. Stay patient, document your setup, and you’ll spend way less time fighting data and more time closing deals.
If you hit a snag, skip the sales pitch emails and check the community forums or docs first—they’re usually more honest anyway. Good luck, and keep it simple.