RudderStack Docs – RudderStack Features

Releases: TOTP-based Multi-Factor Authentication (MFA)

Wed, 05 Aug 2026 00:00:00 +0000

You can now secure your RudderStack account with an authenticator app. Scan a QR code with Google Authenticator, Microsoft Authenticator, 1Password, Authy, or any other authenticator app, and RudderStack asks for a six-digit code from that app when you sign in. You also get a set of single-use backup codes so you can still get in if you lose your device.

Org Admins can go a step further and require Multi-Factor Authentication (MFA) for everyone in the organization, with a seven-day grace period so no one is locked out without warning.

See the Security Settings guide for full details.

Why authenticator app support?

Until now, SMS was the only second factor available on RudderStack. That works, but it has real limits. Text messages don’t arrive reliably everywhere — international users, roaming, and patchy coverage all cause delays or failures, which turns a security feature into a login blocker. SMS is also the weakest of the common second factors, since a phone number can be hijacked through a SIM-swap attack. Many security teams now require an app-based factor and won’t accept SMS.

Authenticator apps solve both problems. Codes are generated on your device, so nothing has to be delivered over a phone network, and there’s no phone number for an attacker to take over. It’s also what most security teams and questionnaires expect to see.

Key features

Authenticator app (TOTP) setup: Scan a QR code — or enter the key manually — and confirm one code to turn it on. Works with any standard authenticator app.
Backup codes: You get 10 single-use codes when you set up your second factor. They’re your recovery path if you lose your phone, and you can regenerate them if you run low.
Your codes stay protected: The secret that generates your codes is held in a dedicated, hardened secrets vault — never in the RudderStack application database.
Require MFA across your organization: Org Admins can turn on the Require 2FA toggle to mandate MFA for all members. Members who don’t have it yet get a seven-day grace period and an email with their deadline.
Choose your own method: Each user picks their own second factor. If you have both an authenticator app and SMS set up, RudderStack asks for the authenticator app code first — it’s the more secure option — and doesn’t send a text unless you choose Verify with SMS instead.
Audit visibility for admins: MFA setup, sign-in attempts, and backup code use are recorded in your organization’s audit logs, and admins can export a per-member MFA status report for security reviews and compliance evidence.

If your organization signs in through SSO, RudderStack defers to your identity provider — enforce MFA in Okta, Azure AD, or your IdP of choice and RudderStack honors it, so your users aren’t asked for a second code on top.

Get started

Go to Settings > Your Profile > Security in the RudderStack dashboard.
Click Set up next to Authenticator app.
Scan the QR code with your authenticator app, then enter the generated code and click Save.
Save the backup codes you’re shown, then click I’ve saved my codes. You’ll be signed out and asked to sign in again with your new second factor.

Org Admins who want to require MFA for the whole organization can use the Require 2FA toggle in Organization settings.

Resources

See the following guides for detailed instructions on using this feature:

Security Settings: Set up an authenticator app or SMS, and regenerate backup codes
Require 2FA toggle: Require MFA for all organization members
Audit Logs: Review MFA-related activity across your organization
Member Management: Roles and permissions, including who can change organization settings

Screenshots

Security settings in the RudderStack dashboard

Setting up an authenticator app

Single-use backup codes shown after setup

Releases: PagerDuty and incident.io Alert Channels

Wed, 15 Jul 2026 00:00:00 +0000

You can now deliver RudderStack’s Configurable Alerts directly into PagerDuty and incident.io — the two tools engineering teams use to run on-call and incident response — alongside the existing Slack, Microsoft Teams, email, and webhook channels. When a pipeline breaks, the alert lands where your on-call attention already lives instead of getting buried in a channel or inbox.

This adds two new delivery destinations for the alerts RudderStack already detects. It does not change what RudderStack monitors or how alert thresholds work — only where those alerts can be sent.

Not to be confused with the PagerDuty destination

This feature sends RudderStack’s operational health signals out to your incident tooling. It is different to the PagerDuty destination, which sends your event data into PagerDuty.

Why route alerts to your incident tools?

A broken pipeline is a business-critical failure, not a cosmetic one. It can silently drop or corrupt the data feeding your analytics, ML models, and downstream marketing and product decisions — and the damage is often invisible until someone notices the numbers are wrong days later.

The problem is that a Slack message or an email is easy to miss. A page is not.

PagerDuty guarantees the right on-call human is actually notified — loudly, via phone, SMS, or push — and auto-escalates if nobody acknowledges.
incident.io coordinates the response once people are aware, spinning up an incident channel, assigning roles, and auto-capturing a timeline that becomes the postmortem.

Meeting your team where its on-call attention already lives turns a RudderStack failure from a buried notification into a real page. For a platform whose promise is data reliability, that closes a direct trust gap.

What you can route

RudderStack’s existing alert engine already detects the failures that matter most (this set is unchanged):

A destination starts rejecting or failing to receive events (bad credentials, downtime, network errors)
A warehouse sync aborts, or pre-sync processing fails
A transformation starts erroring and dropping events
Event volume drops suspiciously versus the same hour last week
A source violates its Tracking Plan (data arriving in the wrong shape)
A Reverse ETL sync fails partially or fatally
A Profiles run fails

Any of these can now land as a PagerDuty incident (with escalation policies, on-call schedules, and phone/SMS/push paging) or as an incident.io alert (which can trigger an incident channel, role assignment, and an auto-built postmortem timeline).

Key features

PagerDuty routing with real paging and escalation: Route any RudderStack alert into a PagerDuty service so the right on-call engineer is paged and alerts auto-escalate if unacknowledged.
incident.io routing with response coordination: Deliver alerts into incident.io to kick off an incident channel, assign roles, and capture a timeline for the postmortem.
Setup in minutes: Configuration is minimal — for PagerDuty, create a service with an Events API v2 integration and paste the 32-character integration/routing key. For incident.io, create an HTTP alert source and paste the secret API key plus the (non-secret) alert source config ID.
The same guardrails as every channel: Only org admins can configure workspace-level channels; alerts are de-duplicated (at most one notification per resource, per alert type, per channel every 24 hours, so on-call isn’t spammed); you can’t disable your last remaining production channel, so you’re never flying blind; and a test alert button confirms the wiring before you rely on it.

Get started

PagerDuty and incident.io alert channels are available on the RudderStack Growth and Enterprise plans and are configured at the workspace level from your RudderStack dashboard:

Go to Data Governance > Alerts in your RudderStack dashboard.
Choose the PagerDuty or incident.io channel.
For PagerDuty, paste your 32-character Events API v2 integration key. For incident.io, paste your HTTP alert source API key and alert source config ID.
Click the test alert button to confirm the connection, then save.

See the Configurable Alerts guide for full setup instructions for both channels.

For vendor-side context, see PagerDuty’s own Events API v2 documentation and incident.io’s Custom HTTP alert source documentation.

Releases: Rudder CLI

Mon, 29 Jun 2026 00:00:00 +0000

Rudder CLI lets you define, validate, and deploy RudderStack resources from your terminal using YAML files in Git.

Manage Tracking Plans and Data Catalog, SQL models, Event Stream sources, and Transformations with the same review and version-control workflows you use for application code.

Key features

Resources as code: Define events, properties, tracking plan rules, SQL models, sources, and transformations in YAML.
Validate before deploy: Check YAML configurations, SQL syntax, and transformation logic locally before pushing to production.
Bi-directional sync: Create resources from the CLI or import existing workspace assets into Git.
CI/CD ready: Integrate validation and deployment with GitHub Actions.

Get started

Install Rudder CLI and authenticate with a workspace access token.
Choose a workflow for Tracking Plans, SQL models, Event Stream sources, or Transformations.
Validate locally, then apply changes to your workspace.

Resources

Releases: RudderStack Assistant

Mon, 15 Jun 2026 00:00:00 +0000

We are excited to announce the RudderStack Assistant, a browser extension for Chrome and Firefox that transforms how you debug and validate your JavaScript SDK implementation. It provides instant visibility into your RudderStack setup directly in your browser.

Why RudderStack Assistant?

Debugging SDK implementations has traditionally required waiting 1-5 minutes for events to appear in the dashboard, piecing together information from browser’s developer tools, or filing support tickets for complex issues. The RudderStack Assistant eliminates these friction points by providing real-time feedback in under one second.

Key features

Real-time event monitoring: See events the moment they fire with full payload inspection, filtering by event type, and visual status indicators.
SDK health dashboard: Instantly view SDK version, write key, data plane URL, installation type (CDN vs NPM), and CSP compatibility.
Destination and plugin visibility: Monitor device-mode destination status and debug configuration issues without leaving your browser.
SDK injection: Test RudderStack JavaScript SDK on any website without code changes — ideal for evaluation, prototyping, and demos.
One-click debug export: Export comprehensive debug data including SDK state, events, and logs to streamline support communication.

