Summary

Jitsu already supports the Pixel Endpoint, which is a great feature for collecting events through an image pixel. I’d like to propose extending this capability by adding Redirection Event Collection.

Use Case:
In many scenarios (e.g., email campaigns, messaging platforms, or any environment where embedding JavaScript or pixels is difficult), it’s much easier to generate a dynamic link. The flow would be:

1. The user clicks the link.
2. The Jitsu server logs the event (just like the pixel does).
3. The server then redirects the user to the intended final destination.

This enables seamless event tracking on links without requiring additional integrations.

Additional Requirement:
If the server is using an ID endpoint (e.g., to bypass ITP restrictions in Safari), the redirection endpoint should also support setting cookies in the same way, ensuring user identity tracking works consistently across pixel and redirect-based events.

This would unlock new use cases for Jitsu in marketing and analytics pipelines, especially in environments where tracking pixels are not possible.

System configuration and versions

N/A – this is a feature request and not tied to a specific bug or version. Applies to both Jitsu Next and self-hosted environments.

Artifacts (logs, etc)

N/A – not a bug report.