{"version":"2.1.280","anchor":"fable-consent-tracking-gains-a-session-consent-key","canonical_anchor":"fable-consent-tracking-gains-a-session-consent-key","heading":"Fable consent tracking gains a session consent key","tier":"internal","area":"Usage & Limits","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/fable-consent-tracking-gains-a-session-consent-key","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Fable consent tracking gains a session consent key\n\nFable's consent tracking now stores a per-session consent key alongside its existing fallback flag\n\n**Unclear.** The finding does not say what Fable is or what user-facing effect, if any, this consent tracking has.\n\n**What**\n\nThe internal component that tracks consent for Fable now keeps a `sessionConsentKey`, exposed through a new `sessionConsentKey()` method. It is reset at the same time as the existing consent fallback flag it already tracked.\n\n**Why**\n\nThis is an internal bookkeeping change to how consent state is tracked per session; it does not describe a new setting or behavior a reader needs to act on.\n\n- Area: Usage & Limits\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}