Salesforce in China — when the landing stack stalls

Salesforce in China is usually the wrong primary landing stack for ordinary Mainland China journeys. Salesforce, Marketo, Segment, and Tealium are one overseas martech class — forms, MQL, CDP, and tags on the China hostname typically stall, miss, or never complete. A Salesforce China plan is a China-reachable capture + automation path by job — not “keep the global landing stack and hope.” Keep the four only for residual HQ / Hong Kong / Taiwan / export jobs.

What Salesforce China means for the landing stack

Hard names your stack decision will use:

• Salesforce — Overseas CRM and automation used for landing forms, lead capture, and MQL routing. Origin: Salesforce. Chinaready Landscape labels Salesforce Marketing Cloud Limited — that Limited label is the MAP SKU signal, not a drop-in remap. Mapped Zhichi / Easemob tiles on that page are customer-service / IM, not this Guide’s landing-stack path.
• Marketo — Adobe Marketo Engage, the MAP in the same overseas class (Adobe Marketo Engage). Landscape’s Marketo alternatives page is the SKU verdict: Limited. Use that page for mapped candidates — do not treat a console that still opens as a Mainland China journey.
• Segment and Tealium — CDP and tag hosts on the same failure class as Google Tag Manager in China. Origins: Segment, Tealium. Landscape labels Segment Twilio Limited; mapped Sensors Data / GrowingIO are product-analytics shortlist, not this Guide’s landing-stack remap. They are not loopholes when Salesforce stalls. Drop them from the China hostname critical path.
• HTML 200 ≠ capture complete — The page host can return 200 while the form, MQL handoff, captcha, or tags never finish. Same class as website accessible in China and captcha forms in China. WordPress and CMS themes re-inject forms and tags: WordPress in China.
• Not a legal ban — Failure is reach, deliverability, data-residency stall, and missing China channels — not a claim that the four are prohibited. PIPL / export is a stall when you terminate or collect in Mainland China, not “cannot market.”
• Where the four still appear — Residual HQ / Hong Kong / Taiwan / export jobs, capped and off the China hostname’s critical path.
• Common myth — “Keep Salesforce as Plan A and add Marketo, Segment, or Tealium for China.” That is still the same overseas class.

Vocabulary first. Next: what must be true before Salesforce stays in scope at all.

What must be true before Salesforce stays in scope

Missing a clear capture job stops your product team before a “keep Salesforce, add China” sprint is real work.

Precondition	Why your process stalls
Capture job locked — ordinary Mainland China landing journeys vs residual HQ / Hong Kong / Taiwan / export	Wrong job keeps Salesforce as Plan A while China-reachable capture never starts
Stack class named — Salesforce + Marketo + Segment + Tealium as one overseas class, not four separate China SKUs	Teams “fix Salesforce” by adding Marketo, Segment, or Tealium and stay on the same stall
Form vs tag path named — landing form / MQL vs CDP / tag hosts on the China hostname	A working HQ Salesforce admin is reported as “Salesforce China works” while Mainland China submit never completes
Honest host assumption — do not assume Salesforce, Marketo, Segment, or Tealium hosts behave like other markets for Mainland China users on local networks	Plans built on everyday global landing-stack usage invent a journey that is not there
Supplementary budget / scope cap if the four stay for residual jobs	Unlimited “Salesforce for China” on the global stack crowds out capture and automation remap
Mainland China vantage proof on form, MQL, captcha, and tag hosts	Overseas QA “passes” while China users never complete the form — same class as website not working in China
China-reachable capture + automation named by job when Mainland China users are the job — not “martech somewhere in China”	Stopping Salesforce Plan A without a chosen path just pauses MQL

Product teams usually cannot treat “ship the same landing stack globally” as the Mainland China plan. Job clarity and remapping are the floor. SKU orientation for the MAP lives on Marketo alternatives.

From capture job to remap or residual Salesforce

