What does this PR do?
With the release of destination actions for Amplitude users can now use this SessionId Middleware to send data to Amplitude via cloud-mode and still track sessions for users
Are there breaking changes in this PR?
No breaking changes
Has this been tested end-to-end? Please provide screenshots on how the fix now populates in the end tool. If not, what was done to test?
Tested via test account ensuring that new sessions are recorded without sending events in device-mode, rather sending in cloud-mode enhanced by said middleware
What does this PR do? With the release of destination actions for Amplitude users can now use this SessionId Middleware to send data to Amplitude via cloud-mode and still track sessions for users
Are there breaking changes in this PR? No breaking changes
Has this been tested end-to-end? Please provide screenshots on how the fix now populates in the end tool. If not, what was done to test? Tested via test account ensuring that new sessions are recorded without sending events in device-mode, rather sending in cloud-mode enhanced by said middleware
Helpful Docs https://segment.com/docs/connections/destinations/catalog/actions-amplitude/