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
- 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
entitysubdirectory within the bucket. For more information about handling subdirectories, see How Subdirectories Work.
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
||A zero-based index of the batch. For example, if generated hourly the first batch
would be |
|The type of file: |
browsertable from January 15th, 2013, the path to the file would look like
|The numeric ID of your Partner.|
|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 |
|A zero-based index of the batch. Currently this is always 0.|
|The type of file: |
line_itemtable from April 2, 2013, your filename would look something like this: