Google introduced it has a brand new metadata discipline for its Search Analytics API (for Search Console’s efficiency reviews) that may inform you about incomplete information factors you obtained by the API. Google mentioned, “This discipline gives context in regards to the state of the info, informing you when your request consists of incomplete information factors.” So in case you are requesting recent information, this can present you when the info is from precisely.
Google wrote on LinkedIn, “The 2 values obtainable are first_incomplete_hour and first_incomplete_date.”
Whenever you request latest information (utilizing all or hourly_all for dataState), a few of the rows returned might signify information that’s incomplete, which signifies that the info remains to be being collected and processed. This metadata object helps you establish precisely when this begins and ends.
All dates and occasions supplied on this object are within the America/Los_Angeles time zone.
The precise discipline returned inside this object is dependent upon how you have grouped your information within the request:
(1) first_incomplete_date (string): The primary date for which the info remains to be being collected and processed, offered in YYYY-MM-DD format (ISO-8601 prolonged native date format).
This discipline is populated solely when the request’s dataState is all and information is grouped by date, and the requested date vary incorporates incomplete information factors.
All values after the first_incomplete_date should change noticeably.
(2) first_incomplete_hour (string): The primary hour for which the info remains to be being collected and processed, offered in YYYY-MM-DDThh:mm:ss[+|-]hh:mm format (ISO-8601 prolonged offset date-time format).
This discipline is populated solely when the request’s dataState is hourly_all, and information is grouped by hour and the requested date vary incorporates incomplete information factors.
All values after the first_incomplete_hour should change noticeably.
A bit extra element will be discovered on this technical documentation.
Discussion board dialogue at LinkedIn.
