I've largely been ignoring the Audience Entry Source within Journey Builder since it's release not too long ago, but after testing it out recently I am pretty impressed.
Some of the pros:
- Removes the need for fire event activity in Automation Studio
- Email Studio Audiences can be configured to either automatically process all records, or only the new records
- If record doesn't exist, a new one is created, effectively removing the need for many steps in Contact Builder
- Lack of API compatibility
- Can't reuse across other Journeys
Question: Based on current functionality, why would an Event Entry Source be used in place of an Audience Entry Source for a typical Journey? I prefer Event Sources personally because I am accustomed to the routine of making attribute groups / root sources / automation / fire event, but it does seem as though Audiences may be the simplified approach.
[Note: If this question is too broad I can relate it back to a single example use case and ask for best practices].
Thanks as always!