GA now: Custom Activity Targets

Everybody would agree that Salesforce adoption ≠ logins.

But then the next question becomes:

What is adoption?

At GoElephant, we believe Salesforce adoption lives at the intersection of:

• Usage: what people actually do in Salesforce, and how consistently they do it
• Experience: How it feels to use Salesforce

The important word is consistency.

Because not every Salesforce user is expected to use Salesforce the same way.

Sales teams may only need to work in Salesforce a few times per week.

Customer service teams may be expected to live in Salesforce every day.

Leadership may only need visibility and occasional interaction.

‍

So if expectations differ across teams… How do you define “good adoption”?

‍

The problem with one-size-fits-all adoption metrics

Most adoption reporting treats every Salesforce user the same.

That creates misleading signals.

If your customer service team works in Salesforce daily while your finance team only touches Salesforce occasionally, should they really be measured against the same expectations?

Probably not.

But many organizations still use:

• One login threshold
• One activity expectation
• One adoption definition across the entire company

The result:

• Inflated risk in some teams
• Blind spots in others
• Misleading adoption scores
• Poor prioritization decisions

Definitions matter.

Because your definition of “expected usage” directly impacts:

• Adoption scores
• Reporting
• Prioritization
• And ultimately your understanding of Salesforce risk and ROI

‍

What our enterprise Salesforce customers asked for

Several enterprise customers raised the same challenge:

“We can’t measure adoption fairly if expectations are identical for everyone.”

They were right. So we introduced Custom Activity Targets.

‍

What’s new: Custom Activity Targets

You can now define different expected activity levels for different user groups.

This includes:

• Expected login frequency
• Expected usage frequency

Targets can be configured by:

• Role Hierarchy
• Or a picklist field on the user object (e.g. Function)

That means your GoElephant adoption scores now reflect how different parts of your organization are actually doing vs. your expected use of Salesforce.

What changes in practice

Before

• One adoption definition for all users
• Sales, Service, Leadership, and Finance treated the same
• Adoption scores disconnected from operational reality
• Unable to identify true adoption risk

After

• Adoption expectations aligned to real-world usage patterns
• Accurate adoption scoring
• Better visibility into under-engaged teams
• More meaningful prioritization and reporting