Installation

All data processing occurs locally in your browser. The extension does not transmit captured events or SDK information to external servers.

Get started

Install the extension from the Chrome Web Store or Firefox Add-ons.
Navigate to any website with the RudderStack JavaScript SDK installed.
Open the extension to instantly view your SDK configuration, health status, and real-time events.
Use the Events tab to monitor event payloads as they fire, or the Overview tab to inspect destinations and plugins.
Export debug data with one click to share with your team or RudderStack support.

Resources

See the following guides for detailed instructions on using the extension:

Releases: RudderTyper 2.0

Mon, 08 Jun 2026 00:00:00 +0000

This feature is in Public Beta as part of RudderStack’s Early Access Program, where we work with early users and customers to test new features and get feedback before making them generally available.

We are introducing RudderTyper 2.0, which generates type-safe client bindings from your Tracking Plans for modern SDK languages —TypeScript, Swift, and Kotlin. By generating native code that matches your Tracking Plan’s event definitions, you can catch instrumentation errors at compile time rather than runtime, with full IntelliSense support in your IDE.

RudderTyper 2.0 is packaged into Rudder CLI, which already works with the Tracking Plans and Data Catalog you maintain as code in your Git repositories. This lets you generate and update your typed bindings as part of the same workflow you already use to manage your tracking plans, keeping your instrumentation in sync with your governance definitions.

What’s new

Modern SDK language support: Generate strongly-typed bindings for TypeScript, Swift (iOS), and Kotlin (Android and JVM) that match your Tracking Plan’s event structure.
Compile-time type safety: Validation ensures your tracking code matches your Tracking Plan definitions before your application ships, with autocomplete and type checking in your IDE.
Packaged into Rudder CLI: Generate bindings directly from your Tracking Plans using the same CLI that manages your Data Catalog as code.
Git-native workflow: Works with the Tracking Plans and Data Catalog you already maintain as code in your repositories, so generated bindings stay version-controlled alongside the rest of your instrumentation.
Standard event coverage: Supports all standard RudderStack event types—track, identify, screen, and group.

Get started

Guide	Description
RudderTyper v2	Overview of RudderTyper 2.0, its features, and limitations
RudderTyper v2 Walkthrough Guide	Step-by-step tutorial to generate and use type-safe bindings in your application
RudderTyper v2 Command Reference	Complete reference for RudderTyper v2 CLI commands and parameters

Releases: Rudder AI

Wed, 03 Jun 2026 00:00:00 +0000

Rudder AI is now generally available — an AI agent that helps you monitor, debug, and interact with your RudderStack workspace from Slack using natural language.

Rudder AI operates with read-only workspace access and automatically masks customer PII before data reaches the AI — your team gets faster answers without exposing sensitive values.

See the Rudder AI Overview for full details.

Why Rudder AI?

When something breaks in your pipeline, finding the answer often means clicking through the dashboard, pulling event samples, and cross-checking destination metrics — while the incident is still open. Rudder AI meets your team in Slack and turns those investigations into natural language questions.

You can check event volumes, analyze delivery failures, review tracking plan compliance, inspect transformations, and get product documentation answers without leaving the channel. Because Rudder AI is read-only, it supports investigation and monitoring without changing sources, destinations, or other workspace configuration.

Key features

Monitor pipeline health: Check event volumes, success rates, and delivery metrics across sources and destinations.
Debug issues faster: Analyze failed events and transformation errors with masked PII protection.
Access configuration: View sources, destinations, transformations, and Tracking Plans in your production workspace.
Query documentation: Get AI-powered answers to RudderStack product questions grounded in the docs.
Slack-native workflow: Use Rudder AI in your designated shared Slack channel — responses are visible to the channel, and the assistant does not run in direct messages or other channels.

Get started

Enable access: Contact your RudderStack representative to enable Rudder AI for your workspace.
Open your designated Slack channel: Rudder AI responds only in the shared channel configured for your workspace — not in DMs or other channels.
Ask questions in natural language: Start with monitoring or debugging prompts, for example event volume by source, destinations with delivery failures, or recent configuration changes.
Provide feedback: Use 👍 or 👎 on responses to help improve the assistant.

See Rudder AI Key Capabilities for example questions by use case.

Data privacy and security

Rudder AI uses Amazon Bedrock for AI processing. Your data is never used to train AI models, and conversations are not stored.
Customer PII is automatically masked before reaching the AI. The masking preserves data structure for debugging while protecting actual values.

See Rudder AII Security and Compliance for access controls, workspace isolation, and revocation details.

Resources

Releases: Stream Events to Snowflake Iceberg Tables

Tue, 17 Mar 2026 00:00:00 +0000

RudderStack’s Snowflake Streaming destination now supports Snowflake-managed Apache Iceberg tables. When enabled, your event data streams in real-time into your own cloud storage — S3, GCS, or Azure — in the Iceberg table format.

Snowflake manages the Iceberg metadata catalog and you get the speed of Snowpipe Streaming with the openness and portability of the lakehouse.

See the Snowflake Streaming to Iceberg Tables documentation for full details.

Why Iceberg tables?

Organizations adopting lakehouse architecture want the best of both worlds: the performance and governance of Snowflake with the openness and flexibility of storing data in their own cloud storage. Until now, Snowpipe Streaming wrote exclusively to standard Snowflake tables locked in proprietary storage — forcing a choice between real-time delivery and data portability.

That trade-off disappears with Iceberg table support. Your event data lands in open Parquet format on storage you control, accessible by any engine that reads Iceberg — Spark, Trino, Databricks, Athena — while Snowflake continues to serve as the primary query engine and catalog. You reduce vendor lock-in, gain multi-engine access, and maintain full storage lifecycle control, all without sacrificing delivery speed.

Key features

Near real-time streaming to Iceberg: Events are delivered via Snowpipe Streaming with ~30 second latency directly into Snowflake-managed Iceberg tables — the same low-latency pipeline, now writing to open storage.
Open Parquet storage on your cloud: Data is stored as Parquet files in your external volume (S3, GCS, or Azure). Query it from Snowflake, Spark, Trino, Databricks, Athena, or any Iceberg-compatible engine.
Automatic table creation: RudderStack automatically creates Iceberg tables with the correct catalog, external volume, and base location configuration. No manual DDL required.
Automatic schema evolution: New event properties are detected and columns are added automatically — your Iceberg tables stay in sync with your event schemas as they evolve.
Automatic compaction: Snowflake handles compaction of the underlying Parquet files, keeping query performance optimized without manual maintenance.
All standard event types supported: Track, identify, page, screen, group, and alias events all stream to Iceberg tables.

Get started

Ensure prerequisites are in place: You need a Snowflake account with Iceberg table support and an external volume configured in Snowflake pointing to your cloud storage (S3, GCS, or Azure).
Set up RSA key-pair authentication: Iceberg table support requires key-pair authentication. Password authentication is not supported for this feature.
Enable Iceberg in your Snowflake Streaming destination: Toggle on the Create Iceberg Tables setting in your Snowflake destination configuration.
Specify the external volume name: Specify the name of the external volume you created by following the steps here
Start sending events: RudderStack handles Iceberg table creation, schema evolution, and compaction automatically.

See the How to Configure Snowflake Streaming to Iceberg Tables guide for detailed setup instructions.

How it works

When you enable Iceberg in your Snowflake Streaming destination, RudderStack:

Sends events to Snowflake via the Snowpipe Streaming API
Lets Snowflake handle buffering and flushing rows to Parquet files
Relies on Snowflake to manage the Iceberg metadata and catalog

The following diagram illustrates the high-level data flow:

Known limitations

JSON fields stored as VARCHAR: Snowflake does not yet support the VARIANT data type for Iceberg tables. JSON data is stored as VARCHAR until Snowflake V3 adds VARIANT support.
No USERS table: Streaming mode is append-only and does not support MERGE operations, so the consolidated USERS table is not available.
~30 second minimum latency: This is a Snowflake-imposed constraint for Iceberg table writes.
TIMESTAMP_NTZ(6) instead of TIMESTAMP_TZ: Timestamps do not include timezone information in Iceberg mode.
Immutable Iceberg settings: External volume and Iceberg configuration cannot be changed after table creation.
Key-pair authentication required: Password-based authentication is not supported.

Resources

Screenshots

Releases: P95 Latency Alerts for Event Stream Destinations: General Availability

Fri, 27 Feb 2026 00:00:00 +0000

P95 latency alerts for Event Stream cloud destinations are now Generally Available for all Enterprise customers.

