Trigger off Journey events via Query Service Jobs

[#1]

Description - Presently, Query Service jobs do not write to the DCCS (Data Collection Core Services) which results in these events being ineligible to be qualified for event qualification to kick off a journey. I would like to be able to use a Query Service job to kick off a qualifying event for 

Why is this feature important to you - This would allow us to kick off journeys from a more flexible point of view. We typically have relied on subscriptions to events from our IT partners that we digest via the HTTP API Source. Unfortunately, development of these events is heavily dev intensive and can often take months. We had a use case for a reminder email for a customers order to send 2 days before their quoted pickup time. We frequently see updated date/time for our order pickups, so we need to use contextual data from other events to qualify the send. We were able to right the logic very eloquently in query servives, but we were not able to actually excecute using it, because of the inability to qualify the event via DCCS, even though it looks good on the profile.

How would you like the feature to work - I would love a toggle in the dataset level to indicate whether or not I would like the data to be digested via DCCS. 

Current Behaviour - Event data that is generated via query service jobs are ineligible for event qualification. We're able to write the data to profile, so there shouldn't be an inflation in usage, but we would be able to better utilize the data that we're digesting from our various partners to drive customer facing results.

[#2]

I can definitely see the purpose of this use case. Great post. 

[#3]

Hadn't even thought of this! Great idea!