Skip to main content

​
Modify Redirects at the Edge

Transform nodes let you modify the redirect response as it flows through the rule engine. Inject tracking parameters, change the redirect type, or add custom headers — all without changing your destination URL or deploying any server-side code. Transforms accumulate as the rule tree is traversed, so you can chain multiple transforms in a single rule path.

Query Parameters

Inject or override URL parameters on the destination. Add UTM tags, tracking IDs, or dynamic values based on rule context.

Redirect Status

Override the HTTP redirect status code per rule branch. Use 301 for permanent, 302 for temporary, or 307/308 for method-preserving redirects.

Response Headers

Set or append custom HTTP headers on the redirect response. Add cache control, security headers, or custom metadata.

​
Query Parameter Injection

Add or replace URL parameters on the destination URL. Two modes are available: Example: A link to https://store.example.com/product with a set transform for utm_source=qr produces https://store.example.com/product?utm_source=qr on redirect.
Combine query parameter transforms with conditions to automatically tag traffic by source. Route visitors from different channels through different transform nodes to inject the right UTM parameters without building separate links.

​
Redirect Status Override

Override the HTTP status code for a specific rule branch. This lets you use different redirect behaviors for different visitor segments without creating separate links. Example: Use 301 for SEO-critical redirects and 302 for campaign links that may change destination.

​
Response Headers

Set or append custom HTTP headers on the redirect response itself. Useful for cache control, security policies, or passing metadata to downstream systems. Forbidden headers: Set-Cookie, Authorization, Host, and Transfer-Encoding are blocked for security. Header values cannot contain newline characters.

​
Chaining Transforms

Transforms accumulate as the rule engine traverses the tree. Place transform nodes at different points in your rule graph to build up the final redirect:
In this example, German visitors get both the lang=de query parameter and a 301 redirect, while other visitors get lang=en with the default 302.

​
Next Steps

Rule Engine

Understand the full rule engine architecture and compilation pipeline.

A/B Testing

Combine transforms with traffic splits to test different parameter configurations.