Tracking behaviour on Salesforce tasks that could point at anything

What was going on

Salesforce’s Task and Event objects use polymorphic relationships, so a single record can be linked to an Opportunity, a support case or something else entirely. That flexibility made it hard to run SOQL queries or build useful insights about behaviours tied to goals such as closing deals or resolving cases.

Customers wanted accurate reporting to support coaching, training and strategy.

What I was asked to do

• Track user behaviours on Tasks and Events and link them to related Opportunities and support cases
• Stay low-code and within the constraints of our product’s managed package, using Salesforce Flow
• Give customers actionable insight that lines up user actions with business goals
• Make it easy to extend later without redevelopment

What I did

I created a custom object to store behavioural data: related record ID, object name, user ID, created and last-modified dates, written whenever specific behaviours happened on Tasks or Events.

• Built a Flow that listens for created and updated Tasks and Events and writes the matching records
• Used a custom Apex Trigger within our managed package to process and report on the data
• Tested extensively in sandboxes for accuracy and performance
• Worked with stakeholders to refine reporting needs

What changed

Customers could measure behaviours on Tasks and Events accurately and tie them to Opportunities and cases. Managers could see where teams needed coaching or training.

• The data exposed inefficiencies in existing processes, leading to recommendations for better tools and workflows
• The low-code design kept maintenance minimal and made future enhancement simple

Doing it responsibly

Behavioural data was processed securely under GDPR and local law, with access limited through Salesforce permissions. I documented what was captured and why, tested for accuracy and ran a post-implementation review to confirm ongoing compliance.