Stage	Decision / outcome
1. Name the capture job	Ordinary Mainland China landing journeys at scale, or residual HQ / Hong Kong / Taiwan / export only?
2. If Mainland China ordinary reach	Rule Salesforce, Marketo, Segment, and Tealium out as primary — one overseas class, not four separate China SKUs
3. Pick capture + automation by job	WeChat-centric — Tencent Qidian-class. Mainland-first B2B CRM + automation — Fxiaoke-class. Ecommerce / retail — Weimob Marketing Cloud-class. SMB / trade — Zoho CRM-class. Landscape’s Marketo page holds those SKUs
4. Tags on the page	Drop GTM, Tealium, and Segment from the China hostname critical path — Google Tag Manager in China
5. If a residual Salesforce-class job remains	Keep the four as a capped supplementary line with clear geo — not the China landing stack
6. Prove hosts from Mainland China, then re-test	Form, MQL, captcha, and remaining tags from broadband + mobile (or China Network Diagnostics). A later marketing snippet can restore Salesforce, Marketo, Segment, or Tealium

Hard gate — primary vs residual

Necessity: confusing these two jobs wastes the quarter — either you keep optimizing a Salesforce China widget that never becomes a Mainland China journey, or you delete HQ measurement and export capture that was never the China path.

Job	Salesforce / Marketo / Segment / Tealium role	What must already be true
Ordinary Mainland China landing (form, MQL, automation, tags)	Not primary — remap	China-reachable capture + automation named by job; tag hosts dropped from the China hostname
Hong Kong / Taiwan / export / HQ	May remain supplementary	Geo and hostname match that residual audience; China hostname critical path does not call the four
“Salesforce in China” via geo toggle, extra MAP, or extra CDP	Myth as Mainland China plan	Host and channel reachability from the user network — not a Salesforce region setting

Hard gate — remap by job, not a vendor dump

A Salesforce China plan that still loads the overseas landing stack is not a China journey. After the fork, pick by job. Landscape currently maps candidates on Marketo alternatives — Fxiaoke, Tencent Qidian, Weimob Marketing Cloud, Zoho CRM. Do not reprint that table here. Do not treat Salesforce Marketing Cloud Zhichi / Easemob tiles as this remap.

Job	Start here	Honest next decision
WeChat-centric acquisition	Tencent Qidian-class	WeChat is already the path; do not dump the product into the global Salesforce org
Mainland-first B2B CRM + automation	Fxiaoke-class	Ordinary Mainland China MQL and CRM live on China-reachable rails
Ecommerce / retail journeys	Weimob Marketing Cloud-class	Retail capture and automation, not a Marketo campaign copy
SMB / trade	Zoho CRM-class	Localized CRM when a full MAP suite is the wrong scale
Tags on the China hostname	Drop GTM / Tealium / Segment	Google Tag Manager in China — not a new overseas loader

Confirm channel fit, deliverability, and entity on the rails you choose. This Guide does not reprint apply paths.

Why the overseas landing stack still stalls

Engineering and ops constraints you must design around:

Constraint	What breaks	What to do
Overseas CRM / MAP hosts	Landing forms and MQL routing still terminate on Salesforce or Marketo. The HTML can return 200 while submit, scoring, or email never complete. Landscape labels Marketo Limited and Salesforce Marketing Cloud Limited.	Prove the host from Mainland China vantage, then remap by job. Do not treat “try Salesforce, then Marketo on timeout” as Plan A.
CDP / tag hosts	Segment and Tealium are GTM-adjacent loaders. Child tags (ads, captcha, chat) still miss.	Drop from the China hostname critical path. Inventory each remaining host — Google Tag Manager in China, captcha forms in China.
Email and channel gap	Cross-border email into Mainland China is filtered or delayed; WeChat / WeCom / Douyin-class channels are missing from the overseas stack.	Remap automation onto a job-fit China path. Limited is usefulness, not a green console.
Data-residency stall	Collecting or terminating personal information in Mainland China can stall on PIPL / export — not a claim that marketing is illegal.	Name where capture terminates before you copy the global form. Do not invent a filing outcome.
CMS / theme injection	WordPress and builders re-inject Salesforce forms, Marketo tracking snippets, Segment, or Tealium after a “clean” launch.	Treat those snippets as deps on WordPress in China. Re-test after marketing changes.
Access acceleration without stack rewrite	Faster HTML does not resurrect stalled form, MAP, CDP, or tag hosts.	Change the landing-stack class, then tune delivery — website accessible in China.

