Skip to content

Call Duration Field Semantics

Use the per-call call-log tables for call-length buckets and the participant-daily activity tables for daily talk-time totals.

Field map

Table Field Grain Meaning Units
ANALYTICS_DB.ANALYTICS.CALL_LOGS TALK_TIME_SECONDS one row per call Recorded billable talk duration for that call in the curated recent call log seconds
ANALYTICS_DB.ANALYTICS.CALL_LOGS_FULL_HISTORY TALK_TIME_CORRECTED one row per call Recorded billable talk duration for that call in the full-history call log seconds
ANALYTICS_DB.ANALYTICS.PARTICIPANT_DAILY_ACTIVITY TALK_TIME_SECONDS one row per participant device per day Daily sum of recorded talk duration across that participant's calls for the day seconds
ANALYTICS_DB.ANALYTICS.PARTICIPANT_DAILY_ACTIVITY_FULL_HISTORY TALK_TIME_SECONDS one row per participant device per day Full-history version of the same daily summed talk duration metric seconds

Interpretation

  • CALL_LOGS and CALL_LOGS_FULL_HISTORY are the right sources for per-call duration bucketing.
  • PARTICIPANT_DAILY_ACTIVITY and PARTICIPANT_DAILY_ACTIVITY_FULL_HISTORY store daily aggregates. Their TALK_TIME_SECONDS fields are not single-call durations and should not be bucketed into call-length tiers.
  • Convert participant-daily TALK_TIME_SECONDS values explicitly when reporting minutes or hours. For example, hours = TALK_TIME_SECONDS / 3600.0.

NULL handling

For per-call duration analysis, treat NULL duration as no recorded talk time and either: - exclude those rows from the duration buckets, or - report them as a separate no recorded talk time category.

In the referenced CALL_LOGS duration analysis, NULL TALK_TIME_SECONDS rows aligned with unanswered calls rather than long calls, so allowing NULL to fall into an ELSE bucket will overstate long-call counts.

Source selection

  • Use CALL_LOGS for recent curated Asterar call data.
  • Use CALL_LOGS_FULL_HISTORY when the question needs full historical coverage or includes very short calls.
  • Use the participant-daily activity tables when the question is about per-device daily usage totals, not individual call lengths.