You can now configure P95 latency thresholds for your Event Stream cloud destinations and receive alerts whenever event delivery slows beyond acceptable limits. For example, if you set a P95 latency threshold of 15 minutes and 95% of events aren’t delivered within that window, RudderStack triggers an alert on your configured delivery channels — Slack, email, Microsoft Teams, or a custom webhook.

This helps you catch delivery delays early, troubleshoot proactively, and keep stakeholders informed before issues escalate.

What’s new

Generally available: P95 latency alerts are no longer in beta. They are fully supported and available for all Enterprise customers.
Expanded access: Previously, only Admins could view the P95 latency metric. Now, any user subscribed to P95 latency alerts for a destination can also view its latency metrics directly in the Events tab.

P95 latency alerts apply only to Event Stream destinations connected to sources in cloud mode.

They do not apply to Reverse ETL connections, warehouse destinations, and device mode connections.

See the following guides for more details:

Set up P95 latency alerts: Configure alert thresholds for your destinations
View the P95 latency event metric: View and interpret the P95 latency metric for your destination

Screenshots

Configure P95 latency alerts in the RudderStack dashboard:

View the P95 latency metric for a destination:

View the P95 latency for events coming from a particular source:

Releases: Bot Management

Mon, 23 Feb 2026 00:00:00 +0000

We are excited to announce Bot Management, a data governance feature that detects, flags, and drops bot traffic on web sources before it enters your data pipelines. By identifying and managing bot events early in your data flow, you can significantly improve data quality and reduce unnecessary costs.

Why Bot Management?

Managing bot traffic has traditionally required implementing custom detection logic in downstream systems, leading to inconsistent bot detection across your analytics stack and inflated costs from processing non-human events. Bot Management eliminates these challenges by providing a centralized, reliable filtering layer that standardizes bot detection across your web sources.

Key features

User agent-based detection: Automatically identifies bot events using predefined bot patterns to detect common bots, crawlers, and automated traffic.
Flexible event management: Choose to flag bot events for downstream analysis or drop them entirely at the gateway to prevent unnecessary processing costs.
Workspace and source-level configuration: Set global bot management settings for all web sources or apply custom configurations for individual sources based on your specific requirements.
Real-time bot metrics: Monitor bot event volume patterns at the source level through the source Events view. For more details, see View Bot Event Metrics.
Cost optimization: Drop bot events at the gateway to reduce billable event volume and prevent unnecessary costs across pipelines, data stores, and analytics tools.

Get started

Bot Management is available in all RudderStack paid plans. You can get started with just a couple of clicks — navigate to Govern > Bot Management in your RudderStack dashboard and enable bot detection for your workspace.

See the Bot Management documentation for detailed instructions.

Resources

See the following guides for detailed instructions on using this feature:

Screenshots

Bot management view in the RudderStack dashboard

Bot management global setting

Source-level bot event management

Bot event metrics in the source page

Releases: Cloud Extract End of Support Announcement

Mon, 01 Dec 2025 00:00:00 +0000

After careful consideration and a strategic evaluation of our product portfolio, RudderStack is ending support for Cloud Extract (our ETL offering).

Here’s what you need to know:

End-of-support date: December 1, 2025. Starting from this date, RudderStack will no longer provide support or respond to support tickets for ETL pipelines.
Pipeline shutdown date: January 10, 2026. All ETL pipelines will be turned off on this date. Users will no longer be able to activate or toggle on their pipelines.
Access until shutdown: Current RudderStack Growth and Enterprise customers will retain access to Cloud Extract pipelines until January 10, 2026.

For account-specific details or assistance with transition planning, contact RudderStack Support for the specifics.

Why RudderStack is sunsetting Cloud Extract

RudderStack’s core competencies include event collection (Event Stream), governance (Data Quality and Data Compliance Toolkits), unification (Profiles), and activation (Reverse ETL & Real-time integration).

By focusing on these areas, we are better positioned to continue to innovate and provide the best possible solutions for your data needs.

Reach out to us for any queries.

Releases: Snowflake Streaming Assisted Migration Feature

Tue, 28 Oct 2025 00:00:00 +0000

Migrating from RudderStack’s traditional Snowflake batch destination to the new Snowflake Streaming destination unlocks real-time data ingestion using Snowflake’s Snowpipe Streaming API. However, manually managing this migration — including creating new destinations, reconnecting sources, and coordinating the cutover — can be complex and risky.

With the assisted migration feature, you can now migrate your existing Snowflake pipelines with a guided workflow that handles all the heavy lifting for you. This feature automatically creates and configures your new Snowflake Streaming destination, manages the transition between pipelines, and minimizes duplicate records during the migration process.

Key capabilities

Automated destination setup: RudderStack creates a new Snowflake Streaming destination using your existing batch destination credentials and configuration, preserving your schema and table mappings.
Guided verification: A step-by-step workflow prompts you to verify that events flow correctly through the new Snowflake Streaming pipeline before completing the migration.
Automatic pipeline coordination: The Snowflake batch destination is automatically paused during migration to minimize duplicate records while both pipelines are active.
Final sync trigger: You can trigger a final sync from the batch destination to ensure any events collected during the pause are loaded to your warehouse.
Rollback capability: If any errors occur during setup, you can roll back to your previous state without any data loss.
Deduplication guidance: Receive migration timestamps and documentation to help you deduplicate any records that may have been ingested during the transition.

Why migrate to Snowflake Streaming?

The Snowflake Streaming destination delivers event data to Snowflake in seconds via continuous micro-batches, enabling real-time analytics, alerting, A/B testing, and fresher data for personalization and AI/ML use cases. Because it uses the Snowpipe Streaming API instead of warehouse compute, it maintains the same or lower cost compared to the batch integration while dramatically reducing latency.

Get started

Go to your existing Snowflake batch destination in the RudderStack dashboard.
Look for the Migrate to Snowflake Streaming banner.
Click Proceed to initiate the assisted migration process.

Follow the guided steps to verify your new Snowflake Streaming destination and complete the migration. If needed, reference the provided timestamps to deduplicate records in your target tables.

See the Snowflake Streaming Migration Guide for more information on manual migration options and deduplication queries.

Screenshots

Releases: Conditional Validation Support in Rudder CLI

Wed, 01 Oct 2025 00:00:00 +0000

RudderStack’s Tracking Plans enable data teams to apply type-safe governance to event schemas. While our governance features ensure consistency and predictability, real-world applications often require schemas to adapt based on business context.

With the release of Conditional Validation, you can now define validation rules that dynamically adjust based on discriminator properties. This powerful capability addresses a common challenge — maintaining strict data quality standards while accommodating legitimate variations in your event data structure.

With conditional validation, you can:

Define context-aware validation rules that adapt based on specific property values
Prevent event proliferation by consolidating similar events with varied requirements
Enforce granular validation on custom types that need to behave differently in different scenarios
Maintain data quality without sacrificing flexibility for legitimate business variations

You can leverage conditional validation both on the event schema level and within custom types, and manage everything via workspace configuration files using Rudder CLI.

Use cases

This section provides some examples of using the conditional validation feature.

Event-level conditional validation

Adaptive page tracking: Single Page Viewed event with different required properties based on page type — for example, search term for search pages, product details for product pages, checkout step for checkout pages
Context-aware form submissions: Different required fields based on form type or user journey stage
Dynamic feature usage tracking: Varying property requirements based on feature context or user role

See Event Rule Variants for more details on creating and managing event rule variants in your Tracking Plans using Rudder CLI.

Custom type conditional validation

Regional address formats: Different required fields for US addresses (state + ZIP) vs. UK addresses (postcode) vs. Japanese addresses (prefecture + district)
Manufacturer vs. marketplace products: Require MSRP and Manufacturer ID for direct products, and require Seller ID for marketplace items
Account tier-specific profiles: Different required profile fields for individual vs. business vs. enterprise accounts

See Custom Type Variants for more details on creating and managing custom type variants using Rudder CLI.

How it works

Conditional validation uses discriminator properties to determine which validation rules apply. A discriminator is a required property whose value triggers specific validation cases.

For example, in an ecommerce tracking scenario:

Discriminator property: page_type (enumerated list defined in Data Catalog)
Variant cases:
- When page_type = search_page: Require the search_term property
- When page_type = product: Require the product object property

Result: Same event handles both scenarios with appropriate validation.

Implementation

Conditional validation works at two levels:

Event rule variants

Define variants within your tracking-plans.yaml to create context-aware event validation:

yaml

version: "rudder/v0.1"
kind: "tp"
metadata:
 name: "ecommerce_tracking_plan"
