Skip to content

Commit 42e41f8

Browse files
authored
chore: add detail on timestamp vs created_at
1 parent c6f332e commit 42e41f8

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

contents/docs/data/events.mdx

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -120,6 +120,16 @@ Below is a list of some of the properties that PostHog captures by default in cl
120120
| Plugins Deferred | `$plugins_deferred` | `['plugin4']` |
121121
| IP Address | `$ip` | `192.168.1.1` |
122122

123+
### Different timestamp properties
124+
125+
An event has 2 `DATETIME` type fields - `timestamp` and `created_at`.
126+
127+
The `timestamp` field is the time at which your app or website has made the SDK call to capture the event. It defaults to `now()`, unless specified on the SDK call.
128+
129+
The `created_at` field is the time at which our server received the event and started processing it.
130+
131+
Generally, work with and build insights and queries with `timestamp` and only reach for `created_at` if you're investigating the difference between the two.
132+
123133
## Managing event definitions
124134

125135
On the [events management page](https://us.posthog.com/data-management/events), you can edit event tags and descriptions. These show up when searching for events throughout PostHog and provide more context about the purpose of the event.

0 commit comments

Comments
 (0)