Join the waitlist

Let us know how we should get in touch with you.

Thank you for your interest! We’re excited to show you what we’re building very soon.

Close
Oops! Something went wrong while submitting the form.

Outbound Integration Changes: Identify Which Filters Can Remove a Record Without Deleting It

Austin Hughes
·
Updated on: November 19, 2026
TL;DR: A record disappearing from an outbound view does not prove it was deleted. RevOps teams should test the connector boundary, stored record, field freshness and downstream eligibility separately. Preserve identifiers, change one approved condition, and verify what happens when the record qualifies again before restoring any live outreach.

Which kind of filter changed?

Identify where the filter runs before deciding what a missing record means. A source connector’s ingestion rule, an audience definition, a table filter and an outreach exclusion can all hide a record from a particular workflow while doing different things to its stored data.

Filter layers and the evidence each requires
LayerQuestion to answerEvidence to retain
CRM connection or ingestionDoes this record remain eligible to enter or update the destination?Exact connector rule and source/destination IDs
Incoming field mappingWhich stored values can change?Read behavior and current values
Audience or segmentDoes the record still match the saved definition?Criteria and matching result
Displayed list viewIs it hidden only by the current view?Same record opened independently of the view
Outreach restrictionCan the person enter or continue the action?Applicable exclusion or policy explanation
Existing automation executionWhat happens to work already started?Execution and enrollment state

Write the acceptance question in terms of the exact connector and object. “Does removing an account from the integration filter delete it?” is still incomplete if the connector imports accounts but a sequence runs on associated people. Name both the source object and each destination record used by the workflow.

Do not infer an ingestion filter merely because the product has a filter builder. In Unify, the filter builder is used across audiences, exclusions, triggers and list views. The surrounding feature determines the effect. Ask the supplier to show an actual connector-level filter if that is the control your team intends to change.

Keep this test separate from deleted-record recovery. The question here is what happens to a record that still exists at the source but no longer meets a selection condition. Restoring a deliberately deleted record introduces identity, retention and recovery behavior that deserves its own acceptance procedure.

Establish identity before changing eligibility

Capture the source ID, destination ID and any related IDs before the transition. A stable reference lets you distinguish a stored record that stopped matching from a different record returned by a search. Avoid using a company display name as the only evidence of identity.

Open the record independently of the filtered surface. Use a supported direct record view or an authorized exact-ID lookup where the product provides one. Record who performed the lookup and what they could access, because an operator’s permissions may explain why one person sees a record and another does not.

Retain the actual field used by the rule, its source and its current value. A destination company attribute and a similarly named CRM field may not be interchangeable. Confirm whether the rule evaluates the CRM record directly through a relationship or the destination’s mapped attribute.

Identify the relationship path as well. A person may qualify because of an associated company or opportunity rather than a field on the person. If the relationship changes, record that separately from a field-value change so the supplier can explain which condition stopped matching.

  • Source record: Object type, stable ID and the current condition value
  • Destination record: Object type, stable ID and independent lookup reference
  • Relationship: The linked company, person or opportunity used by the condition
  • Operator: The role and connection used to inspect each surface
  • Dependency: The audience, list, trigger or active enrollment consuming the record

Prepare a permitted no-send test

Agree on a test environment and prevent the demonstration from contacting a prospect. Inspect which actions are already running before changing the condition. A record can feed more than the visible audience, so review its downstream dependencies with the workflow owner.

For Unify, inspect the Play trigger and its connected actions rather than assuming that removing a match will cancel work already underway. Record whether the workflow acts on a company or person, and distinguish new trigger eligibility from an existing execution.

Choose an authorized record for which the supplier can show the complete path without inventing data. Establish the expected transition before changing anything. The expectation should state which surface should stop including the record and which stored record should remain inspectable, if that is the documented behavior being evaluated.

Do not use a live-send action as a shortcut for proving eligibility. A no-send demonstration can inspect records, match previews and existing state without enrolling a prospect. Where the product cannot isolate the proposed behavior safely, request a vendor demonstration or a documented explanation and leave the observation unresolved.

Assign a restoration owner before the test begins. That person should know the original condition, the original field value and the controls used to hold action. Restoring a filter is not the same as approving outreach, so keep those decisions separate in the test notes.

Observe the record after it stops matching

Inspect the stored destination record first, then inspect its membership and operational state. This order avoids treating absence from a filtered screen as evidence of deletion. Record what is actually visible instead of compressing every outcome into “removed.”

A useful observation can distinguish present and current, present with older values, absent from a particular audience, inaccessible to the test user, or unavailable through the supported record lookup. If the record is not found, ask the supplier to establish the reason rather than declaring that the connector deleted it.

In Unify, an audience’s results change as records meet or stop meeting its criteria. That explains a membership transition, not a claim about deleting the underlying company or person. Review both company and people results when the audience has separate conditions for each.

For a shared segment definition, inspect all its uses before changing it. The definition can affect multiple workflows, including engagement policies. A targeted experiment becomes difficult to interpret if the same edit changes access or eligibility elsewhere in the workspace.

Keep the historical record and current qualification distinct. Your business may need to preserve a person’s previous outreach while excluding them from future activity. The acceptance evidence should show how the product separates those requirements, without assuming a filter change erases history or automatically stops every running workflow.

Check field freshness as its own outcome

Verify whether the destination can still receive relevant updates after the source condition changes. A record that remains searchable may still be stale, while a record outside an audience may continue to update normally. Only connector-specific evidence establishes which behavior applies.

Choose a permitted, non-operational field for a freshness check if the supplier supports that approach. Record the prior value, the authorized change and the destination’s observed value. Avoid changing a lifecycle or ownership field merely to produce a visible update when that field could also trigger outreach or reassign work.

For HubSpot bidirectional syncs in Unify, incoming field mappings determine what values update, and mapping changes reprocess affected records in the background. A field configured to preserve an existing value should not be diagnosed as a failed connector simply because it differs from the CRM.

When evaluating Salesforce, inspect the corresponding field mappings and sync behavior for that connector. Do not carry an observation from the HubSpot connection over to Salesforce, or from a company attribute over to a related opportunity, without checking the actual configured path.

Record observation times, but do not invent a universal synchronization deadline. If a result has not appeared, retain the last-known state and ask the supplier which processing or access evidence is available. “Not observed yet” is more precise than treating every delay as permanent data loss.

Verify downstream eligibility separately from storage

Follow the record into the specific consumer that matters: an audience, a trigger, an exclusion or an enrollment. Storage alone does not establish that an action is permitted. Equally, a changed membership does not establish that an already-created task or active enrollment was canceled.

In Unify, applicable sequence exclusions continue to evaluate active enrollments and can stop matching people after the changed CRM data reaches Unify. Turning an exclusion off does not itself create a new enrollment. Keep that behavior separate from an ordinary list filter that merely narrows what is displayed.

For a user assigned to an engagement policy, the policy’s exclusions replace the sequence ruleset exclusions. Check the actual assigned policy rather than assuming that the exclusions visible in a sequence are the full explanation of that user’s eligibility.

Record each consumer’s result independently. The audience may show the company as no longer matching while a prior enrollment still has a historical record. An account owner may retain visibility while another user loses permission to engage it. Those observations can coexist and should not be forced into one status label.

If the expected restriction is not visible, stop the rollout and inspect the dependency. Confirm that the workflow reads the field you changed, that its relationship is populated and that the intended exclusion is enabled in the relevant policy. Avoid broadening permissions or disabling restrictions simply to make the demonstration pass.

Use a connector filter transition matrix

Record expected behavior before the test and observed behavior afterward. Keep the observation cells blank until evidence exists. Use separate rows for leaving a condition, receiving a later source update and becoming eligible again, because these are different acceptance questions.

Blank connector filter transition matrix
Transition to evaluateSource condition and IDsDestination state and freshnessDownstream eligibilityObserved reentry and evidence
Baseline matching record
Record no longer matches
Permitted source update while excluded
Original condition restored
Downstream eligibility reviewed before action

Attach the configuration reference and the operator’s role to the completed matrix. Include the exact record lookup or report used to observe the destination, rather than only a screenshot of an empty search. When the supplier gives a written explanation, retain it as an expectation and label the practical observation separately.

Use the matrix to make a purchasing decision about your workflow, not to score an entire platform as good or bad. A connector that retains excluded records may fit a team that needs historical context, provided future action is controlled. A team requiring removal from a specific downstream system needs that requirement verified explicitly.

What must be checked when the record qualifies again?

Requalification should not be treated as automatic permission to resume outreach. First confirm identity, current values and applicable restrictions. Then inspect whether the downstream action is a new run, a continuation or a historical record that remains finished.

Unify Play settings control repeat runs of a record. The default automated behavior runs a matching record once; reruns require the configured option and cooldown, and in-progress executions remain suppressed. A record matching the criteria again therefore does not, by itself, prove that a new execution should occur.

For a sequence, inspect the existing enrollment rather than creating another one to test the theory. Removing a person from a sequence preserves enrollment history, and re-entry is governed by the applicable enrollment rules. Do not use a new duplicate record to sidestep a legitimate restriction on the original person.

Check the restoration path with the same operator role used for the original observation. If an administrator can see the record but the intended operator cannot, that is an access question. Workspace roles, record sharing and connected-CRM permissions all matter to what the operator can do.

Keep the restoration record usable

Document the original condition and the exact change that restored eligibility, including who approved it. A restoration note should identify whether only the filter changed or whether a source value, mapping or relationship was also corrected. Those are different interventions and should remain distinguishable when another operator reviews the result.

Retain unresolved observations even when the final preview looks correct. If field freshness was never demonstrated, mark that requirement open. If the destination record remained present but its downstream restriction was not verified, do not describe the whole transition as passed. A bounded result is easier to operate than an unsupported blanket assurance.

Decide whether to proceed, adapt or stop

Proceed only when the team can explain each observed state and assign responsibility for any required manual step. An unresolved connector boundary is a reason to narrow the rollout, not to invent a universal rule about records being deleted or retained.

Filter-change decisions
FindingDecision
Only the displayed view changedConfirm the stored record and intended workflow eligibility separately
Record remains but freshness is unclearHold dependent decisions until update behavior is explained
Restriction did not reach the consuming workflowResolve the field, relationship or policy dependency
Requalification creates unexpected workInspect rerun and enrollment behavior before enabling action
Lookup cannot establish whether the record existsEscalate with the source and destination IDs
Behavior is documented and demonstrated for the required pathRecord the evidence and the operational owner
  • If the buyer’s priority is historical context, test retained record access and history rather than assuming exclusion should delete data
  • If the priority is stopping outreach, verify the actual action restriction and active workflow state
  • If the priority is accurate routing, inspect ownership and relationship freshness before reassignment
  • If multiple connectors feed the record, identify which source controls the field used by the condition
  • If requalification is allowed, document who authorizes the next action and what evidence they review

Explore Unify to review CRM-backed audiences and outreach controls together, then validate the connector transition your workflow depends on.

Frequently asked questions

Does a record disappearing from a filter mean it was deleted?

No. It may no longer match a view, audience or rule while remaining stored. Verify the record independently with the permitted lookup and stable identifier.

Can an excluded record remain stale in the destination?

That is a connector-specific question. Inspect whether updates continue after the source condition changes; do not infer freshness from the record merely being present.

Does an audience change automatically stop an active sequence?

Do not assume that. Verify the action’s applicable exclusions, policy and enrollment state separately from audience membership.

Will a record automatically run again after it qualifies?

Not necessarily. Check the consumer’s re-entry rules. In Unify, Play reruns and sequence enrollment rules are separate controls.

Should we delete and recreate the record to test re-entry?

No. That changes the identity and the question being tested. Preserve the original record and inspect its eligibility and history.

What evidence should we request from a supplier?

Request the exact connector configuration, source and destination IDs, observed stored state, field freshness, downstream eligibility and requalification result in a permitted no-send demonstration.

Glossary

  • Ingestion filter: A selection condition applied at a source-to-destination boundary
  • Membership: Whether a record belongs to the selected result set
  • Freshness: How current the stored value is relative to its intended source
  • Eligibility: Whether the record is permitted to enter or continue a specific action
  • Requalification: Meeting a condition again after previously failing it

Sources