Based on the provided information, it seems like you are trying to determine which field is considered your cursor in the context of an incremental sync. In Airbyte, the cursor is the field used to track which records are new or updated since the last sync. The cursor field is specified in the configuration and is used to filter records during the sync process. From the call you provided:

plaintext {{ stream_partition.waba_id }}?fields=product_catalogs,id,country,currency,name,conversation_analytics.start({{ stream_interval.start_time }}).end({{ stream_interval.end_time }}).granularity(MONTHLY).dimensions(["CONVERSATION_CATEGORY","CONVERSATION_TYPE","COUNTRY","PHONE","CONVERSATION_DIRECTION"])

The cursor field is typically a timestamp or an incrementing ID that allows the system to determine which records have changed. In your case, it looks like

conversation_analytics.start({{ stream_interval.start_time }})

and

conversation_analytics.end({{ stream_interval.end_time }})

are being used to filter records based on time intervals. Therefore, the cursor field in your call is likely related to the

start_time

and

end_time

parameters within the

conversation_analytics

field. These parameters are used to define the time range for the incremental sync, which aligns with the concept of a cursor field in Airbyte. For more detailed information on how cursor fields work in Airbyte, you can refer to the [Airbyte documentation on cursors](https://docs.airbyte.com/understanding-airbyte/airbyte-protocol#cursor) and the [logic for resolving the cursor field](https://docs.airbyte.com/understanding-airbyte/airbyte-protocol#logic-for-resolving-the-cursor-field). If you have any further questions or need additional assistance, feel free to ask!