[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["必要な情報がない","missingTheInformationINeed","thumb-down"],["複雑すぎる / 手順が多すぎる","tooComplicatedTooManySteps","thumb-down"],["最新ではない","outOfDate","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["サンプル / コードに問題がある","samplesCodeIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-08-01 UTC。"],[[["The Google Interactive Media Ads SDK offers two parameters, Google's RDP and IAB's `us_privacy`, for publishers to signal restricted data processing under the CCPA."],["When either RDP or `us_privacy` is used, Google limits its use of certain identifiers and data to support CCPA compliance."],["Publishers can enable restricted data processing on a per-ad-request basis by appending `&rdp=1` or including the `us_privacy` parameter with a compliant value to their ad tag parameters."],["This guide explains how to implement Google's and IAB's signals for restricted data processing within ad requests."]]],["Publishers can use two parameters, `rdp` and `us_privacy`, within the Google Interactive Media Ads SDK to enable restricted data processing (RDP) in compliance with the California Consumer Privacy Act (CCPA). Appending `&rdp=1` to ad tag parameters activates Google's RDP signal. Using the parameter `us_privacy` with an IAB-compliant string like \"1YNN\" similarly triggers RDP. These parameters restrict how Google utilizes unique identifiers and other data. Both can be used together, and publishers decide when RDP supports their compliance plans.\n"]]