Ideas

Today, when a Marketo user accesses the REST API and reads Activity ID #22 (Change Score), the primary attribute is called "Score Name".  This is defined as an integer. However, the integral value does not provide a match with other calls, like checking object fields.   If I look in the UI at a score activity, I can see that both a score ID attribute and score name attribute are logged:     As a result, I'm guessing there's been a slight error where Score ID is being retrieved instead of Score Name. Could this please be updated so the proper, resolvable value is passed? Otherwise, this forces solution providers to write manual workarounds.   ... View more

One of the less-commonly-known facts about Marketo's REST API is that all activities within a record's Activity Log are recorded--even if the Activity itself isn't really an Activity.   This is notable in cases where someone has set up a choice in a Flow Step that corresponds to an Activity. For example, someone may have a Change Data Value or Change Progression Status Flow Step with multiple options along the lines of:   Choice 1: If condition is met, update this value. Else, do nothing.   This is a pretty common setup for Marketo users to have in Smart Campaigns, so when someone hits the Else condition, they get an Activity in their log similar to the following:     When this activity is looked at via REST API, however, it simply shows the associated lead ID, step ID, activity ID, etc. without providing any additional context. This can make things look as though there is some sort of error occurring and not that this is intentional behavior. As a result, would it be possible to expose skip as a value that can be seen from Activity extracts? This allows developers to see that this is an intentional omission and not a technical issue. ... View more