Skip to content

Add additional info regarding timestamp fields #4456

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 23, 2023

Conversation

spencerattick
Copy link
Contributor

Proposed changes

Added a note on Iterable's date field in our document on Iterable destination. Iterable has a specific date format that must be used to segment a field by date. Thus, Segment converts ISO strings to UTC before sending it to iterable.

We have had tickets on this issue where a customer is confused as why the timestamp is getting converted to UTC despite sending the local time.

Merge timing

ASAP is fine

Added a note on Iterable's date field in our document on Iterable destination. Iterable has a specific date format that must be used to segment a field by date. Thus, Segment converts ISO strings to UTC before sending it to iterable.

We have had tickets on this issue where a customer is confused as why the timestamp is getting converted to UTC despite sending the local time.
@markzegarelli markzegarelli enabled auto-merge (squash) March 23, 2023 16:16
@markzegarelli markzegarelli merged commit 1d34809 into develop Mar 23, 2023
@markzegarelli markzegarelli deleted the spencerattick-patch-1 branch March 23, 2023 16:17
@github-actions
Copy link
Contributor

Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants