访问实体读取文件
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
实体读取文件是合作伙伴的广告系列对象的 JSON 表示法。实体读取文件是只读的，不能用于将更改回写到 Google Display &Video 360。如需详细了解如何使用实体读取文件，请与您的客户经理联系，他们可以更详细地讨论您的需求。
请注意，实体读取文件自处理之日起仅可供 60 天。
您可以在文件格式参考文档中查看实体读取文件的格式。
实体读取文件分为两组存储：
- 公共表，其中包含常见的公共数据，例如存储在
gdbm-public 存储分区中的浏览器版本或语言相关信息。
- 私有表格，包含合作伙伴的广告系列、预算和其他私有数据的相关信息。专用表存储在合作伙伴专用存储分区中；例如，如果您的合作伙伴 ID 为 123，则专用表所在的存储分区将为
gdbm-123。
公共表和私有表都位于存储分区内的
entity 子目录中。
如需详细了解如何处理子目录，请参阅
Cloud Storage 对象命名空间。
公共表格会在世界协调时间 (UTC) 凌晨 5 点生成。不公开表以合作伙伴所在时区的时间凌晨 5 点生成（但在极少数情况下可能会出现延迟），并自动、安全地存储在
Google Cloud Storage 中。生成所有公共表和私有表后，系统会生成一个摘要文件。
公共表
gdbm-public/entity/(processing_date).(batch_index).(entity_type).json
| 字段 | 说明 |
|---|
processing_date | Display & Video 360 处理数据的日期，与文件中包含的事件不一定相关。日期格式为 YYYYMMDD（例如 20120320 表示为 2012 年 3 月 20 日）。 |
batch_index |
批次的索引（从零开始）。例如，如果按小时生成，则第一个批次为 0，第二个批次为 1，依此类推。 |
entity_type | 文件类型：SupportedExchange、DataPartner、UniversalSite、GeoLocation、Language、OperatingSystem、Browser、Isp、summary 和 SiteIdToPlacementId.csv。 |
例如，如果您要生成文件名以检索 2013 年 1 月 15 日之后
browser 表的实体读取文件，则该文件的路径将如下所示：
gdbm-public/entity/20130115.0.Browser.json
私享表
gdbm-(partner_id)/entity/(processing_date).(batch_index).(entity_type).json
| 字段 | 说明 |
|---|
partner_id | 您的合作伙伴的数字 ID。 |
processing_date | Display &Video 360 处理数据的日期。此日期不一定与文件中包含的事件相关。日期格式为 YYYYMMDD（例如 20120320 表示 2012 年 3 月 20 日）。这些文件将在合作伙伴所在时区的凌晨 4 点到凌晨 6 点之间生成。 |
batch_index | 批次的索引（从零开始）。目前，此值始终为 0。 |
entity_type | 文件类型：Partner、Advertiser、InsertionOrder、LineItem、Creative、Pixel、InventorySource、UserList、UniversalChannel 和 summary。 |
例如，如果您要生成文件名以检索合作伙伴 123 在 2013 年 4 月 2 日访问
line_item 表的实体读取文件，则您的文件名将如下所示：
gdbm-123/entity/20130402.0.LineItem.json
如未另行说明，那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可，并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情，请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-08-31。
[null,null,["最后更新时间 (UTC)：2025-08-31。"],[[["\u003cp\u003eEntity Read Files (ERF) have been discontinued and users should migrate to the Display & Video 360 API.\u003c/p\u003e\n"],["\u003cp\u003eEntity Read Files provided read-only JSON representations of a partner's campaign data but were not capable of writing back changes.\u003c/p\u003e\n"],["\u003cp\u003eThese files were organized into public tables, containing common data like browser versions, and private tables, containing partner-specific campaign data, within respective Google Cloud Storage buckets.\u003c/p\u003e\n"],["\u003cp\u003ePublic tables were generated daily at 5 AM UTC, while private tables were generated at 5 AM in the partner's timezone and stored with a specific naming convention indicating the processing date, batch index, and entity type.\u003c/p\u003e\n"],["\u003cp\u003eEach public and private table has a \u003ccode\u003eprocessing_date\u003c/code\u003e and \u003ccode\u003ebatch_index\u003c/code\u003e as well as an \u003ccode\u003eentity_type\u003c/code\u003e to indicate what type of data is contained within the table.\u003c/p\u003e\n"]]],[],null,["# Access Entity Read Files\n\n| Entity Read Files have sunset. [Migrate to use the\n| Display \\& Video 360 API.](/display-video/api/guides/how-tos/erf-migration)\n\nEntity Read Files are JSON representations of a partner's campaign objects. Entity Read Files\nare read-only and cannot be used to write-back changes to Google Display \\& Video 360. To learn more about using\nEntity Read Files, contact your account manager, who will be able to discuss your needs in more detail.\n\nNote that Entity Read Files are available only for 60 days from their processing date.\n\nThe format of the entity read files can be viewed in the\n[File Format reference](/bid-manager/guides/entity-read/format-v2).\n\nThe entity read files are stored as two groups: \n\n- Public tables, which contain common public data, such as information about browser versions or languages that are stored in the `gdbm-public` bucket.\n- Private tables, which contain information about the partner's campaigns, budgets, and other private data. Private tables are stored in partner-specific buckets; for example, if your partner ID is 123, the bucket that contained your private tables would be `gdbm-123`.\n\nBoth public and private tables are in an `entity` subdirectory within the bucket. For more information about handling subdirectories, see [Cloud Storage object namespace](/storage/docs/objects#namespace). \nThe public tables are generated at 5AM UTC. The private tables are generated at 5AM in your partner's timezone (although in rare cases there may be delays) and stored automatically and securely in [Google Cloud Storage](/storage). A summary file is generated after all of the public and private tables have been generated. All filenames are case-sensitive.\n\nPublic Tables\n-------------\n\n```\ngdbm-public/entity/(processing_date).(batch_index).(entity_type).json\n```\n\n| Field | Description |\n|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `processing_date` | The date when Display \\& Video 360 processed the data and is not necessarily related to the events contained within the file. Date format is `YYYYMMDD`, for example `20120320` would be March 20, 2012. |\n| `batch_index` | A zero-based index of the batch. For example, if generated hourly the first batch would be `0`, the second batch would be `1`, and so on. |\n| `entity_type` | The type of file: `SupportedExchange`, `DataPartner`, `UniversalSite`, `GeoLocation`, `Language`, `OperatingSystem`, `Browser`, `Isp`, `summary` and `SiteIdToPlacementId.csv`. |\n\nFor example, if you were generating a filename to retrieve the entity read file for the `browser` table from January 15th, 2013, the path to the file would look like \n\n```\ngdbm-public/entity/20130115.0.Browser.json\n```\n\nPrivate Tables\n--------------\n\n```\ngdbm-(partner_id)/entity/(processing_date).(batch_index).(entity_type).json\n```\n\n| Field | Description |\n|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `partner_id` | The numeric ID of your Partner. |\n| `processing_date` | The date when Display \\& Video 360 processed the data. This date is not necessarily related to the events contained within the file. Date format is `YYYYMMDD`, for example `20120320` would be March 20, 2012. The files will be generated between 4AM and 6AM in the Partner's timezone. |\n| `batch_index` | A zero-based index of the batch. Currently this is always 0. |\n| `entity_type` | The type of file: `Partner`, `Advertiser`, `InsertionOrder`, `LineItem`, `Creative`, `Pixel`, `InventorySource`, `UserList`, `UniversalChannel`, and `summary`. |\n\nFor example, if you were generating a file name to retrieve the entity read file for partner 123 accessing the `line_item` table from April 2, 2013, your filename would look something like this: \n\n```\ngdbm-123/entity/20130402.0.LineItem.json\n```"]]
