[[["容易理解","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"]],["上次更新時間：2022-03-31 (世界標準時間)。"],[[["Attribution Reporting API enforces data limits, such as the size of source and trigger data and the number of conversions attributed to a source."],["Event-level reports for clicks and views have varying data constraints and noise application probabilities to protect user privacy."],["Aggregatable reports have limitations on total bucket values, report frequency, and contributions per report, with noise applied during aggregation."],["All report types share limits on destinations, attributions per source, and reporting origins to prevent excessive data collection."],["Reports are sent with varying delays depending on the report type, with options for customization and ad tech optimization."]]],["Attribution Reporting has constraints for data collection. For event-level reports, clicks allow 64-bit `source_event_id`, 3-bit `trigger_data`, and up to 3 attributed conversions; views use 64-bit `source_event_id`, 1-bit `trigger_data`, and 1 conversion. Noise is applied to reports with a randomized response, and there is a 1-hour to 30-day reporting delay. Aggregatable reports have a 65536 total bucket value limit, a maximum of 20 reports per source, and 20 contributions per report. There are also limits on the number of unique destinations, attributions, reporting origins, and trigger registration header size.\n"]]
