This is a bit out there, but let me provide some context.
Today, if you use Marketo Custom Objects, you can link two layers of objects--one that connects to the user record and one that can connect to that previous custom object. As a result, you can take advantage of certain connections between the two custom objects, such as referencing them in Smart Lists.
I would like the ability to establish secondary connections to Marketo Activities to provide supplemental details like Marketo Custom Objects can. The main use case is to extend metadata on activities where this is relevant. Some examples might be:
- If a record has a Change Nurture Stream activity, have a secondary activity that can record the business reason why the stream changed and any nurture-specific scoring
- If a record is rejected by sales with a rejection reason field, append the rejection reason data to a Change Revenue Stage activity.
- If a record unsubscribes from email after a message, note in the activity that this send email activity resulted in a later unsubscribe.
You'll notice in each example that these extensions come on top of standard Marketo activities--this isn't an issue with custom activities. However, without some way to hook into these existing activities, Marketo users are stuck duplicating system activities with custom ones with extended attributes.
.png)