WhatCounts + Salesforce
Connect WhatCounts and Salesforce to Unify Email Marketing with Your CRM
Automate contact sync, campaign data flow, and lead nurturing between WhatCounts and Salesforce without writing a single line of code.
Why integrate WhatCounts and Salesforce?
WhatCounts is an email marketing platform brands use to run personalized, data-driven campaigns at scale. Salesforce is the CRM most sales teams live in. Together they should form a complete revenue marketing engine — but without integration, marketing and sales end up working in silos, manually exporting lists and reconciling engagement data after the fact. Connecting WhatCounts and Salesforce through tray.ai means every email interaction reaches your sales team in real time, and every CRM update keeps your email audiences properly segmented.
Automate & integrate WhatCounts & Salesforce
Use case
Automatic Contact and Lead Sync from Salesforce to WhatCounts
Whenever a new lead or contact is created or updated in Salesforce, tray.ai automatically adds or updates the corresponding subscriber record in WhatCounts with the correct list membership, custom field values, and suppression status. No more manual CSV exports, and no more marketing teams working from contact data that was accurate two weeks ago. Sales-qualified leads get enrolled in targeted nurture tracks immediately, with no manual handoff required.
Use case
Sync WhatCounts Email Engagement Data Back to Salesforce
Email opens, clicks, bounces, and unsubscribes captured in WhatCounts are automatically written back to the corresponding Salesforce contact or lead record, giving sales reps a full picture of a prospect's email history. This data can populate custom Salesforce fields, update activity timelines, or trigger workflow rules and alerts. Sales teams can prioritize outreach based on actual engagement without ever leaving Salesforce.
Use case
Trigger Salesforce Opportunities or Tasks Based on Email Clicks
When a contact clicks a high-intent link in a WhatCounts campaign — a pricing page, demo request, or product tour — tray.ai can automatically create a Salesforce task, update an existing opportunity stage, or notify the assigned sales rep via Chatter or email. Hot leads get acted on immediately instead of sitting in a batch report until Friday. Marketing and sales teams can define custom click-based triggers for each stage of their funnel.
Use case
Dynamic List Segmentation Driven by Salesforce CRM Data
Using Salesforce fields like lead score, account tier, industry, geographic region, or opportunity stage, tray.ai automatically maintains dynamic WhatCounts subscriber lists that update in real time as CRM data changes. Marketers can launch highly personalized campaigns knowing their audience lists reflect what's actually in Salesforce right now — not what was exported last month.
Use case
Automated Unsubscribe and Suppression Management
When a contact unsubscribes or marks an email as spam in WhatCounts, tray.ai immediately updates the corresponding Salesforce record to reflect their opt-out status and suppresses them from future Salesforce marketing campaigns or Campaign member lists. This bidirectional suppression sync keeps you compliant with CAN-SPAM, GDPR, and other regulations across both platforms. No one needs to manually cross-reference suppression lists between systems.
Use case
Campaign Performance Reporting Aggregated in Salesforce
tray.ai pulls WhatCounts campaign metrics — send volume, open rates, click-through rates, conversion data — and writes them directly into custom Salesforce objects or Campaign records. Marketing leaders can see email performance alongside pipeline and revenue data in a single Salesforce dashboard. No more manually compiling reports across two platforms to answer basic questions about what's working.
Use case
Salesforce Campaign Membership Enrollment into WhatCounts Journeys
When a contact is added to a Salesforce Campaign as a Campaign Member, tray.ai can automatically enroll them in a matching WhatCounts email journey or drip sequence built for that campaign's goal. Every sales motion gets a corresponding email nurture track running alongside it. Campaign members who advance stages in Salesforce can also be moved to different WhatCounts journeys automatically to match where they actually are.
Get started with WhatCounts & Salesforce integration today
WhatCounts & Salesforce Challenges
What challenges are there when working with WhatCounts & Salesforce and how will using Tray.ai help?
Challenge
Bidirectional Data Sync Without Creating Duplicate Records
Syncing contacts between WhatCounts and Salesforce in both directions carries a real risk of creating duplicate subscriber or lead records — especially when the same email address exists as both a Lead and a Contact in Salesforce, or when multiple WhatCounts lists contain the same subscriber.
How Tray.ai Can Help:
tray.ai's workflow logic performs deduplication lookups across Salesforce Lead and Contact objects before creating new records, using email address as a unique key. Built-in conditional branching lets the workflow upsert existing records rather than create duplicates, and custom field mapping ensures the correct Salesforce object type is always targeted based on your business rules.
Challenge
Handling Salesforce API Governor Limits at Scale
Salesforce enforces strict API call limits per 24-hour period. High-volume bidirectional syncs between WhatCounts and Salesforce — particularly for large subscriber lists or frequent engagement event polling — can burn through those limits fast, causing sync failures and data gaps.
How Tray.ai Can Help:
tray.ai uses intelligent API call batching and rate-limit-aware request pacing to get the most out of each Salesforce API call. Bulk update patterns consolidate multiple record updates into single API requests wherever possible, and tray.ai's built-in retry and error-handling framework queues throttled calls and retries them automatically so no data is lost.
Challenge
Mapping Complex Salesforce Data Structures to WhatCounts Subscriber Fields
Salesforce stores data across multiple related objects — Contacts, Leads, Accounts, Opportunities, and custom objects — while WhatCounts subscriber records use a much flatter field structure. Getting rich relational CRM data into meaningful WhatCounts subscriber attributes and list memberships takes careful field mapping and transformation logic.
How Tray.ai Can Help:
tray.ai's visual data mapper and built-in transformation operators let teams define field mapping rules that pull data from multiple Salesforce objects in a single workflow and compose WhatCounts subscriber attributes from them. Lookup steps can retrieve related Account or Opportunity fields and merge them into the subscriber payload before sending to WhatCounts — no custom code required.
Challenge
Maintaining Compliance Across Opt-Out and Suppression Lists
Opt-outs captured in WhatCounts need to show up in Salesforce immediately. Contacts marked as Do Not Email in Salesforce should never get re-added to active WhatCounts lists. That's both a compliance requirement and a genuinely tricky synchronization problem that manual processes can't handle reliably.
How Tray.ai Can Help:
tray.ai supports real-time event-driven workflows that fire immediately on opt-out events in WhatCounts, updating Salesforce records within seconds. Guard logic in Salesforce-to-WhatCounts sync workflows checks the opt-out status of every contact before adding or re-adding them to any WhatCounts list, creating a compliance gate that runs continuously and automatically.
Challenge
Keeping Sync Workflows Resilient Through API and Schema Changes
Both WhatCounts and Salesforce are actively developed platforms. API updates, deprecated endpoints, and admin-driven field renames can silently break integration workflows — and the failure often isn't obvious to marketing or sales teams until data has already stopped flowing.
How Tray.ai Can Help:
tray.ai's centralized workflow monitoring dashboard surfaces API errors, failed steps, and data mapping mismatches in real time, with configurable alerts that notify the right people immediately when a sync workflow fails. The connector layer abstracts API version changes where possible, and flexible field mapping configuration makes it straightforward to adapt workflows to schema changes without rebuilding integrations from scratch.
Start using our pre-built WhatCounts & Salesforce templates today
Start from scratch or use one of our pre-built WhatCounts & Salesforce templates to quickly solve your most common use cases.
WhatCounts & Salesforce Templates
Find pre-built WhatCounts & Salesforce solutions for common use cases
Template
New Salesforce Lead to WhatCounts Subscriber Enrollment
Automatically adds every new Salesforce lead to a designated WhatCounts subscriber list with mapped custom fields, triggering a welcome or nurture email sequence immediately upon lead creation.
Steps:
- Trigger fires when a new Lead record is created in Salesforce
- tray.ai maps Salesforce lead fields — name, email, company, lead source, and custom fields — to the corresponding WhatCounts subscriber attributes
- Subscriber is created or updated in the appropriate WhatCounts list and enrolled in the configured welcome or nurture journey
Connectors Used: Salesforce, WhatCounts
Template
WhatCounts Email Engagement Sync to Salesforce Activity Timeline
Polls WhatCounts for recent email engagement events — opens, clicks, and bounces — and logs each interaction as an Activity or Task on the matching Salesforce lead or contact record.
Steps:
- tray.ai polls WhatCounts on a scheduled interval to retrieve new engagement events since the last sync
- Each event is matched to the corresponding Salesforce lead or contact record by email address
- An Activity log entry or Task is created in Salesforce with details of the email interaction, including campaign name, subject line, and event type
Connectors Used: WhatCounts, Salesforce
Template
High-Intent Email Click to Salesforce Task and Rep Alert
Monitors WhatCounts for clicks on defined high-intent links and instantly creates a follow-up Task in Salesforce assigned to the contact's owner, with an optional Chatter notification to prompt immediate outreach.
Steps:
- tray.ai listens for click events on specified URLs or link categories within WhatCounts campaigns
- The clicking contact is looked up in Salesforce by email address to retrieve their record ID and assigned owner
- A high-priority Salesforce Task is created and assigned to the contact owner, and an optional Chatter post notifies the rep with campaign context and clicked URL details
Connectors Used: WhatCounts, Salesforce
Template
WhatCounts Unsubscribe to Salesforce Opt-Out Sync
Detects unsubscribe and spam complaint events in WhatCounts and immediately updates the corresponding Salesforce contact or lead record to mark the contact as opted out and removes them from active Salesforce Campaign membership.
Steps:
- tray.ai receives or polls for unsubscribe and spam complaint events from WhatCounts
- The affected subscriber is located in Salesforce by email address across both Lead and Contact objects
- The Salesforce record's email opt-out field is updated to true and the contact is removed from any active Campaign Member records to prevent future marketing sends
Connectors Used: WhatCounts, Salesforce
Template
Salesforce Opportunity Stage Change to WhatCounts Journey Transition
Monitors Salesforce for opportunity stage changes and automatically moves the associated contact from one WhatCounts email journey to another that matches the new sales stage, so marketing communications stay relevant as deals progress.
Steps:
- Trigger fires when a Salesforce Opportunity stage field is updated to a defined value — for example, Proposal Sent or Closed Won
- tray.ai retrieves the primary contact associated with the Opportunity from Salesforce
- The contact is removed from their current WhatCounts journey and enrolled in the new journey that corresponds to the updated opportunity stage
Connectors Used: Salesforce, WhatCounts
Template
WhatCounts Campaign Metrics to Salesforce Campaign Records
Periodically fetches performance metrics from completed WhatCounts campaigns and writes send count, open rate, click rate, and unsubscribe rate into the corresponding Salesforce Campaign record for unified reporting.
Steps:
- tray.ai runs on a scheduled trigger to fetch completed campaign statistics from the WhatCounts API
- Each WhatCounts campaign is matched to its corresponding Salesforce Campaign record by name, external ID, or custom mapping
- Campaign statistics are written into custom numeric fields on the Salesforce Campaign record and a sync timestamp is updated for audit purposes
Connectors Used: WhatCounts, Salesforce