Custom Web Device Mode Integrations
2 minute read
This guide will help you build custom web device mode integrations that let you connect RudderStack to any tool or platform, even when there is no pre-built integration available.
Overview
Custom web device mode integrations run client-side in your users’ browsers (device mode), giving you direct control over how events are transformed and sent to your chosen tools.
This approach is helpful when you need to:
- Connect to niche or proprietary tools that aren’t part of RudderStack’s standard integration catalog.
- Implement custom business logic for event transformation that goes beyond what configuration settings allow.
- Maintain real-time, client-side connections to tools that require immediate data processing.
- Bridge legacy systems that need specific data formats or authentication methods.
How custom integrations work
A custom web device mode integration creates a bridge between RudderStack’s event tracking and your tool’s SDK or API. RudderStack handles the event collection, consent management, and filtering, while your custom code handles the specific requirements of your chosen tool.
The integration runs alongside RudderStack’s other device mode integrations, automatically receiving filtered and transformed events based on your destination configuration. This means your custom integration benefits from all of RudderStack’s built-in features while giving you complete control over the final data delivery.
Supported features
All custom device mode integrations support the same features as standard RudderStack device mode integrations:
- Device Mode Transformations: If you have connected a device mode transformation to your custom web device mode destination, RudderStack automatically applies the transformation before sending events to the integration.
- Consent management: Your custom integration respects the consent management settings configured in your destination. Events are forwarded only when the consent requirements are met.
- Event filtering: You can configure client-side event filtering in your destination settings to control which events reach your custom integration.
