July reviews won't tell you what happened on July trips.

You're preparing a summer campaign, and someone asks what July visitors complained about. You reach for reviewMonth: "JULY" . The answer looks conveniently close.

The Actor filters by submission month, and its date records the submission timestamp. There's no year selector or visit date. Labeling that extract “July visitors” quietly changes the question your report answers.

Which July did you actually select?

The reusable problem is choosing the right event clock. A review submission and a hotel stay represent different events. A month selector can't bridge them.

The review Actor exposes the submission clock because that's what its public review data provides.…