# 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 %}

<figure><img src="https://2018944329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6nRvcVoGY4QrsHN9eWVJ%2Fuploads%2FMnP09egipECAv5EhRXjb%2F1%20(4).png?alt=media&#x26;token=21496ba0-35cf-4fb1-aa46-02dfdbdc504e" alt="define a timezone"><figcaption><p>Define a timezone in which the app will operate</p></figcaption></figure>

<details>

<summary>What happens if I don't set this up?</summary>

❌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.<br>

</details>