Reuse Saved Groups and find broken targeting references

Saved Group references let you reuse targeting definitions without copying each group's contents into every rule. Enterprise teams can send each group once in an SDK payload, then reference it wherever it is needed.

Configure references and check targeting health

The SDK Connection offers ID Lists only and All Saved Groups formats. The broader format requires a compatible SDK, so check every application consuming the connection before changing it. Updating the connection does not upgrade the SDKs in those applications.

Broken-reference diagnostics help identify targeting that points to missing or invalid groups. For example, if a rule references a group that has been removed, inspect the flagged condition and repair its reference before relying on that rule for a rollout.

Missing references, nested conditions and exclusions can behave differently across payload formats and SDK versions. Review those cases when adopting reference-based targeting rather than assuming every SDK handles them identically.

Getting started

Review the Saved Group reference options, confirm compatible SDK versions across the connection, and select the appropriate format. Check affected targeting and any broken-group health warnings before rolling the change out.