Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
PorterHorne opened this issue Aug 6, 2018 · 1 comment

Comments

@PorterHorne
Copy link

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
Copy link

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants