> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/time-tracking/clockify/data-overview.md). # Data Overview Clockify provides three report types, each tailored to different reporting needs. All reports include time-tracking data filtered by your specified date range. ## Report types | Report | Description | Best For | | ------------ | ------------------------------------------ | ------------------------------------------- | | **Summary** | Aggregated hours by project, user, or date | Executive dashboards, billing summaries | | **Detailed** | Individual time entries with full context | Payroll, project costing, granular analysis | | **Weekly** | Hours grouped by week | Weekly planning, capacity planning, trends | ## Summary report fields #### Metrics | Field | Description | | ---------------- | ------------------------------------- | | Duration (hours) | Total billable or non-billable hours | | Amount | Billable amount if hourly rate is set | | Count | Number of time entries | #### Dimensions | Field | Description | | --------------- | -------------------------- | | Project | Project name | | User | Team member name | | Date | Entry date | | Billable status | Whether hours are billable | | Task | Task description | ## Detailed report fields #### Metrics | Field | Description | | --------------- | -------------------------------------- | | Duration | Hours for each individual entry | | Billable amount | Amount if the entry is marked billable | | Hourly rate | Rate applied to the entry | #### Dimensions | Field | Description | | ------------- | ------------------------------------------- | | User | Team member who logged time | | Project | Associated project | | Task | Task description | | Description | Notes on the time entry | | Start time | When the entry started | | End time | When the entry ended | | Tags | Any tags applied to the entry | | Billable | Whether the entry is billable | | Cost estimate | Estimated cost if hourly rate is configured | ## Weekly report fields #### Metrics | Field | Description | | -------------- | -------------------------------- | | Hours per week | Total hours logged in each week | | By project | Hours broken down by project | | By user | Hours broken down by team member | #### Dimensions | Field | Description | | --------------- | ------------------ | | Week start date | Monday of the week | | Week end date | Sunday of the week | | Project | Project name | | User | Team member | ## Common metric combinations * **Summary + Project dimension** — Track hours and costs by project for billing or capacity planning * **Detailed + User + Date dimensions** — Audit individual time entries for payroll or compliance * **Weekly + User dimension** — Monitor team capacity week-over-week * **Summary + Billable status** — Separate billable from non-billable hours for invoicing ## Use cases by role {% tabs %} {% tab title="Project Managers" %} Use **Weekly** or **Summary** reports grouped by project to track project progress, resource allocation, and budget consumption. Join multiple projects to compare performance across your portfolio. {% endtab %} {% tab title="Finance & Accounting" %} Pull **Detailed** reports to ensure accurate payroll and billing. Filter by date range to match accounting periods. Export to BigQuery for cost analysis and revenue recognition. {% endtab %} {% tab title="HR & Operations" %} Use **Summary** reports by user to monitor team capacity, workload distribution, and utilization rates. Schedule daily or weekly refreshes to track trends over time. {% endtab %} {% tab title="Billing & Invoicing" %} Query **Summary** or **Detailed** reports filtered by billable status and project to generate invoices automatically. Join with rates to calculate billable amounts for clients. {% endtab %} {% endtabs %} ## Platform-specific notes * **Date ranges default to one month** — If you set a start date but no end date, Coupler.io will pull data for one month from the start date * **Macros are supported** — Use dynamic date ranges like `{{lastweekstart}}`, `{{thisyearstart}}`, or `{{30daysago}}` for recurring imports * **No built-in filtering by user or project** — Use Google Sheets formulas or post-import transformations in your destination to filter by specific users or projects * **Time defaults to midnight (00:00)** — All dates are treated as 00:00 unless you manually adjust * **Workspace admin required** — Only workspace administrators can retrieve the Workspace ID from settings --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.coupler.io/sources/category/time-tracking/clockify/data-overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.