Stalled form ≠ legal ban. Salesforce China failure for ordinary Mainland China journeys is reach, deliverability, residency stall, and missing China channels — not a prohibition.

HQ admin OK → false confidence. A laptop outside Mainland China can still open Salesforce or Marketo while the visitor never completes capture. Users describe “form broken”; engineering sees 200s on the page host.

Reporting residual HQ / Hong Kong / Taiwan traffic as China landing working → wrong stack. VPN-using testers are not ordinary Mainland China users at scale.

Adding Segment or Tealium after Salesforce stalls → same class. CDP and tag hosts are not a China capture plan.

What stalls teams that keep Salesforce as Plan A

• Geo-toggle thinking — Product treats “China” as a Salesforce market expand before a China-reachable capture path exists.
• Four parallel SKU tracks — Teams staff four “does it work” tickets instead of one overseas-class fork.
• HQ laptop QA — Testers outside Mainland China never see the stalled form, so the ticket never opens.
• Hong Kong / Taiwan conflated with Mainland China — Outside-Mainland China performance is reported as Salesforce China working.
• MAP or CDP as a Salesforce fix — Marketo, Segment, or Tealium is added on the same hostname. The class does not change.
• Captcha left on Google hosts — Submit still waits after “we remapped CRM.”
• Theme defaults that re-inject the stack — CMS, GTM, and “global landing” components restore Salesforce, Marketo, Segment, or Tealium.
• No owner for the job remap — The fork stalls because nobody owns WeChat-centric, Mainland-first B2B, retail, or SMB capture — only “make Salesforce work in China.”

What “fixed” means: Mainland China users can complete the capture journeys you claim; one landing-stack class is on that client path; Salesforce, Marketo, Segment, and Tealium are gone from it; residual jobs are named and capped; the China-reachable capture + automation path is named by job (Fxiaoke-class, Tencent Qidian-class, Weimob Marketing Cloud-class, or Zoho CRM-class as the job requires). Overseas-only Salesforce with a China landing claim is not fixed.

China landing partner when the landing stack is the product

Most product teams exploring Mainland China entry need a China landing partner once they stop treating Salesforce as Plan A — to stand up China-reachable capture and job-based automation (WeChat-centric, Mainland-first B2B, retail, or SMB), drop GTM / Segment / Tealium from the China hostname critical path, run Mandarin ops, and prove the form from Mainland China broadband and mobile. Your team still owns which journeys must convert and which residual HQ line to keep; the partner path makes that remapped landing stack executable when those rails are not already in-house. Keeping a capped Salesforce line for residual outside-Mainland China jobs does not remove the need for that China landing partner on the primary China path.

What we can offer?

Salesforce in China work for Mainland China is a primary-vs-residual decision before any “keep the same landing stack” sprint. Chinaready helps your product team remap capture and automation to rails that can actually complete for Mainland China users — a job-based China path, not a Salesforce form hope:

1. China Readiness Assessment — Decide whether Salesforce, Marketo, Segment, and Tealium are residual only, which capture journeys must complete in Mainland China, and which job, host, and entity gates sit on the critical path before a remap date.
2. China Access Acceleration — Keep China-facing pages and conversion paths reachable and fast from Mainland China vantage so remapped capture does not die on leftover overseas form, MAP, or tag hosts.
3. China Product Hosting — Place China-critical landing pages where ICP adjacency, entity consistency, and capture destinations stay coherent after Salesforce-class hosts leave the journey.
4. Mobile App Distribution — Align any China app or Mini Program capture with the chosen job path — not mistake a Salesforce WebView form for a China landing plan.

Contact us when you need a Mainland China landing-stack remap before you staff another Salesforce China form sprint.