Skip to content

Commit

Permalink
Merge pull request #7340 from segmentio/Lfdelossantos-patch-1
Browse files Browse the repository at this point in the history
Fix the wrong version of its/it's
  • Loading branch information
forstisabella authored Dec 18, 2024
2 parents 0792f20 + 3701b73 commit f951037
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion src/connections/storage/warehouses/schema.md
Original file line number Diff line number Diff line change
Expand Up @@ -132,7 +132,7 @@ The table below describes the schema in Segment Warehouses:
| `<source>.pages` | A table with your `page` method calls. This table includes the `properties` you record for pages as top-level columns, for example `<source>.pages.title`. |
| `<source>.screens` | A table with your `screen` method calls. This table includes `properties` you record for screens as top-level columns, for example `<source>.screens.title`. |
| `<source>.tracks` | A table with your `track` method calls. This table includes standardized properties that are all common to all events: `anonymous_id`, `context_*`, `event`, `event_text`, `received_at`, `sent_at`, and `user_id`. This is because every event that you send to Segment has different properties. For querying by the custom properties, use the `<source>.<event>` tables instead. |
| `<source>.<event>` | For `track` calls, each event like `Signed Up` or `Order Completed` also has it's own table (for example. `initech.clocked_in`) with columns for each of the event's distinct `properties` (for example. `initech.clocked_in.time`). |
| `<source>.<event>` | For `track` calls, each event like `Signed Up` or `Order Completed` also has its own table (for example. `initech.clocked_in`) with columns for each of the event's distinct `properties` (for example. `initech.clocked_in.time`). |


## Identifies table
Expand Down

0 comments on commit f951037

Please sign in to comment.