Using Transformations in cloud mode

Use transformations with cloud mode destinations.

When you add a transformation and connect it to a destination, RudderStack does the following:

  1. Tracks and collects events at the source.
  2. Applies the user transformation logic to your events.
  3. Transforms the events in the destination-specific format. This is done internally and requires no user intervention.
  4. Forwards the transformed events to your destination.
Transformations workflow

Applying transformation on a batch of events

You can perform any aggregation or roll-up operation on a batch of events using the transformBatch function instead of transformEvent:


To ensure event ordering when using the transformBatch function, make sure you pass the messageId from the input event to the output event. Without the messageId, RudderStack does not guarantee event ordering.

It is highly recommended to use transformEvent as much as possible, as it ensures event ordering.


The transformation fails if the following memory and time limits are exceeded:

Memory limit128 MB
Execution time limit4 seconds

Questions? Contact us by email or on Slack