[[["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."],[[["This documentation details privacy message types, represented by unique codes, used for communicating specific privacy-related events or statuses."],["These codes cover various scenarios, including touchpoint analysis exclusions, data filtering in merge operations, and merge row handling."],["Specific codes indicate when data is unavailable due to privacy considerations or when data access budgets are nearing exhaustion."],["Codes like `MERGE_ROW_ADDED` and `MERGE_ROW_TEMPORARILY_UNAVAILABLE` signal merge row status during data processing."]]],["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"]]