Skip to content

Conversation

@francisco
Copy link
Contributor

Changes:

  • Add bullet clarifying that transformations are not supported in device-mode destinations
    Why:
    It's a common assumption among customers and the current warnings lower in the doc are not clear enough.

Transformations _irrevocably_ change the event payloads flowing through Segment and immediately affect either all destinations, or a single downstream destination, depending on your settings.

> **Warning**: Once you apply Transformations, the original tracking payloads are not easily recoverable.
> warning ""
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one might be worth using the error format, since it could be considered data-destructive.

Copy link
Contributor

@sanscontext sanscontext left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One nit, but not stop ship. LGTM!

@sanscontext sanscontext merged commit e240e5b into master Jan 7, 2020
@sanscontext sanscontext deleted the prot_transformations branch January 7, 2020 23:08
bot-docsteam added a commit that referenced this pull request Jul 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants