Remove backend predicate results from audience evaluation - #4174
Merged
tonidero merged 1 commit intoSep 4, 2026
Merged
Conversation
rickvdl
approved these changes
Sep 4, 2026
tonidero
force-pushed
the
toni/remove-backend-predicate-results
branch
from
September 4, 2026 10:55
db19c9e to
4da5db6
Compare
tonidero
marked this pull request as ready for review
September 4, 2026 11:38
The backend is dropping the backend_predicate_results item from the audiences topic, so the client no longer reads it or exposes it to rules. AudiencesConfigProvider returns the audience dictionary from the default blob directly, LocalRulesEvaluator.match and RulesDimensionResolver.snapshot lose their per-evaluation backendValues parameter, and `backend` is no longer a reserved root. The recursive dimension-name check stays, sourced from providers. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
tonidero
force-pushed
the
toni/remove-backend-predicate-results
branch
from
September 4, 2026 11:57
4da5db6 to
3f7e624
Compare
An error occurred while trying to automatically change base from
toni/subscriber-dimensions
to
toni/customer-info-rules-properties
September 4, 2026 12:35
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
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.
Motivation
The backend is dropping the
backend_predicate_resultsitem from theaudiencesremote-config topic, so the SDK no longer needs to read it or expose it to rule evaluation.Note
Medium Risk
Changes how checkpoint and audience rules resolve when predicates still reference
backend.*(those reads are no longer supplied), which can shift match outcomes until dashboard rules are updated.Overview
Aligns the SDK with the backend removing the
backend_predicate_resultsitem from the audiences remote-config topic.Audiences config no longer bundles pre-evaluated backend predicates with the audience blob:
AudiencesSnapshotandgetSnapshot()are gone in favor ofgetAudiences(), which only loads thedefaultaudiences blob under a consistent config generation.Local rules evaluation drops the reserved
backend.*dimension scope—LocalRulesEvaluatorandRulesDimensionResolverno longer acceptbackendValues, and checkpoint audience matching passes only custom variables plus audience predicates. Subscriber dimensions from the customer response remain as root-level names (unchanged).Tests that covered backend predicate matching and metadata parsing were removed or updated to match the slimmer API.
Reviewed by Cursor Bugbot for commit 3f7e624. Bugbot is set up for automated code reviews on this repo. Configure here.