# Define a timezone
{% hint style="info" %}
✅This will tell Two Owls to record your events at the same timezone as the one Facebook uses to report your events, meaning they speak the same time language!
{% endhint %}
Define a timezone in which the app will operate
What happens if I don't set this up?
❌You might see some weird mismatch.
:point\_right:**Event allocated to a date in the past:** Say your Ad Account operates in UTC + 5, and there was a purchase that happened at **1 a.m on June 26 (UTC + 5)**. Two Owls, by default, will record that event in UTC and send Facebook that this event happened at **8 p.m on June 25** (according to UTC).
*Facebook understands this as is, without converting the timezone. That means you won't see that purchase showing up on the 26th in the EM!*\
\
:point\_right:**Events coming from "the future":** In the same manner, some events appear to come from the "future" and Facebook won't accept them. Timezone mismatch is the culprit here.
---
# Agent Instructions: 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:
```
GET https://docs.twoowls.io/getting-started/important-checklists/app-checklist/define-a-timezone.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.