Stay organized with collections
Save and categorize content based on your preferences.
Entity Read Files are JSON representations of a partner's campaign objects. Entity Read Files
are read-only and cannot be used to write-back changes to Google Display & Video 360. To learn more about using
Entity Read Files, contact your account manager, who will be able to discuss your needs in more detail.
Note that Entity Read Files are available only for 60 days from their processing date.
Public tables, which contain common public data, such as information about browser versions
or languages that are stored in the gdbm-public bucket.
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.
Both public and private tables are in an entity subdirectory within the bucket.
For more information about handling subdirectories, see
Cloud Storage object namespace.
The 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. A summary file is generated after
all of the public and private tables have been generated.
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.
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.
entity_type
The type of file: SupportedExchange,
DataPartner, UniversalSite,
GeoLocation, Language, OperatingSystem, Browser,
Isp, summary and SiteIdToPlacementId.csv.
For 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
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.
batch_index
A zero-based index of the batch. Currently this is always 0.
entity_type
The type of file: Partner, Advertiser, InsertionOrder, LineItem, Creative, Pixel, InventorySource, UserList, UniversalChannel, and summary.
For 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:
[[["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 2025-05-07 UTC."],[[["\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,["| 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```\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```\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```"]]
