{"version":"2.1.224","anchor":"remote-settings-responses-carry-the-identity-that-fetched-th","canonical_anchor":"remote-settings-responses-carry-the-identity-that-fetched-th","heading":"Remote settings responses carry the identity that fetched them","tier":"internal","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/remote-settings-responses-carry-the-identity-that-fetched-th","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Remote settings responses carry the identity that fetched them\n\nRecorded consent is now attributed to the identity that actually fetched the remote settings.\n\n**What**\n\nThe remote settings fetcher now returns the identity used for the request on every path, including a cached 304, an empty 204 or 404, a parsed settings body and the caught-404 fallback. The caller hands it to the consent-recording step, so a recorded consent is attributed to the identity that actually fetched the settings.\n\n**Evidence**\n\n`consentIdentity`\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}