Thanks for posting this idea. I'm also encountering the same type of situation, and we've contemplated doing the same approach of managing multiple datastream IDs dynamically in the client application. However, this would mean the logic to decide which datastream ID to use has to reside within the c...

Description There needs to be a way for incoming XDM events to be filtered/routed to specific enabled Datastream Service.   Current Behaviour Currently when we enable Analytics, Experience Platform, Event Forwarding for example, all incoming XDM events are pushed to all the enabled Services for the ...

In the Adobe documentation on sending non-XDM data, it mentions that "type" can use as a substitute for "xdm.eventType".  https://experienceleague.adobe.com/docs/experience-platform/edge/fundamentals/tracking-events.html?lang=en#sending-non-xdm-data   While it's possible to define "type", I can't f...