Native Marketo source connection (events/activities) to stream into Data Collection Core Service (DCCS) for AJO & Unitary Events

Currently, the native Marketo Engage integration uses Adobe's Sources connector framework & not Data Collection Core Service (DCCS). Data lands in the Data Lake and Real-Time Profile (which is why you can see it in Profile browse), however it never passes through DCCS nor does it create Unitary Events that would be extremely helpful for AJO use cases for triggering journeys based on Marketo engagement events & activities. Especially when we want to designate specific users and/or email addresses for the journeys in AJO when profiles have multiples per profile.

Options for workarounds exists, however labor intensive & data heavy.

1. Stand up a streaming ingestion path for the same events, so that they arrive via DCCS/Edge, which AJO B2C can listen to as a Unitary Event.
2. Use AEP Audience (streaming) + Read Audience in AJO B2C, store the trail downloaded email in a lookup dataset either at ingestion time (a field like trail_email) or use Data Distiller to write it on a schedule. Later, use this lookup dataset to pull in that value and use it to override.

In addition to labor intensive & data heavy the above options have multi workflows, data latency, as well as data limitations.

Ideally the native Marketo source connection should be completely streaming into all services and across the full AEP platform & products to avoid such workarounds.