This is legacy documentation, and may not be complete. To see the latest documentation, if you are a marketer, refer to the Marketers site. If you are a measurement partner, refer to the Measurement Partners site.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-09-18 UTC."],[[["Privacy message types are categorized using unique codes for various scenarios, including touchpoint analysis exclusions, merge row data filtering, and data access budget status."],["Specific codes indicate when data is filtered due to privacy concerns, insufficient user information, or missing merge row specifications."],["Codes also highlight situations where merge rows are added, temporarily unavailable due to privacy, or when outlier users are filtered from analysis."],["Some privacy messages may be temporarily suppressed due to privacy considerations or data unavailability."],["A dedicated code signals when the data access budget is nearing exhaustion."]]],["The core content defines a set of privacy message types, each represented by a unique code. These codes indicate various states related to data filtering, merge rows, and privacy concerns. Key actions include excluding data from touchpoint analysis, filtering data due to user count, adding or suppressing merge rows, and notifying when the data access budget is nearly exhausted. These codes also highlight situations where data or messages are temporarily unavailable for privacy reasons.\n"]]
