The feed has always supported multiple feeds per form. This provides multiple conditional API Goals; it’s basically a way to get around my inability to support more than one Conditional API Goal per feed when configuring a feed.
As I implement complex tests, I’ve found that there’s no good way to prevent each feed creating an Affiliate tracking record. If you have a form with an Affiliate field, and that form has multiple feeds, the associated Contact will receive an Affiliate tracking record for each feed.
The current implementation doesn’t properly handle the feed’s opt-in configuration. The first feed processes opt-in configuration. The issue is that any subsequent feeds also process the opt-in configuration. Such action will only have no effect since the first feed already processed the opt-in configuration. The action unnecessarily slows feed processing.
The resolution to these issues is to implement a second kind of feed processing, “Update a Contact”, which will provide a configuration mechanism for such conditional API Goals.