Salesforce Configuration

Salesforce configuration for Kopimore is more complex than HubSpot but supports more sophisticated routing and process logic. This lesson covers the key setup patterns for Salesforce teams.

Leads vs Accounts: The Key Decision

Most Salesforce teams need to decide upfront: does Kopimore create Leads or Accounts (with Contacts) for new identified visitors? The answer depends on your Salesforce architecture. Teams that use Leads as a top-of-funnel object should create Leads; teams that have moved to an Account-based model should create Accounts and Contacts directly.

Recommendation: if your SDRs work a Lead queue, create Leads. If your team works an Account list, create Accounts. Mixing models creates de-duplication nightmares.

Custom Fields to Create

On the Lead or Account object: Kopimore_Identified_Date__c (Date), Kopimore_Last_Visit_Page__c (Text 255), Kopimore_Session_Count__c (Number), Kopimore_ICP_Score__c (Number), Kopimore_Visit_Source__c (Text). On the Activity object: configure Kopimore to log visit sessions as Tasks or Events with Type = "Visitor Intelligence."

Salesforce Flow Configuration

Create a Record-Triggered Flow on Lead/Account creation with Source = "Kopimore." The flow should: evaluate assignment rules (match existing territory definitions), create the appropriate Task for the assigned rep, set a follow-up date based on ICP score, and trigger a Platform Event that fires your Slack notification.

Duplicate Prevention

Salesforce's native duplicate matching rules should be configured to match Kopimore-created records by domain, not email (since many Kopimore records don't have emails yet). Use Account.Website field as the duplicate matching key for company-level records.