Today, if you wanted to see what Smart Campaigns are idle or inactive via API, you would need to query activities for the Smart Campaign being referenced and work backwards. This makes ongoing performance maintenance for the good of the platform onerous.
By comparison, if one could pull something like the last timestamp someone ran through a trigger campaign or the last time a batch campaign processed more than 0 records, finding what Smart Campaigns need to be deactivated/flagged for review/etc. becomes more straightforward. Often the 6 months inactivity notification is insufficient for larger instances, and more proactive checking via API would alleviate problems for those more complex instances.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.