AdWords is now Google Ads. Our new name reflects the full range of advertising options we offer across Search, Display, YouTube, and more. Learn more

Ads
2K members online now
2K members online now
For questions related to Google Shopping and Merchant Center. Learn to optimize your Shopping ads
Guide Me
star_border
Reply

Few issues with IDs re-processed feed?

Visitor ✭ ✭ ✭
# 1
Visitor ✭ ✭ ✭

Hi All,

 

Had a few issues with IDs which are resolved my questions are - 

 

- When I update data in the feed IE updated IDs is it better to - Fetch Now or Re-process Feed?

- If I fetch now how long does it take to process and show on Diagnostics?

If I Re-processed feed  how long does it take to process and show on Diagnostics?

 

I did it about 1 hour ago and I still have the same errors showing as before in diagnostics 

 

Thanks in advance for your help.

1 Expert replyverified_user
1 ACCEPTED SOLUTION

Accepted Solutions
Marked as Best Answer.
Solution
Accepted by topic author Matthew E
January

Few issues with IDs re-processed feed?

[ Edited ]
Top Contributor
# 2
Top Contributor

(a) fetch-now;
(b) 72-hours or more;
(c) 72-hours or more;

re-process does not read any new data --
re-process reuses old, existing, cached data;
only fetch-now actually fetches new data
from the feed-source (spreadsheet, etc.).

 

re-process is mainly to help with optional

supplemental-feeds and feed-rules -- not

for normal fetches/re-uploads/re-submits

of changes, additions, or deletions from

the target-country's primary-feed.

after a feed has been fetched, a best-practice is to carefully inspect
any feed-processing-issues, by clicking on the feed's name, under

the products-feeds-tab:
https://merchants.google.com/mc/products/sources

then -- rather than the diagnostics-tab -- carefully inspect the individual
item-status, by inspecting the products-list's status-column and by clicking
on the items' title, under the products-list-tab:
https://merchants.google.com/mc/items

products-feeds/feed-processing issues are reported immediately after processing;
typically a few minutes or hours after a re-fetch (re-upload), depending on the
inventory size.

products-list/individual-item issues are usually reported a few hours or so
after all items have been fully processed -- depending on the inventory size,
the status of the primary-feed, and other factors.

a best-practice is to use a mix of both letters and numbers for id -- e.g.
abc123
and never, never, change the id of a physical-inventory item, once assigned.

all items are tracked by id.

any issues with id's can trigger a re-inspection by a person at
google, which can sometimes take an additional 72-hours or so;

changed id values are assumed to be new inventory items.

the diagnostics-tab is mainly to help diagnose long-term, more pervasive issues,
by carefully analyzing a few example items, locating a root-cause, and applying
a long-term fix, to all items, so that the issue will never, ever, reoccur for any
items in inventory -- not just the few flagged-example items.

the diagnostics-tab is typically updated after google has fully processed
a feed, all items, crawled the website, crawled the images, inspected the
account and feeds, and flagged a few example items to inspect.

the diagnostics-tab rarely reports all issues --
and should likely not be used with that assumption;

the items reported are more the few-bad-apples that

may spoil the entire bunch.

 

the diagnostics-tab keeps issues as a historic record, to

help with long-term fixes; issues may remain for 30-days,

and permanent suspension-flags remain indefinitely,

 

too many, too frequent, or any severe issue, can

trigger a suspension from the program, at any time.

 

 

View solution in original post

Marked as Best Answer.
Solution
Accepted by topic author Matthew E
January

Few issues with IDs re-processed feed?

[ Edited ]
Top Contributor
# 2
Top Contributor

(a) fetch-now;
(b) 72-hours or more;
(c) 72-hours or more;

re-process does not read any new data --
re-process reuses old, existing, cached data;
only fetch-now actually fetches new data
from the feed-source (spreadsheet, etc.).

 

re-process is mainly to help with optional

supplemental-feeds and feed-rules -- not

for normal fetches/re-uploads/re-submits

of changes, additions, or deletions from

the target-country's primary-feed.

after a feed has been fetched, a best-practice is to carefully inspect
any feed-processing-issues, by clicking on the feed's name, under

the products-feeds-tab:
https://merchants.google.com/mc/products/sources

then -- rather than the diagnostics-tab -- carefully inspect the individual
item-status, by inspecting the products-list's status-column and by clicking
on the items' title, under the products-list-tab:
https://merchants.google.com/mc/items

products-feeds/feed-processing issues are reported immediately after processing;
typically a few minutes or hours after a re-fetch (re-upload), depending on the
inventory size.

products-list/individual-item issues are usually reported a few hours or so
after all items have been fully processed -- depending on the inventory size,
the status of the primary-feed, and other factors.

a best-practice is to use a mix of both letters and numbers for id -- e.g.
abc123
and never, never, change the id of a physical-inventory item, once assigned.

all items are tracked by id.

any issues with id's can trigger a re-inspection by a person at
google, which can sometimes take an additional 72-hours or so;

changed id values are assumed to be new inventory items.

the diagnostics-tab is mainly to help diagnose long-term, more pervasive issues,
by carefully analyzing a few example items, locating a root-cause, and applying
a long-term fix, to all items, so that the issue will never, ever, reoccur for any
items in inventory -- not just the few flagged-example items.

the diagnostics-tab is typically updated after google has fully processed
a feed, all items, crawled the website, crawled the images, inspected the
account and feeds, and flagged a few example items to inspect.

the diagnostics-tab rarely reports all issues --
and should likely not be used with that assumption;

the items reported are more the few-bad-apples that

may spoil the entire bunch.

 

the diagnostics-tab keeps issues as a historic record, to

help with long-term fixes; issues may remain for 30-days,

and permanent suspension-flags remain indefinitely,

 

too many, too frequent, or any severe issue, can

trigger a suspension from the program, at any time.

 

 

Few issues with IDs re-processed feed?

Visitor ✭ ✭ ✭
# 3
Visitor ✭ ✭ ✭

Thank you for the answer and more understanding that just what I needed Smiley Happy