Skip to content

Commit 4e6c081

Browse files
author
markzegarelli
authored
Merge pull request #2220 from segmentio/paulbarkman-patch-1
Update tracking plan timestamp format requirements.
2 parents 1a1a8f6 + 33ed915 commit 4e6c081

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/protocols/tracking-plan/create.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ The Tracking Plan editor is organized as a spreadsheet to help you add new even
3737
| Name | Specify the name of your event or property. |
3838
| Description | Enter a description for your event or property. These descriptions are helpful for both engineers instrumenting Segment and consumers of the data. |
3939
| Status | Specify whether a property is required or optional. You can't require a `.track()` call because Segment is unable to verify when a `.track()` call should be fired. |
40-
| Data Type | Specify the data type of the property. Data type options include `any, array, object, boolean, integer, number, string`. |
40+
| Data Type | Specify the data type of the property. Data type options include `any, array, object, boolean, integer, number, string, Date time`. Note: Date time is required to be in ISO-8601 format |
4141
| Permitted Values | Enter simple regular expressions to validate property values. This works when a property data type is set to `string`. For example, you can add pipe delimited strings to the regex column to generate violations when a property value does not match fall, winter or spring. |
4242

4343
> info ""

0 commit comments

Comments
 (0)