> ## Documentation Index
> Fetch the complete documentation index at: https://docs.metricanic.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Account and timezone

> Keep your account details current and choose the reporting timezone that matches the comparisons you make.

Use **Account** to update your name and business details, set the workspace timezone, and choose whether to receive marketing emails. These settings serve different purposes and save separately.

Set the timezone before comparing daily results with a traffic source. Two reports can contain the same events but assign them to different days when their timezone boundaries differ.

## Update account details

Open **Account**, edit **Name**, **Surname**, **Business**, or **Country**, then click **Save profile**. Your personal name belongs to your user account. Business details belong to the workspace.

**Email** is displayed for identification and is read-only on this page. Editing a business name does not change the sign-in email or create another workspace.

For example, changing **Business** from a temporary project name to your company's name keeps the existing campaigns and account access. It changes the workspace's business details, not campaign ownership or tracking URLs.

## Choose a reporting timezone

In **Timezone**, choose the timezone you want the tracker to use, then click **Save timezone**. Look for **Timezone saved** before leaving the page.

Choose the timezone of the comparison you make most often. If your traffic source reports in a regional timezone, using the same one makes daily totals easier to reconcile. UTC is useful when you want a stable reference across several sources. Regional timezones can shift their UTC offset with daylight saving time.

For example, an event at 00:30 UTC belongs to the previous calendar day in a timezone two hours behind UTC. Changing the timezone can move that event between daily report rows even though the event itself has not changed.

When comparing results, use the same date range and timezone in both systems. An explicit report timezone overrides the default for that request. For API integrations, send `timezone` explicitly to avoid a later account preference change altering your exports. See [Reports and events API](/api-reference/reports-and-events).

<Note>
  Automation rules use UTC hourly buckets. Changing the account timezone does not redefine their
  evaluation windows. Use [Choose a rule schedule](/automation/schedules) when reconciling a rule
  with a report.
</Note>

## Set your email preference

The **Marketing emails** toggle controls optional product updates, launch notes, and marketing messages. It saves immediately, without **Save profile** or **Save timezone**.

If saving fails, the toggle returns to its previous state and shows an error. Check the final state rather than assuming the click saved the preference. This control manages marketing subscription, not your password or API access.

Use [Security](/account/security) for passwords and landing protection, [API keys](/account/api-keys) for software access, and [Subscription](/account/billing) for plan and payment changes.