conversation_agent_assigned which has interaction_id
message_sent which has both
and classic which has interaction_id
my issue is the interaction_id in classic is like the interaction_raw_id in message_sent
and my interaction_id in conversation_agent_assigned is like interaction_id in message sent
but there is no link between conversation_agent_assigned and classic
there is through message_sent but i cannot rely soley on that if i want to get assignment and interaction data where there are no messages sent
Best answer by srikanthkarunakaran
Hi @arwaaboulella :
Thanks for your query. You've observed correctly — the interaction_id in the classic report behaves like interaction_raw_id, while conversation_agent_assigned uses the higher-level interaction_id. The message_sent report acts as a bridge between them.
However, when there are no messages, that bridge breaks, making it difficult to join assignment data with classic interaction logs.
To address this, we recommend:
Using the conversation APIs (GET /conversations/{id}) which return assignment and metadata even without messages.
If available, relying on conversation_id instead of interaction_id, as it's more consistent across APIs.
As a last resort, correlating events using user_id and timestamp if no message data exists.
Let us know if you'd like help constructing a query based on this approach.
Thanks for your query. You've observed correctly — the interaction_id in the classic report behaves like interaction_raw_id, while conversation_agent_assigned uses the higher-level interaction_id. The message_sent report acts as a bridge between them.
However, when there are no messages, that bridge breaks, making it difficult to join assignment data with classic interaction logs.
To address this, we recommend:
Using the conversation APIs (GET /conversations/{id}) which return assignment and metadata even without messages.
If available, relying on conversation_id instead of interaction_id, as it's more consistent across APIs.
As a last resort, correlating events using user_id and timestamp if no message data exists.
Let us know if you'd like help constructing a query based on this approach.
