Skip to content

docs(audiences): document Export sync toggle as prerequisite for Salesforce write-back#1614

Merged
george-dilthey merged 1 commit into
mainfrom
docsbot/doc-1221-intercom-tag-0717-1d1ed07b
Jul 17, 2026
Merged

docs(audiences): document Export sync toggle as prerequisite for Salesforce write-back#1614
george-dilthey merged 1 commit into
mainfrom
docsbot/doc-1221-intercom-tag-0717-1d1ed07b

Conversation

@george-dilthey

Copy link
Copy Markdown
Contributor

What changed

Added explicit instructions for enabling the Export sync toggle to docs/audiences.md in two places:

  1. "Writing back to your CRM" section — updated the opening sentence (previously "Enriched data and segment changes write back automatically") to clearly state that the Export sync toggle is the required master switch before any data flows to Salesforce. Added a step-by-step "To enable Export sync" block explaining the exact navigation path (Settings → Sources/Destinations → object tab → Export [Object] data → toggle on Export sync).

  2. New FAQ — added "I've mapped fields to Salesforce but the data isn't syncing — why?" to the FAQ section, directly mirroring the customer's question. Points to the Export sync toggle as the primary cause and repeats the enabling steps.

Why

Intercom conversation #215475130065193: Gabriel Griffith (Saviynt, Enterprise) mapped fields to the Salesforce Account object with "Always write" rules but saw no data flowing to Salesforce. Fin couldn't resolve this and escalated. Support engineer Peter Johnston explained the fix: the Export sync toggle in Settings → Sources/Destinations → Export Accounts data must be enabled — it's a master switch, and field-level write rules are irrelevant until it's on. Customer confirmed the fix worked by sharing a screenshot of the toggle enabled.

The existing "Writing back to your CRM" section said "Enriched data and segment changes write back automatically" — misleading because it implies no setup is required. The setup steps (step 4) told users to leave Export Sync "off for now" during initial import setup but never told them when or how to turn it on. No FAQ covered this exact symptom.

Source link(s)

  • Intercom conversation: https://app.intercom.com/a/inbox/w28k1kwz/inbox/conversation/215475130065193
  • Verifier verdict: PASS for both claims (Export sync as master switch, 24h cadence) — code evidence at clay-base/apps/cron/src/audiences/salesforce/exportAudiencesToSalesforce.ts:47-62 (toggle gates all writes before field-level evaluation) and scheduleExports.ts:31-45 (24h per-workspace cadence with deterministic workspace offset)

Uncertainties

None. Both product-behavior claims verified PASS by the verifier sub-agent. Human admin (Peter Johnston) confirmed the answer in the Intercom conversation and customer confirmed the fix worked.

Related observations

Multiple other open PRs touch docs/audiences.md (PRs #1485, #1507, #1528, #1547, #1550, #1558, #1569, #1582, #1585, #1587, #1605) — none of them cover the Export sync toggle as a prerequisite or the "mapped fields not syncing" FAQ. This change is materially new and independent of those PRs. Reviewer should be aware of the concurrent edits and reconcile at merge time.

Closes DOC-1221

…sforce write-back

Fixes the gap surfaced by Intercom ticket #215475130065193: customer mapped
fields with Always write rules but saw no data sync because Export sync was
off. The existing doc said data "writes back automatically" with no mention
that the toggle must be enabled first.

Changes:
- Update "Writing back to your CRM" to state Export sync is the master switch
  and add step-by-step instructions for enabling it
- Add FAQ "I've mapped fields to Salesforce but the data isn't syncing — why?"
@linear-code

linear-code Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

DOC-1221

@george-dilthey
george-dilthey marked this pull request as ready for review July 17, 2026 16:58
@george-dilthey
george-dilthey merged commit 4386c74 into main Jul 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant