.png%3Falt%3Dmedia%26token%3D9aca9a3b-1884-44ca-8f01-d1c7a5077301)
.png%3Falt%3Dmedia%26token%3D9aca9a3b-1884-44ca-8f01-d1c7a5077301)
⏰
Define a timezone
Ensure there are no discrepancies in Events Manager report
✅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!
.png?alt=media&token=da3b22a5-e03c-445c-811c-9a07436a483d)
Define a timezone in which the app will operate
❌You might see some weird mismatch.
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!
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.
👉
Last modified 2mo ago