list_email_id should be a column in the Email object and be the primary key for an object

[PorterHorne]

I do not see list_email_id as a column in the Email object. I also do not see an object with primary key list_email_id.

If these exist, please provide documentation and make them available thru the API

If they do not exist, are there plans to add list_email_id as a column in the Email object and create an object with primary key list_email_id?

[jdarrell]

list_email_id absolutely should be the primary key for an object, one probably called List Email, that at a minimum has the columns:

list_email_id
list_id
email_id

No object other than List Membership has list_id on it, indicating that the List object currently cannot be associated with anything except the prospect (through the API).

Since such a "List Email" object is really just an association between list and email, that object would be storing the the same number of rows as Visitor Activity where list_email_id is not null. Therefore, I think list_id should just be added to the Visitor Activity object. Since Visitor Activity has both email_id and list_email_id, we get all the utility gained from adding list_email_id to Email + creating a new object with list_email_id as its primary key.

Please add list_id to Visitor Activity!