We are currently migrating a subset of report types from offline to instant reporting. Once a user is migrated, queries.list responses will include existing instant reports. See our blog post for more information.

Access Entity Read Files

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.

The format of the entity read files can be viewed in the File Format reference.

The entity read files are stored as two groups:

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.

Public Tables

gdbm-public/entity/(processing_date).(batch_index).(entity_type).json

Field	Description
`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.
`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

gdbm-public/entity/20130115.0.Browser.json

Private Tables

gdbm-(partner_id)/entity/(processing_date).(batch_index).(entity_type).json

Field	Description
`partner_id`	The numeric ID of your Partner.
`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.
`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:

gdbm-123/entity/20130402.0.LineItem.json