# Best Practices

## Recommended setup

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Start with a report entity</strong></td><td>The report entities (Events with invitees, Questions and answers, User availability) are pre-joined and ready for analysis. Use these instead of joining raw entities manually unless you need something custom.</td></tr><tr><td><strong>Connect the right account from the start</strong></td><td>Before authorizing, log in to the correct Calendly account in your browser. Connecting the wrong account (personal vs. shared org) is the most common setup mistake and requires creating a new connection to fix.</td></tr><tr><td><strong>Use org-level entities for team reporting</strong></td><td>If you need data across multiple team members, use organization-level entities like Scheduled events for organization rather than pulling each user separately. This saves you from managing multiple data flows.</td></tr></tbody></table>

## Data refresh and scheduling

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Set a meaningful date range for reports</strong></td><td>Report entities (Events, Availability, etc.) require a start and end date. Use the date picker to set a rolling window that matches your reporting cadence — for example, the past 30 days for a monthly review.</td></tr><tr><td><strong>Narrow date ranges for large teams</strong></td><td>If your organization has many users and high booking volume, keep date ranges to 30–90 days to avoid slow or failed runs. Pull historical data separately as a one-time export.</td></tr></tbody></table>

## Performance optimization

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Use Append for multi-user analysis</strong></td><td>To compare scheduling activity across individual users, set up multiple sources using user-level entities and use the Append transformation to combine them into one dataset.</td></tr><tr><td><strong>Join Calendly with ad or CRM data for attribution</strong></td><td>If you're tracking UTM parameters in Calendly bookings, use the Join transformation to match Report: Events with invitees against your Facebook Ads or Google Ads data on campaign name or UTM values.</td></tr></tbody></table>

## Common pitfalls

{% hint style="danger" %}
Don't forget that all Calendly timestamps are in UTC. Skipping timezone conversion in your destination will produce misleading reports — especially for teams spread across multiple time zones.
{% endhint %}

{% columns %}
{% column %}
**Do**

* Log in to the correct Calendly account before connecting
* Use Report entities for most reporting needs
* Filter by status in your destination to separate active and canceled events
* Convert UTC timestamps to your local timezone before presenting data
  {% endcolumn %}

{% column %}
**Don't**

* Expect Contacts data — it's not available in the Calendly API
* Use very wide date ranges on large organizations (performance will suffer)
* Assume UTM fields will be populated — they only appear if links were tagged
* Connect a personal account when you need org-level data
  {% endcolumn %}
  {% endcolumns %}