spec:
 id: "ecommerce_tracking_plan"
 display_name: "Ecommerce Store - Tracking Plan"
 description: "Comprehensive tracking plan for the casual apparel e-commerce demo site built with React TypeScript. Captures user behavior across product discovery, cart interactions, and purchase completion for analytics and optimization."
 rules:
 - type: "event_rule"
 id: "page_viewed_rule"
 event:
 $ref: "#/events/ecommerce_events/page_viewed"
 allow_unplanned: false
 properties:
 # Base properties required for all page views
 - $ref: "#/properties/ecommerce_properties/page_type"
 required: true
 - $ref: "#/properties/ecommerce_properties/page_name"
 required: false
 - $ref: "#/properties/ecommerce_properties/page_url"
 required: false

 # Conditional Validation Variants
 variants:
 - type: discriminator
 discriminator: "#/properties/ecommerce_properties/page_type"
 cases:
 - display_name: "Product Detail Page"
 match:
 - "product"
 description: "When user is viewing a specific product page"
 properties:
 - $ref: "#/properties/ecommerce_properties/product"
 required: true

 - display_name: "Search Results Page"
 match:
 - "search"
 description: "When user is on search or category pages"
 properties:
 - $ref: "#/properties/ecommerce_properties/search_term"
 required: true

 # Default case for home and other pages (only page_url required)
 default:
 - $ref: "#/properties/ecommerce_properties/page_url"
 required: true%

Custom type variants

Define variants within your custom-types.yaml to create reusable, context-aware object types:

yaml

version: "rudder/v0.1"
kind: "custom-types"
metadata:
 name: "ecommerce_types"
spec:
 types:
 # Product Type - Consolidates all product-related properties with conditional MSRP validation
 - id: Product_Object
 name: "Product_Object"
 description: "Custom type for product information with conditional manufacturer pricing validation"
 type: "object"
 properties:
 - $ref: "#/properties/ecommerce_properties/product_id"
 required: true
 - $ref: "#/properties/ecommerce_properties/product_sku"
 required: true
 - $ref: "#/properties/ecommerce_properties/product_name"
 required: true
 - $ref: "#/properties/ecommerce_properties/product_category"
 required: true
 - $ref: "#/properties/ecommerce_properties/product_price"
 required: true
 - $ref: "#/properties/ecommerce_properties/manufacturer_pricing"
 required: false
 # Conditional Validation Variants for Product Object
 variants:
 - type: discriminator
 discriminator: "#/properties/ecommerce_properties/manufacturer_pricing"
 cases:
 - display_name: "Product with Manufacturer Pricing"
 match:
 - true
 description: "Products that have manufacturer suggested retail price (MSRP)"
 properties:
 - $ref: "#/properties/ecommerce_properties/product_msrp"
 required: true

Deploy the changes to your workspace

bash

rudder-cli apply -l ~/path_to_tracking_plan_dir

See the Conditional Validation documentation for more details.

Releases: Custom Types Support in Rudder CLI

Thu, 17 Jul 2025 00:00:00 +0000

Building on our recent Custom Types release, you can now define Custom Types directly in your workspace configuration files and deploy them using Rudder CLI. This enhancement brings Custom Types into your existing infrastructure-as-code workflows, enabling you to version control and programmatically manage complex data validation rules.

With workspace config and CLI support, you can now:

Define Custom Types as code: Create a custom-types.yaml file alongside your existing Tracking Plan configurations, enabling version control and collaborative development of data governance rules.
Reference Custom Types in properties: Use Custom Types as property types in your properties.yaml files, eliminating the need to redefine complex validation logic across multiple properties.
Deploy via CLI: Use the rudderstack tp apply command to push Custom Types and their associated properties to your workspace, integrating seamlessly with your existing deployment workflows.

This release complements the existing Data Catalog API and Git-Based Data Catalog and Tracking Plan Management, giving development teams full flexibility in how they manage data governance across their organization.

Get started

Create a workspace config file: Add custom-types.yaml to your Tracking Plan directory alongside your existing configuration files.
Define your Custom Types: Define your custom type rules.
Reference your Custom Types: In your properties.yaml file, you can define a property that references your previously defined custom types.
Validate and Deploy with CLI: Use the Rudder CLI tool to validate the YAML configurations and apply changes to your workspace.

See the Use Custom Data Types in Rudder CLI guide for more details on creating and managing custom types using Rudder CLI.

Sample snippets

Defining custom types in workspace configuration files

yaml

version: "rudder/v0.1"
kind: "custom-types"
metadata:
 name: "ecommerce_types"
spec:
 types:
 # Product Type - Consolidates all product-related properties
 - id: Product_Object
 name: "Product_Object"
 description: "Custom type for product information including ID, SKU, name, category, pricing"
 type: "object"
 properties:
 - $ref: "#/properties/ecommerce_properties/product_id"
 required: true
 - $ref: "#/properties/ecommerce_properties/product_sku"
 required: true
 - $ref: "#/properties/ecommerce_properties/product_name"
 required: true
 - $ref: "#/properties/ecommerce_properties/product_category"
 required: true
 - $ref: "#/properties/ecommerce_properties/product_price"
 required: true
 - $ref: "#/properties/ecommerce_properties/product_msrp"
 required: false

Reference custom types within a property configuration

yaml

version: "rudder/v0.1"
kind: "properties"
metadata:
 name: "ecommerce_properties"
spec:
 properties:
 # Product Custom Type Property
 - id: "product"
 name: "product"
 type: "#/custom-types/ecommerce_types/Product_Object"
 description: "Product information object containing all product details"

Deploy the changes to your workspace

bash

rudder-cli apply -l

Releases: Cursor Column Support for Reverse ETL Syncs

Thu, 15 May 2025 00:00:00 +0000

Previously, RudderStack’s Reverse ETL Upsert mode was diff-based, meaning it compared every column and row to detect changes from your source table in order to determine what records needed to synced. This led to longer sync times and higher warehouse costs, particularly for large tables.

With Cursor Column support, you can leverage a timestamp value checkpoint for the diff. This optimizes Reverse ETL syncs by allowing you to specify a comparable timestamp column (for example, updated_at) to track incremental changes in Upsert mode. RudderStack will then query only records with a cursor value greater than the last checkpoint, avoiding resource-intensive, full-table comparisons.

By reducing the computational load of warehouse queries, this feature lowers operational costs and speeds up syncs, especially for large datasets.

Setup guide

RudderStack does not support migrating existing Reverse ETL connections from upsert mode to cursor mode. You must create a new Reverse ETL connection to use the cursor column feature.

Create a new destination connected to a warehouse table or SQL model as a source.
After adding the destination credentials and mappings, choose Upsert as your sync mode.
Turn on the Cursor Column toggle.
Choose the timestamp column you want to use as the cursor column.
Initiate your first sync.

RudderStack will perform a full sync on the first run.

After the first run, RudderStack will use the cursor column to identify any new or updated records that arrive in the source table and sync those records on any subsequent sync jobs.

See our Cursor Column Support docs for more information on this feature.

Screenshots

Releases: Full Sync Mode Support

Wed, 14 May 2025 00:00:00 +0000

We’re excited to announce Full Sync mode—a new Reverse ETL sync mode that gives you more control over how data flows from your warehouse to various business tools.

Similar to Upsert and Mirror modes, Full Sync mode is configured at the connection level. It ensures that the entire dataset is sent on every sync—this is ideal for teams that already handle change detection or diffs inside the warehouse.

Key details

Full Sync mode is configured when creating a Reverse ETL connection.
RudderStack will send the full model result set on each sync, overwriting or resending all records based on the destination’s behavior.

This mode offers maximum flexibility for advanced teams that prefer to own the sync logic in their warehouse, while still benefiting from RudderStack’s destination coverage and scheduling infrastructure.

When to use Full Sync mode

Warehouse-managed diffs: If you’re using tools like dbt or scheduled jobs to determine which records to send, Full Sync mode lets you send that curated dataset downstream, exactly as it appears in your warehouse.
Destinations with limited support for updates: Some tools or custom endpoints do not handle upserts or partial updates well. Full Sync mode guarantees that the complete table is refreshed every time, reducing downstream inconsistencies.

Learn more about the Full Sync mode in our docs

Screenshots

Releases: Tracking Plan Code Generation

Tue, 06 May 2025 00:00:00 +0000

Event data quality has never been more important, but even for teams that run tight processes, details can get lost in translation. Between the creation of an event schema definition and the instrumentation of the API call to fire the event from the codebase of the website or app, simple mistakes can create big problems downstream.

RudderStack’s new Code Generation (Codegen) feature automatically creates clear code snippets that software engineers can use in their instrumentation. The code snippets ensure property and trait keys are accurate, provide samples for selected data types, and clearly denote whether the key is optional.

The Codegen feature is in Public Beta as part of RudderStack’s Early Access Program, where we work with early users and customers to test new features and get feedback before making them generally available.

Contact the Product team if you have any questions.

As part of this release, we’ve made significant updates to the UI for our schema view and have completely overhauled the schema editing experience, which significantly simplifies schema buildout and updates.

