Genesys Cloud - Developer Community!

 View Only

Sign Up

Question about time interval precision for post_analytics_conversations_details_query

  • 1.  Question about time interval precision for post_analytics_conversations_details_query

    Posted 2 days ago

    I have a question regarding the data retrieval period for the post_analytics_conversations_details_query API in Genesys Cloud.

    I am using the following request body to retrieve daily data, based on the conversation end time (other body parameters omitted):

    "interval": "yyyy-mm-ddT00:00:00/yyyy-mm-ddT23:59:59",
    "segmentFilters": [
      {
        "predicates": [
          {
            "dimension": "conversationEnd",
            "value": "yyyy-mm-ddT00:00:00/yyyy-mm-ddT23:59:59"
          }
        ]
      }
    ]

    My understanding is that the interval is specified only down to seconds. In this case, will conversations that end at times such as 23:59:59.999 be included in the results?
    I am concerned that only conversations ending up to 23:59:59.000 might be included, and those ending in the milliseconds after that might be excluded.

    If that is the case, I assume one workaround would be to set the end of the interval to the next day's 00:00:00. However, this raises a concern that conversations ending exactly at 00:00:00 might be double-counted in both days' queries.

    Could you please clarify:

    1. How the API treats the end of the interval with respect to milliseconds (e.g., is the end time inclusive or exclusive at the millisecond level)?
    2. Whether conversations ending at 23:59:59.xxx are included when I specify .../23:59:59 as the interval end.
    3. The recommended best practice for defining daily intervals (based on conversation end time) to avoid either missing conversations or double-counting them.

    Thank you in advance for your support.

    Best regards,


    #PlatformAPI

    ------------------------------
    Naoki Ono
    ------------------------------