You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Campaigns: allow custom objects / Companies in list, not only People
#30104
Campaign lists currently only accept People as members.
We prospect organizations, where the natural CRM entity is a custom object with a generic institutional email, not a person.
A message list member is always a personId, and the send engine, tracking (opens/clicks/bounces), campaign_deliveries and unsubscribe handling are all built on top of that
The only way to use native campaigns today is one "envelope" Person record per organization email, which pollutes the People object and breaks data integrity.
Use case
We'd like campaign lists to support members that are not People
Example:
~10,000 establishments (custom object prospect), each with an email like contact@establishment.fr, sales@establishement.fr
The outreach target is the organization itself: replies, deduplication and ownership all live at the establishment level.
Proposal
Polymorphic list for campaigns, any object with an email field should be allowed in the list.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Summary
Campaign lists currently only accept People as members.
We prospect organizations, where the natural CRM entity is a custom object with a generic institutional email, not a person.
A message list member is always a personId, and the send engine, tracking (opens/clicks/bounces), campaign_deliveries and unsubscribe handling are all built on top of that
The only way to use native campaigns today is one "envelope" Person record per organization email, which pollutes the People object and breaks data integrity.
Use case
We'd like campaign lists to support members that are not People
Example:
~10,000 establishments (custom object prospect), each with an email like contact@establishment.fr, sales@establishement.fr
The outreach target is the organization itself: replies, deduplication and ownership all live at the establishment level.
Proposal
Polymorphic list for campaigns, any object with an email field should be allowed in the list.
All reactions