Honestly, I don't think our approach is ideal but I don't have a better one in mind. We look back a rolling 7 days on most mornings and look back 30 days on Saturdays, the idea being that forms shouldn't be changed more than a month back. Going back 30 days definitely picks up a ton of records without a change but it's the only way to ensure we get them all, even if users have to wait for the weekend to pick up those changes. The notification service theoretically solves for that, but that process really feels like overkill for a data warehouse use case. I think Genesys would recommend you turn on rescores on all your forms, and that would ensure any rescores create a new evalID, the only downside for us being that if the rescore happens in a new month all of the dates except the call date point to the new month.
------------------------------
Benjamin Wyatt
------------------------------
Original Message:
Sent: 09-05-2025 09:55
From: Mark Spooner
Subject: Getting a delta from the Evaluations API
Hi Benjamin,
Many thanks for your response above.
I was wondering if you could elaborate a bit more on how you're ensuring you pick up deltas?
I tried the above but I couldn't seem to pick up known changes.
Many thanks
------------------------------
Mark Spooner
------------------------------
Original Message:
Sent: 07-18-2025 11:20
From: Benjamin Wyatt
Subject: Getting a delta from the Evaluations API
My org's approach is to hit /api/v2/analytics/evaluations/aggregates/query grouping by conversation ID and using the eventTime alternative time phrase. Then we loop through the conversations using /api/v2/quality/evaluations/query targeting the conversation ID.
Frankly, I don't think Genesys truly understands the use case for extracting all changes to evaluations daily. They have pushed me to use the notification service, which seems problematic in the event of downtime, but maybe it could work for you.
------------------------------
Benjamin Wyatt
Sr. Metrics Reporting Analyst