CONNECTIONS / Salesforce / Salesforce to TikTok CRM
Salesforce lead stages, feeding TikTok's optimization.
TikTok's lead objective improves when it can see which leads actually turned into pipeline. Signals reads Salesforce lead status and opportunity stage and keeps the CRM Events API feed current.
- ● salesforce → tiktok.crm_integration :: live
- > event Lead status change Working→Qualified
- > event Opportunity stage change Qualified→Proposal
- hash sha256(email,phone)
- route tiktok.crm_integration match 84%
- ✓ delivered · stage recorded
WHAT THIS ENABLES
Salesforce to TikTok CRM Integration
Salesforce to TikTok CRM Integration is the pipeline that maps Salesforce lead status and opportunity stage changes into TikTok's CRM Events API, so TikTok's lead-generation optimization learns from qualified pipeline instead of raw form-fill counts.
- Salesforce lead and opportunity stages reported to TikTok as distinct, optimizable events.
- TikTok bidding weighted toward the funnel depth your revenue team actually cares about.
- A CRM feed that runs on Salesforce's own update cadence, not a batch export.
WHAT FLOWS WHERE
Salesforce to CRM Integration, mapped.
Lead status and Opportunity stage changes leave Salesforce, are hashed and deduped by Signals, and post to TikTok's CRM Events API as stage-mapped conversion events.
Lead status and Opportunity stage changes leave Salesforce, are hashed and deduped by Signals, and post to TikTok's CRM Events API as stage-mapped conversion events.
Built for the teams that own the number.
BFSI, auto, real estate, and EdTech teams qualifying TikTok leads inside Salesforce.
From kickoff to verified events.
-
Connect
Connected App authorization scoped to the Salesforce Lead and Opportunity objects.
-
Map
Lead status and Opportunity stage values mapped to TikTok-recognized CRM events.
-
Deliver
Server-side delivery with hashed identifiers, monitored end to end.
What ships with this use case.
TikTok optimizing lead campaigns toward Salesforce stages that predict revenue rather than raw submissions.
Stage events flowing continuously, without a recurring export task on anyone's calendar.
Hashed, consent-aware identifier handling from Salesforce straight through delivery.
What CRM Integration actually receives.
- ● signals :: event payload
- > POST /event/track source=salesforce.lead
- event "Contact" · event_time 1783948020
- user.email sha256 "2e9f34…" · user.phone sha256 "77bc10…"
- properties.lead_status "Qualified"
- ✓ accepted · dedupe=event_id
Adjacent moves on the same stack.
from Salesforce
Salesforce to Meta Conversion Leads
Salesforce to Meta CAPI for CRM is the pipeline that maps opportunity stage changes and…
Learn more
from Salesforce
Salesforce to Google EC for Leads
Salesforce to Google Enhanced Conversions for Leads captures GCLID at the lead form,…
Learn more
same use case
ActiveCampaign to TikTok CRM
ActiveCampaign to TikTok CRM Integration: Signals reads your ActiveCampaign contacts and…
Learn moregeneric
TikTok CRM Integration
Sync qualified lead stages from your CRM back to TikTok so lead-based campaigns optimize on…
Learn moreAsked on almost every call.
Which Salesforce stages should feed TikTok's CRM Events API?
The stages that predict revenue, most commonly qualified lead, opportunity, and closed won. TikTok's optimization works best with at least one down-funnel stage arriving at steady volume, and we help you pick which Salesforce stage to send first if current pipeline is thin.
How does TikTok avoid double counting a Salesforce lead that changes stage twice quickly?
Each stage change carries its own event and a stable identifier derived from the Salesforce record, so a lead moving from MQL to SQL within the same hour sends two distinct, dedupable events rather than one ambiguous update. TikTok's CRM Events API processes each on its own merits.
NEXT STEP