See our Tracking Plan Codegen docs for more information.

Screenshots

Releases: CLI-based Data Governance

Wed, 02 Apr 2025 00:00:00 +0000

We are excited to announce CLI-based data governance workflows in RudderStack. Our new CLI utility and other features make it easy to manage your data catalog and tracking plans as code.

With CLI-based data governance, you can bring the same rigor and process to your data governance workflows that you apply to other development workflows, giving you more control, increased visibility, and ultimately better data quality.

This feature is in Alpha, where we work with early users and customers to test new features and get feedback before making them generally available.

Note that these features are functional but can change as we improve them. Contact the Product team if you have any questions.

Key features

Some key features of CLI-based tracking plans management include:

Declarative YAML configuration

Define your events, including their names and descriptions, in YAML format.
Create reusable properties with advanced validation rules like min/max length, patterns (through regular expressions), and enums.
Define tracking plan rules by associating events with required properties using a structured reference system.
Reuse property definitions across multiple events with a standardized path reference system.

Powerful CLI tool

The new workflow comes with a powerful Rudder CLI tool that lets you:

Create, update, and delete data catalog and tracking plan resources via command line.
Verify your YAML configurations before pushing changes.
Sync changes in your local files or GitHub repo to RudderStack.

The CLI utility currently only supports pushing to RudderStack, so we recommend starting with a clean workspace (pulling existing assets from the UI is in the works!). Reach out to our team if you would like us to create a dedicated workspace for testing. See our list of limitations to learn more about current differences between the CLI and UI.

Git Integration & CI/CD support

Leverage GitHub Actions to automatically validate and deploy tracking plans from your repository.
Implement version control by tracking changes, managing branches, and reviewing modifications through standard Git workflows.
Review any tracking plan changes before they reach production.

Use Cases

This feature is particularly valuable for teams who:

Manage large tracking plans with hundreds of events and properties.
Need better integration with existing development workflows.
Want to maintain consistent tracking standards across multiple applications.
Require version control and review processes for data governance.

Get started

Install the Rudder CLI tool in your preferred environment.
Generate a workspace-level Service Access Token in the RudderStack dashboard with the following permissions to manage Data Catalog and Tracking Plans:

Resource	Permissions
Tracking Plans	Create & Delete, Edit
Data Catalog	Edit

If you’re on Free or self-hosted plan, or for testing and development only: Generate a Personal Access Token with Read-Write role

Any action authenticated by a Personal Access Token will break if the user generating the token is removed from the organization or there is a breaking change to their permissions.

Token permissions for legacy RBAC system

If you are on the legacy Permissions Management (RBAC) system, your workspace-level Service Access Token should have minimum Admin permissions.

See Generate a workspace-level Service Access Token for steps to create the token.

Initialize a new Tracking Plan project with YAML definitions. Then, sync the changes to your workspace.
Automate Tracking Plan management using GitHub Actions.

Releases: Event Stream Destination Latency Metrics

Thu, 27 Mar 2025 00:00:00 +0000

For data teams, managing stakeholder expectations is critical - they want to see the right data arrive on time.

For data engineers running RudderStack, a variety of factors can impact how quickly data is delivered to destinations. Some variables, like complexity of Transformations attached to a destination, are within your control. In many cases, though, latency can increase due to external factors like sudden traffic spikes or degraded performance of a destination API.

Previously, it was difficult for data engineers to troubleshoot data delays for specific destinations.

Now, RudderStack Org Admins can see granular latency metrics for every cloud destination, giving them visibility into delivery latency and equipping them to better manage stakeholder expectations.

These metrics include:

P95 latency for the selected time window: 95% of data is delivered within or faster than this time. For example, if P95 latency for the last two hours is 9 seconds, that means that 95% of events delivered over the last two hours were delivered within 9 seconds or less.
Latency trend: The latency trend shows P95 latency at intervals over the selected time window. This view is helpful for isolating the timing and impact of increased or decreased latency.

See our P95 Latency Event Metrics documentation for more information on this feature.

Screenshots

Releases: Destination Event Details

Mon, 10 Mar 2025 00:00:00 +0000

Data engineers running RudderStack often get questions from their stakeholders about potential problems with event delivery to a specific destination.

Previously, the events view on destinations was limited, showing only a basic chart and failure responses by top-level event type.

Now, you can see a full list of events that RudderStack has attempted to deliver to each destination, including diagnostic data for:

Successful deliveries
Time of last successful delivery
Failures
Time of last failure

You can also drill into individual events to see granular failure information, including sample payloads.

Note that table shows post-transformation event names, which ensures you are seeing the exact events that RudderStack is delivering to your destination, even if you have modified the event name or have generated new events in a user transformation.

See our Event Metrics documentation for more information on this feature.

Screenshots

Releases: Transformation Failure Alerts

Fri, 07 Mar 2025 00:00:00 +0000

You can now configure dedicated alerts for Transformation failures, giving you the ability to take immediate action when problems arise.

Transformation failures can happen for multiple reasons:

Unexpected data causing errors
Testing not covering all use cases across production data, or
A source with new data is connected to the destination.

Previously, these failures would materialize as cloud destination failure alerts, making it difficult to trace problems. With dedicated transformation failure alerting, you’ll be notified if there is an unexpected problem and can take action immediately.

With this feature, you can configure a global failure rate threshold (applicable for all transformations) and specific thresholds for individual transformations.

See Transformation failure alerts for more information on this feature.

Screenshots

Releases: Events Tab 2-hour Time Window

Fri, 14 Feb 2025 00:00:00 +0000

Previously, the Events tab view in the Sources, Transformations, and Destinations configured in RudderStack defaulted to a 1-day time window.

Now, the Events tab defaults to a 2-hour time window, giving you much more granular visibility into data flow over the last few hours.

In the 2-hour view, data flow is shown in 5-minute increments, helping you:

Review recent spikes or drops in traffic and events with higher precision.
Troubleshoot potential issues as soon as they arise.
Quickly validate if the fixes are having the desired effect.

See our Event Metrics documentation for more information on this feature.

Screenshots

Releases: Custom Types for Data Catalog Properties

Tue, 28 Jan 2025 00:00:00 +0000

RudderStack’s Tracking Plans feature makes it easy for data teams to apply type-safe governance to event schemas flowing through RudderStack. Advanced rules enable you to create types and rules on individual properties, but for teams managing hundreds of properties, individual rules can be limiting.

With the release of Custom Types, you can now build and manage a separate, centralized library of rules, and apply them to multiple properties across your Data Catalog. Custom Types give you the ability to:

More easily manage and apply the same rule across multiple properties.
Implement more complex rules for properties.

You can also create and manage Custom Types via the Data Catalog API.

Example use cases

Array of enums: With Custom Types, you can combine rules and types for complex use cases. For example, you could define enum values as a Custom Type, then use that Custom Type in a property defined as an array, enabling you to govern an array of enums.
Sub-property bundles: If you need to add sub-properties to multiple properties, you can create an Object Custom Type, add the list of specific sub-properties, and apply them to properties in your Data Catalog.
Custom date formats: If you need to enforce a specific date format across multiple different date properties, you can create a Custom Type with your specific logic, then use that type for those properties.
Custom address formats: If you need to enforce formats for different types of addresses (residential and commercial, for example), you can create Custom Types for each and apply them to different properties.

Screenshots

Releases: Support for Azure DevOps Git URLs Starting with ssh while Importing Profiles Project

Tue, 21 Jan 2025 00:00:00 +0000

RudderStack now supports Azure Git URLs starting with ssh while importing your Profiles project from a Git repository.

With this enhancement, you can now use Azure DevOps as a Git provider for your Profiles project in addition to the previously supported ones, that is, Google cloud sources, AWS CodeCommit, GitHub, GitLab, and Bitbucket.

Read more about this feature in the Import Profiles Project from Git guide.

Releases: RudderStack Dagster Integration

Tue, 07 Jan 2025 00:00:00 +0000

Today, we are excited to announce the launch of the dagster-rudderstack Python library, which integrates RudderStack with Dagster. This integration allows teams to seamlessly orchestrate RudderStack Profiles and Reverse ETL jobs within their existing Dagster workflows. You can also define cross-system dependencies, ensuring your warehouse operations are synchronized and optimized beyond the boundaries of RudderStack.

Overview

As organizations integrate more data sources into their workflows, the processes of cleaning, transforming, and activating data become increasingly complex.

Orchestration tools like Dagster simplify these processes by enabling teams to schedule jobs, define dependencies, and maintain reliable, maintainable, and observable data pipelines. Its modular design and support for modern data practices empower teams to streamline workflows, reduce errors, and focus on delivering actionable insights.

Feature walkthrough

