Information about Studio events, including both standard and custom actions (play, pause, and so forth), action duration, and more. Information about video-specific events, including actions (play, pause, and so forth), content IDs, pod positioning, and more. See all video eventsĭata Transfer files are pushed to Ad Manager cloud storage buckets on an hourly basis. We advise polling at regular intervals to check for updates. ![]() ![]() The majority of the data is delivered and available between 5 and 15 hours after the recorded hour, though some delayed events can take up to 8 days after the event occurred. In extremely rare cases, Data Transfer files can be re-published to correct erroneous data.Īd Manager does not deliver data transfer information to third-party servers. In these cases, the re-published files have the string "_corrected" appended to the file name, but the previous versions of the files are not deleted from the bucket. About the data contained in Data Transfer filesĭelays of a few hours are normal, but occasionally Data Transfer files take longer than usual to process. If data is late, it appears in the next hourly batched file with an accurate time stamp. This could mean, for example, that a file has mostly 8 a.m. Timestamps with a scattering of earlier timestamps if processing was delayed. If there is no activity during a given hour, an empty Data Transfer file that only contain header data is posted. If the files for a given hour are missing, use reports in Ad Manager to see whether there were any events during the missing hour. When checking for events during a given hour, keep in mind the date and day boundaries discussed below. If Ad Manager reporting confirms that there were no relevant events during the hour you're checking, there's no need to contact support about the missing data transfer file. The first hourly file for a given day typically contains events from midnight to 1 a.m. Pacific Time, but the event timestamps are in the publisher's network time zone. If, for example, the publisher is set to Eastern Time, they'd see events from 3 a.m. The three hours before that would actually be in the previous day's file. You might therefore have timestamps from a different date than is represented by the file name. Master/companion reporting in Data Transferĭata Transfer files show both master and companion creative impressions but the query tool only counts an impression served for the master/companion creative set (not an impression for each creative) unless information is broken down by master/companion.Always refer to the timestamp on events in the file, not the time the file is posted or name of the file. IsCompanion is “TRUE” for the Companion creative impression. ![]() The CreativeId field contains the individual creative IDs for the Master and Companion creatives and not the Creative Set ID. Discrepancies with Ad Manager reportingīad traffic, or spam data, is periodically removed from Ad Manager reports or API-generated reports.There isn’t an additional field in Data Transfer for Creative Set ID to associate companion impressions to master impressions. Due to the publishing schedule of Data Transfer files, some of this cleanup may not be reflected. This can result in Data Transfer showing slightly more impressions, clicks, or other events. When discrepancies occur, the extent tends to be ~1%. Your CodeServes Data Transfer files might show a higher value than the "Code served count" metric in Ad Manager reports because Data Transfer counts a code serve for every served impression, but reports only count one code serve per request.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |