docs(audiences): add archive cross-reference for Salesforce-deleted records - #2348
Open
george-dilthey wants to merge 2 commits into
Open
docs(audiences): add archive cross-reference for Salesforce-deleted records#2348george-dilthey wants to merge 2 commits into
george-dilthey wants to merge 2 commits into
Conversation
…ecords When records are hard-deleted in Salesforce, they are tagged "Deleted in source" during the next weekly full sync but remain in the audience count until explicitly archived. The Salesforce "Deleted records" section now cross-references the archive path (filter by Sync status → Deleted in source → Archive records) so customers know how to reduce their audience count, mirroring the equivalent guidance already present in the Snowflake section.
Contributor
george-dilthey
marked this pull request as ready for review
August 26, 2026 21:31
…ections The previous commit accidentally dropped 87 lines from the end of the file (FAQ sections 'When two sources have conflicting values', 'Will two records automatically merge', 'Does syncing my CRM cost credits', 'Does Find Companies/People cost credits', and the entire Best practices section). This commit restores all of that content while keeping the intended one-sentence addition in the Salesforce Deleted records paragraph.
This was referenced Aug 27, 2026
Open
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Extended one sentence in
docs/audiences.mdin the Salesforce "Deleted records" section to cross-reference how to archive records already tagged Deleted in source in order to reduce the audience count. The Snowflake section already had an equivalent cross-reference; the Salesforce section was missing it.Net diff: +1 sentence appended to the existing "Deleted records" paragraph; all other content unchanged.
Why
Intercom conversation
215475624610966(Pave Enterprise customer, GTM Engineer Ethan Lin) reported that deleting ~7k accounts in Salesforce didn't reduce their Clay Audiences count from 62k to 55k. Support agent Ryan Phung correctly explained the "Deleted in source" tagging behavior and weekly full sync, but also incorrectly advised that clicking "Save and Review" would force an early full sync.Research confirmed:
apps/api/v3/audiences/services/audiences-imports.service.ts:2106–2125(verifier FAIL on this claim)."To clean up these records, see [How do I archive records...]"); Salesforce didn't.Source link(s)
apps/api/v3/audiences/services/audiences-imports.service.ts:2106–2125—startAsyncBigSourceSynconly called whenisSyncBeingReEnabledlibs/shared/src/audiences/import-types.ts:17— UI label is "Deleted in source" (not "Deleted from Source" as the support agent wrote)services/big-source-sync/src/services/big-source-sync-service.ts:60—FULL_SYNC_INTERVAL_MS = 7 * 24 * 60 * 60 * 1000Uncertainties
None. The change only adds a cross-reference to an already-documented procedure (archive via segment filter). All three product-behavior claims verified against code.
Related observations
libs/shared/src/audiences/import-types.ts:17). This is a support training gap, not a docs gap (the docs already use the correct label throughout).docs/audiences.md(PRs docs(audiences): document how to pause or stop a workflow #2179, docs(audiences): document Salesforce one-connection limit and Incomplete status #2184, docs(audiences): add Clay table import via Add data sidebar wizard #2192, docs(audiences): document signal date limitation and add FAQ #2195, docs(audiences): explain that archived source tables remain in Origin source filter #2202, docs(audiences): explain signal vs bulk-enrichment relationship and fix auto-enrich timing #2203, docs(audiences): cover archived workbook behavior in Origin source filter FAQ #2204, docs(audiences): explain why Audiences fields have values when CRM fields are blank #2210, docs(audiences): explain Clay-prefixed auto-populated fields and fix export credits FAQ #2215, docs(audiences): clarify Find People destination when using Audience as Target companies #2224, docs(audiences): add concrete use-case guidance to Audiences vs. Tables FAQ #2225, docs(audiences): document Enhanced Matching skip logic and hashed email output fields #2231, docs(audiences): document Enhanced Matching skip logic and hashed email output fields #2232, docs(audiences): document Update segment record as admin-only and clarify permission error #2245, docs(clay-ads): add EEA consent, platform fields, delete-recreate behavior, match rate clarification #2251, docs(audiences): note that HubSpot sync time of day is not shown in the UI #2261, docs(audiences): add CRM and warehouse sync cadence anchor sections #2272, docs(audiences): add FAQ for fixing existing duplicates, fix Import Record Matching scope #2280, docs(audiences): rewrite Clay table import section and fix Upsert action name #2288, docs(audiences): restructure Clay table section and rename Upsert/Update Audiences Record actions #2291, docs(audiences): document Salesforce SOQL import for Enterprise customers #2295, docs(audiences): add FAQ for time-gated audience segment membership #2303, docs(audiences): add FAQ for Salesforce duplicate company records #2305, docs(audiences): add common HubSpot contact and company field examples #2321, docs(audiences): expand field mapping intent best practice to cover SFDC import sync path #2323, docs(audiences): clarify legacy plan access and add why-not-visible FAQ #2345) were reviewed — none add the Salesforce deletion count cleanup cross-reference this PR introduces.Closes DOC-2103