Workflow

Install the dagster-rudderstack Python package.
Use the RudderStack-specific operations to define Profiles runs and Reverse ETL syncs within jobs.
Define RudderStack-specific resources like connection details (access tokens, connection IDs, etc.)
Define a schedule.

See the RudderStack Dagster integration docs for more information on using this tool.

Releases: Profiles IDE

Wed, 18 Dec 2024 00:00:00 +0000

The Profiles IDE provides a seamless, production-ready environment for developing and deploying your Profiles projects directly within the RudderStack dashboard. It supports in-platform project management and integration with external version control systems like GitHub and GitLab.

Key features

Integrated editor for building and modifying YAML-based Profiles configuration files.
Safe validation of workflows through separate development schemas.
Easy rollbacks of uncommitted changes with a button click.
Automated notifications when multiple users are editing a project simultaneously.

Workflow

You can use the Profiles IDE to modify inputs, build features, and safely validate the changes in a controlled session, before committing them to the production project.

Here’s how to use the feature:

New Profiles project

Select the Web-based editor (IDE) option while creating a new Profiles project.
Provide the project name, warehouse credentials, and output schema for storing the results.
Click Open in editor mode.

Existing Profiles projects

Go to the Settings tab of the Profiles project.
Click Editor mode.

See the Profiles IDE documentation for more details on using this feature.

Screenshots

Editor mode option after creating a new Profiles project.

Editor mode option in an existing Profiles project.

Specify development/validation schema for testing the changes.

Modify configuration, view the changes, and commit to the production schema.

Releases: SSO Support for Other Providers

Wed, 20 Nov 2024 00:00:00 +0000

RudderStack now supports setting up and enabling SSO for your organization for various SSO providers in addition to the existing SSO providers like Okta, OneLogin, and Azure Entra ID.

Workflow

You can integrate RudderStack SSO with your own SSO provider by following these three simple steps:

Specify the configuration settings in your SSO provider’s admin dashboard.
Configure the SAML 2.0 custom attributes.
Contact the RudderStack team to enable SSO for your organization.

See our Generic SSO Setup Guide for more details.

Releases: Server-side Cookies

Tue, 19 Nov 2024 00:00:00 +0000

You can now set server-side cookies in the JavaScript SDK, ensuring users are tracked across sessions over time, even when browsers expire client-side cookies.

Web browsers are increasingly implementing user tracking restrictions. For example, Safari’s Intelligent Tracking Prevention (ITP) automatically expires client-side, third-party cookies after 7 days. Suppose one of your visitor’s cookies expire and they return to your website. In that case, RudderStack’s JavaScript SDK sees them as a new user and assigns them a new unique anonymousId- this can create challenges for customer journey tracking, attribution analytics, and identity resolution because the ID and session data would show two users when, in reality, it is the same user returning to your website.

With this release, you can configure the JavaScript SDK to set server-side cookies, which aren’t subject to the client-side cookie expiration timelines enforced by Safari and other browsers.

Read our server-side cookies documentation for more information on this feature.

Workflow

To implement server-side cookies, set theuseServerSideCookies option to true while loading the JavaScript SDK.

javascript

rudderanalytics.load(WRITE_KEY, DATA_PLANE_URL, {
 useServerSideCookies: true // Default is false
});

Setting server-side cookies requires that you make the cookie request to your website domain.

Most customers use a proxy, but the SDK also supports custom implementations.

How it works

The JavaScript SDK makes explicit POST requests to the server to set cookies via the /rsaRequest endpoint:

The response includes Set-Cookie headers which set the rl_anonymous_id cookie (user’s anonymousId value which is persisted through the server-side cookie).

Releases: Service Access Tokens

Thu, 24 Oct 2024 00:00:00 +0000

We have expanded access to our APIs and services with Service Access Tokens (SATs). SATs can be created at the organization or workspace level and are not tied to individual user accounts.

SATs are ideal for production use cases and centralized management of tokens across the RudderStack platform.

Previously, access to RudderStack APIs required you to create Personal Access Tokens, which are tied to an individual user’s account. If that user account was removed, or permissions on the account were changed, access to APIs and services was impacted as well.

With this release, you can create and manage central SATs to ensure stability and security for critical production workflows.

Contact the RudderStack team to get access to this feature.

How it works

Org Admins can create SATs at the organization or workspace level.

Organization-level SATs can be used to access SSO SCIM and the Audit Log API, used for managing SCIM users and accessing audit logs from the platform, respectively.

Workspace-level SATs can be used to access resources in a specific workspace. These are used to manage programmatic workflows that leverage RudderStack APIs. Some examples are:

Using the Transformations API to manage Transformations programmatically.
Using the Data Catalog API to programmatically manage your Data Catalog and Tracking Plans.
Using the Test API to run programmatic end-to-end pipeline tests.

Operations performed by both SAT types are logged and are available through the Audit Logs view and the Audit Logs API.

Create a SAT

To create SATs, Org Admins can access the Service Access Token view by going to Settings > Organization > Service Access Tokens tab.

Click the Organization or Workspace tab followed by Generate new Token to generate a new Organization-level SAT or Workspace-level SAT.

See the Service Access Token documentation for more information.

Screenshots

The following screenshots highlight the SAT generation flow:

Generate an organization-level SAT:

Copy newly-generated organization-level SAT:

Generate a workspace-level SAT:

Specify workspace-level SAT permissions:

Copy newly-generated workspace-level SAT:

Releases: Full Custom Consent Manager Support

Fri, 04 Oct 2024 00:00:00 +0000

Previously, RudderStack supported fully-integrated consent data flows for OneTrust and Ketch - two popular consent management tools.

With this release, you can integrate your custom consent management solution with RudderStack, giving you granular control over consent settings for each individual destination.

You can also use the Custom Consent Management feature to implement compliant pre-consent user tracking, with the options to store no cookies, store only the session tracking cookie, or only persist the anonymousId.

RudderStack also supports running multiple consent management solutions simultaneously, which is useful when consent management solutions differ across platforms.

Custom Consent Management is now available on all RudderStack plans. See our documentation for more information on using this feature.

Workflow overview

Before capturing user consent, make sure that:

You are running the latest version of the JavaScript SDK.

You have set the enabled key to true in the consentManagement API object. See the JavaScript SDK documentation for more information.

Update the code on your website to grab consent IDs from your custom consent manager.
Add the consent setting in the load object, or pass them to the SDK’s consent API using the consent method, as shown:

javascript

rudderanalytics.consent({
 consentManagement: {
 allowedConsentIds: ['performance', 'analytics'],
 deniedConsentIds: ['advertising']
 }
});

Using the consent method is helpful for tracking users who update consent settings and then go on to perform other actions on the same page and in the same session.

Specify the consent settings for each destination by adding the allowed consent ID values in the Consent settings section of the destination configuration. In the below example, the destination accepts data from users have consented to only performance or analytics tracking:

Releases: Global Advanced Property Rules across Tracking Plans

Fri, 04 Oct 2024 00:00:00 +0000

Our Tracking Plans feature evaluates advanced rules for properties, allowing you to flag data that does not align to your settings for enums, data formats, minimum/maximum values, and more.

Previously, you had to apply advanced rules individually to each event in each Tracking Plan — a time consuming and error-prone process.

With this release, advanced rules for properties are now set globally through the Data Catalog. That means the advanced rules are now applied to the property across all events and Tracking Plans, eliminating the need to update rules in multiple places.

Advanced rules for properties are now only managed globally through the Data Catalog. You can no longer set individual advanced rules for properties through Tracking Plans.

Note that:

If you had any existing advanced rules, you have been automatically migrated. Existing settings for advanced rules will not be affected, and any property-level advanced rules you created previously have automatically be propagated to the Data Catalog for global management across all Tracking Plans.
This release applies to all the customers using our UI-based Tracking Plans features.

Read our Data Catalog documentation for more information on this feature.

Screenshots

Releases: Support for URLs Starting with ssh while Importing Profiles Project from Git

Fri, 27 Sep 2024 00:00:00 +0000

