When a GBP is subscribed to Google's Pub/Sub in LocalClarity, reviews are brought into the platform as soon as they are processed by Google. Typically, that means after a review is posted on Google, it then shows up in LocalClarity between 10 seconds on the fast end, and 10 minutes on the longest end. What happens if you perform a sync after a review is left in Google, but before it is brought into LocalClarity? Well, it depends, here are some scenarios:

If the review is for a location unaffiliated with any Auto Response campaign, Automation, or Report, then nothing is affected. The review is simply brought in a little bit faster than the Pub/Sub method. The Pub/Sub checks for duplicates, so the review won't be brought in again.

If the review is for a location associated with an Auto Response campaign, that review will not be responded to by the campaign.  This is done as a precaution. Think about the first time you run a sync for all locations in a Profile, you wouldn't want all of those "new" reviews responded to at once.

If the review is for a location associated with an Automation or Real Time report, that will not trigger in this case. Real Time reports are only through Pub/Sub or daily API syncs. Manual syncs that outpace Pub/Sub delivery will not be triggered in the report.

In summary, every time you run a manual sync for a card or a location, there is a very slight chance that this sync will occur in the small gap between the review being left on Google, and being brought into LocalClarity by the Pub/Sub. If a client reports a review or two being missed by Auto Response or a Real-Time report, the first thing to check would be the Sync Schedule, to see if any manual syncs were run for that Profile.

‍