RudderStack now supports URLs starting with ssh (for example, ssh://git@host:port/path.git) while importing your Profiles project from a Git repository.

With this enhancement, you can now use more Git providers like Google cloud sources, AWS CodeCommit, etc. for your Profiles project in addition to the previously supported ones, that is, GitHub, GitLab, and Bitbucket.

Read more about this feature in the Import Profiles Project from Git guide.

Releases: Configurable Alerts for Profiles

Thu, 08 Aug 2024 00:00:00 +0000

RudderStack now supports setting up notifications for any failures in your Profiles project runs. This helps you troubleshoot the issues and take remedial actions on time.

To use this feature:

Navigate to Settings > Workspace in your RudderStack dashboard and go to the Alerts tab.
Click the Profiles tab and toggle on the Run failures setting.

Read more about this feature in the Configurable Alerts guide.

Releases: Snowflake Key Pair Authentication Support for Profiles

Thu, 04 Jul 2024 00:00:00 +0000

RudderStack now supports Snowflake’s key pair authentication mechanism while setting up your Profiles connection. You can now configure a key pair in Snowflake and use the private key for user authentication.

Snowflake’s key pair authentication mechanism leverages a 2048-bit RSA key pair and offers better security over basic authentication (username + password).

To use this feature:

Set up a key pair in Snowflake.
Create a warehouse connection to allow Profiles Builder (PB) to access your data by running the pb init connection command.
In the subsequent setup, enter y (yes) for Do you want to use key-pair authentication.
Enter the file path containing the private key.
If the private key is encrypted, specify the Private Key Passphrase used for encryption.
Continue with the rest of the warehouse connection setup.

See the Profiles CLI Setup guide for more information.

Releases: Transformation Credential Store

Tue, 02 Jul 2024 00:00:00 +0000

RudderStack allows you to create and pass sensitive user secrets or environment variables as configurable credentials to your transformations.

By storing secrets and variables in RudderStack’s credential store, you can avoid hardcoding sensitive information in your transformations and avoid any security risks.

RudderStack credential store supports two types of credentials:

Secrets let you store text values encrypted. You can use them to securely store sensitive information like passwords, app secrets, API keys and authorization tokens.
Variables are non-encrypted strings that you can use to store application configuration.

See the Transformation Credentials documentation for more information on this feature.

Releases: Tracking Plan Nested Properties Support

Thu, 23 May 2024 00:00:00 +0000

RudderStack supports defining nested properties for an event in your tracking plan, allowing you to validate complex data structures in your inbound events and metadata.

While editing your tracking plan, choose an event property of object or array data type, click the + sign next to it and choose the event property to nest.

Note that:

RudderStack supports up to three levels of nesting.

You can nest properties within an event property of object or array data type.

See our Tracking Plans documentation for more details.

Releases: Cohorts and Activations

Thu, 16 May 2024 00:00:00 +0000

RudderStack Profiles now provides the Cohorts and Activations features, which let you define target customer segments in your warehouse and activate them in downstream marketing tools like Braze, Mailchimp, etc. They give business users unprecedented access to complete customer profiles through an intuitive UI.

Cohorts

Using cohorts, you can define core customer segments in your warehouse via a simple YAML configuration, and the entire business can use them as a single source of truth. It is a subset of instances of an entity meeting a specified set of characteristics, behaviors, or attributes. For example, if you have a user as an entity, you can define cohorts like known users, new users, or North American users, etc.

By leveraging cohorts, you can target specific customer segments by enabling targeted campaigns and analysis. See Cohorts for more information.

Activations

Activations provide business users the access to explore the customer 360, build audiences from cohorts, and sync them directly to the desired destinations. This helps you make informed decisions, run personalized marketing campaigns, and enhance the overall customer experience across multiple platforms.

See Activations for more information.

Releases: Reverse ETL 1:Many Connections Enhancement

Thu, 25 Apr 2024 00:00:00 +0000

RudderStack now supports 1:many connections for the Reverse ETL feature, meaning you can now connect a Reverse ETL source to multiple destinations:

Previously, RudderStack supported connecting a Reverse ETL source to only one destination, and you had to set up multiple pipelines with the same source to send data to multiple destinations. With this enhancement, you can send data from one warehouse source to multiple destinations across your entire stack.

See our documentation on Setting Up Reverse ETL Connections for more information.

Releases: Sync Schedule Enhancement for Reverse ETL Pipelines

Tue, 12 Mar 2024 00:00:00 +0000

RudderStack lets you specify a sync schedule that defines how frequently data is synced from your Reverse ETL sources. When you set the schedule type to Basic, you can now set this interval to as low as 5 minutes, so you can sync more frequently and keep the destination data up to date.

See the Sync Schedule Settings for more information on this update.

Releases: Configurable Alerts Enhancement

Tue, 05 Mar 2024 00:00:00 +0000

RudderStack now supports smart alerting capabilities that let you set up timely notifications for critical data issues, helping you take necessary actions before they escalate into major problems.

With this alerting feature, you can:

Configure alerts for event delivery failures, warehouse pre-sync or sync failures, and tracking plan violations.
Set failure thresholds at a workspace and resource level, so you are notified only when absolutely necessary.
Break alerting silos by setting up alert delivery channels of your choice like email, webhook, Slack, PagerDuty, or any other tool of your choice.

Read more about this feature in our Configurable Alerts guide.

Releases: Feature Launch: Health Dashboard for Data Quality Monitoring and Alerting

Thu, 01 Feb 2024 00:00:00 +0000

Today, we’re introducing the Health Dashboard, the final tool in our Data Quality toolkit. It provides a centralized place to monitor data quality and manage alerts across your entire stack.

With the Health Dashboard, you can drive data trust and ensure that every strategic decision, from marketing campaigns to product development, is based on accurate and reliable information. It exposes the key metrics related to your pipelines like:

Event ingestion metrics
Event delivery metrics
Warehouse load metrics
Tracking plan violations

You can also set up timely notifications for critical issues so you can take appropriate action immediately. You can configure thresholds for key alerts by source and destination, and deliver alerts to your system of choice like email, webhook, Slack, or any other tool of your choice.

For more information on this feature, see our Health Dashboard for Data Quality Monitoring and Alerting launch blog.

Releases: Feature Launch: Transformations for Real-time Schema Fixes

Wed, 31 Jan 2024 00:00:00 +0000

Tracking plans enable you to catch violations and quarantine or drop bad data before it gets downstream. But without remedying the bad data, you’re left with an incomplete dataset and a partial picture of your customer.

Today, we’re introducing real-time schema fixes with Transformations so you can fix bad data while maintaining an efficient workflow. This feature is part of our Data Quality Toolkit, a set of capabilities that help you guarantee quality data from the source so you can spend less time wrangling and more time helping your business drive revenue.

Using Tracking plans, you can enrich your events with violation information like erroneous property names, incorrect data types, or wrong payload structures. Then, you can write transformations in JavaScript or Python to correct these violations before they impact your stakeholders downstream.

Because transformations occur in your pipeline – after event collection and before delivery – you don’t have to worry about submitting a dev ticket. You can fix bad data in real-time without redeploying sites or apps, a critical benefit especially during code freezes.

For more information on this feature, see our Transformations for real-time schema fixes launch blog.

Releases: Feature launch: Tracking Plans for Violation Management

Tue, 30 Jan 2024 00:00:00 +0000

Bad data may be inevitable, but it doesn’t have to keep you from supporting your business. With advanced violation management via Tracking Plans, you can spend less time wrangling and more time helping your business drive revenue.

Tracking Plans, part of RudderStack’s Data Quality Toolkit, allow you to easily enforce data quality standards on your incoming events. This feature works seamlessly with the Data Catalog feature and lets you define the required attributes and expected data formats for your event data. The tracking plans then automatically evaluate every incoming event against your standards and flag violations of any type on any level – be it unplanned events, errant key/value properties, missing required fields, and so on.

When you catch a violation, you can use RudderStack’s custom logic to determine what to do with the events based on your use cases, data volumes, and risk tolerance. You can drop the erroneous events, deliver them with a flag, or send them only to a data lake destination for replay later.

For more information on this feature, see our Tracking Plans for Violation Management launch blog.

Releases: Feature launch: Data Catalog

Mon, 29 Jan 2024 00:00:00 +0000

Data definitions should be a team sport. In the real world, though, hard-to-bridge divides exist between different business units. Development, data, and business teams have different incentives and operate independently.

This means data teams and developers rarely get complete requirements from business teams. A shared document may be floating somewhere in the ether, but it’s often an incomplete, out-of-date spreadsheet. This scenario results in messy event instrumentation that creates issues downstream. Issues that the data team has to fix.

With our tools for collaborative event definitions, you can align every team around the same event definitions and integrate data quality into your existing workflow. Our Data Catalog and Event Audit API help you guarantee quality customer data from the source.

For more information on this feature, see our Data Catalog launch blog.

Releases: In-app Event Usage Reporting Enhancements

Thu, 07 Dec 2023 00:00:00 +0000

We have completely revamped our in-app usage reporting across Event Stream and Reverse ETL features. You can now view your usage data across time and break it down by source.

To see this reporting feature, log in to the RudderStack dashboard and navigate to Settings > Organization > Usage. Here, you can view the event usage by product.

See our Events Usage guide for more information on this feature.

Releases: Multiple Workspaces and Environments

Thu, 07 Dec 2023 00:00:00 +0000

RudderStack now supports multiple workspaces within an organization in its Starter, Growth, and Enterprise plans.

A workspace is an environment or nested grouping of resources and related settings. You can use the multiple workspaces feature for separating your development and production pipeline workflows and switch seamlessly between them. You can also add/remove members who are a part of your RudderStack organization to the relevant workspaces.

The number of available workspaces depends on your RudderStack Cloud plan. See the Workspaces documentation for more information.

To view the workspace details and manage its settings, go to Settings > Workspace in your RudderStack dashboard.

To switch between workspaces, click Workspace > Switch workspace. Then, select the workspace you want to view.

For more information on this feature, see our Workspaces guide.

Releases: Reverse ETL Connection Limit Enhancement

Thu, 07 Dec 2023 00:00:00 +0000

RudderStack now supports setting up to 10 Reverse ETL connections in the RudderStack Free and Starter plans and unlimited connections in the Growth and Enterprise plans.

Earlier, our Reverse ETL feature was limited to just 1 connection for the Free and Starter plans. Now, you can set up to 10 connections to sync the customer data residing in your data warehouse to the downstream destinations of your choice.

Releases: Cancellable Reverse ETL Syncs

Thu, 30 Nov 2023 00:00:00 +0000

RudderStack lets you cancel an ongoing Reverse ETL sync at any point to fix any configuration or destination-related issues without having to contact RudderStack Support.

At times, there might be scenarios where you might want to cancel an ongoing sync because of the following reasons:

Missing/incorrect mappings leading to inaccurate data for an otherwise healthy Reverse ETL pipeline
Wrong destination configuration
Missing required data in the warehouse table, etc.

Now, you can cancel your ongoing syncs by going to the Syncs tab of your reverse ETL source and clicking Stop Now.

In the confirmation popup, click Stop Sync to cancel and stop the sync. RudderStack automatically cancels the sync and stops reading data from the warehouse.

After you stop a sync, RudderStack automatically triggers this draining process in the background. The time taken for this process to complete depends on the amount of data. Hence, waiting for some time before triggering next sync is recommended.

To read more about this feature, read our Syncing Events guide.

Releases: Health Dashboard for Pipelines and Tracking Plans Observability

Thu, 16 Nov 2023 00:00:00 +0000

We have released the Health dashboard to help you get better observability into your Event Stream pipelines and tracking plans.

This dashboard gives you visibility into the event delivery and failures for all the Event Stream destinations in your workspace. You can filter your destinations by type (Cloud or Warehouse) or view metrics for only the destinations that have event failures.

In the Tracking Plans tab, you get a list of all sources connected to a tracking plan in your workspace along with metrics for validated events and violations.

We’re also planning to add a tab for observability into your Reverse ETL syncs in the upcoming release. Stay tuned!

See our Health Dashboard documentation for more information on this feature.

Releases: Tracking Plans for Growth Customers

Thu, 16 Nov 2023 00:00:00 +0000

We are thrilled to announce the expansion of our Tracking Plans feature! Previously exclusive to Enterprise customers, tracking plans are now available in the RudderStack Cloud Growth plan as well, starting November 15th.

Tracking plans are a powerful tool that help you ensure data quality, enhancing your analytics experience. See our documentation for more information on this feature.

Before diving in, make sure to connect with your Customer Success team for guidance.

Releases: Fall 2023 Product Roundup

Wed, 01 Nov 2023 00:00:00 +0000

RudderStack is the warehouse native Customer Data Platform and makes it easier for you to collect, unify, and activate your customer data to drive better business outcomes.

Over the past few months, we’ve released a lot of new features and enhancements to make RudderStack a more powerful tool. Check out the product roundup below to ensure you don’t miss anything.

The compliance toolkit

We launched a toolkit to help you simplify compliance across the entire data lifecycle. You can now continuously manage consent, collection, storage, and deletion all within RudderStack. Each tool runs within your own data infrastructure and supports first-class integrations with compliance tools like OneTrust and Ketch.

Read our launch blog to learn more.

New features

Real-time activation API

With the real-time Activation API, you can extend RudderStack Profiles to every corner of the enterprise through real-time, RudderStack-managed API. Now, anyone in your company can access your customer 360 data in real time using a single API integration.

Read the launch announcement to learn more and contact the RudderStack Product Team to join our Early Access Program.

ProfilesML

ProfilesML enables you to build predictive features in your warehouse without MLOps. The new feature brings out-of-the-box predictive capabilities to RudderStack Profiles. It fits within your existing Profiles workflow, allowing you to start building predictive features in four steps:

Choose your ProfilesML model (churn prediction and lead scoring are currently available, and more models are on the way).
Specify the predictive feature or define it yourself.
Push the ProfilesML project to Github and kick off a run.
Monitor model performance and tweak as necessary.

Read the launch announcement to learn more and contact the RudderStack Product Team to join our Early Access Program.

Real-time Braze deduplication

With this new feature, RudderStack prevents duplicate data from being sent to Braze, saving data points and avoiding unnecessary billing overages. No more custom work and no more accidental overages from duplicate data points. The Braze deduplication feature is available in both cloud and device mode for Event Stream and for Reverse ETL pipelines.

Read the launch announcement and the release notes to learn more.

User Suppression API

You can use the user suppression API suppress event collection across multiple data sources and delete user information from multiple destinations with a single endpoint.

With this API, you can create a suppression rule that automatically stops tracking user events across data sources when a user opts out of tracking and automatically deletes user data from downstream destinations when a user requests to be forgotten.

Read the launch announcement and the release notes to learn more.

Cookieless tracking

RudderStack’s cookieless tracking feature, now a part of our JavaScript SDK, gives you control over what user information you collect and where to store it, so you can adapt to fast-changing regulatory environments.

While loading the JavaScript SDK, you can specify the user information you want to store, such as userId, anonymousId, and session information, and you can decide where to store it. Store data in browser cookies or use one of four cookieless storage methods: local storage, in-memory storage, session storage, or none.

Read the launch announcement and the documentation to learn more.

RudderStack’s consent management features give you fine-grained control of which integrations are loaded and receive customer data based on any combination of consent preferences chosen by the user.

Our fully integrated consent solution works with first-class consent tools like OneTrust, as well as custom-built systems, and it now allows for both client-side and server-side consent categorization of each individual downstream integration.

Read the launch announcement to learn more.

Databricks Reverse ETL source

If you’re using Databricks, you can now easily sync data from your data lakehouse to your entire stack. This new integration is a big unlock if you’re building models or audiences in Databricks and want to push that data to marketing and product tools. It supports Databricks Unity Catalog and works with our visual data mapper and mirror mode features.

Read the launch announcement and the documentation to learn more.

Apache Kafka source

Our Kafka source integration enables you to automatically forward Kafka streams to key business tools and standardize schemas for data used in identity resolution and customer 360 projects – all without customer integration and pipeline work. With RudderStack, you can get more out of your Kafka implementation.

Read the launch announcement to learn more and contact the RudderStack Product Team to join our Early Access Program.

Materialize destination

With the RudderStack Materialize destination, you can now get the power of a data warehouse and the speed of real-time streaming. Use the Materialize destination integration to stream real-time events from RudderStack directly into Materialize – the operational data warehouse – where it’s available for real-time materialized views, alerts, and analytics. Check out the Materialize documentation to learn how to set up the connection.

Read the launch announcement to learn more.

More updates

JavaScript SDK v3

Our latest Javascript SDK (currently in beta) is more lightweight and efficient, and it’s less vulnerable to adblockers. Best of all, you can now load specific SDK features by leveraging SDK plugins.

Read the release notes for more information.

JSON mapping support

With JSON mapping, you can now map RudderStack events to a destination’s expected format using an intuitive mapping UI or a JSON text editor.

Read the release notes to learn more.

Billing and plans UI enhancement

We released a new billing and plans UI, making it easier for you to manage your RudderStack Cloud plan and update your payment and billing information.

Read the release notes to learn more.

Databricks Partner Connect

RudderStack is now featured on Databricks Partner Connect, making it easy for Databricks users to get started with RudderStack directly from Databricks.

Read the release notes to learn more.

New integration releases and enhancements

This fall, we added a host of new sources and destinations to our integrations directory and released important enhancements for many others.

Here’s a quick summary of what’s new:

ActiveCampaign Hybrid mode (release notes)
Bing ads Audience rETL destination (release notes)
comScore destination (release notes)
Eloqua ReverseETL destination (release notes)
Facebook Conversions destination (release notes)
Ortto destination (release notes)
Ortto source (release notes)

Enhancements:

Google Cloud Functions enhancements (release notes)
Marketo Static Lists enhancement (release notes)
Mixpanel enhancements (release notes)
Clevertap enhancements (release notes)
Pinterest Ads mapping enhancements (release notes)