Skip to main content
Nathan_Fehler2
Level 2
October 15, 2018
Question

Managing Contacts Associated with Multiple Accounts

  • October 15, 2018
  • 2 replies
  • 4825 views

Our business model often contains leads/contacts (email addresses) that are associated with multiple accounts. Each contact in this scenario has a single unique email that is used across all associated accounts. We would like to be able to send more personalized communications with a send per unique email-account relationship based on the account that the lead or contact is associated with. Due to the way Marketo dedupes email sends to only one record with an email address, is there a way to:

  • Send an email to an email address for each account associated with it (See Examples):
    • abc@xyz.com  Company1
    • abc@xyz.com  Company2
    • abc@xyz.com  Company3

Has anyone attempted to do this sort of thing using Custom Objects, API Triggers, Otherwise? We use Microsoft Dynamics CRM solution, and feed data to Marketo via custom APIs from our in-house database.

2 replies

Jay_Jiang
Level 10
October 15, 2018

I'd imagine it'd have to be some kind of api solution. If you aren't sending large amounts of emails, one way I can think of is...

Build a requested smart campaign with flow send email and a webhook endpoint in the language of your choice with some api calls to marketo.

Marketo sends webhook of lead's email address to your service. Your service would get leads by filtering by email address to get the ids of each lead, trigger the request campaign for each lead id you get.

You may have have to throttle your api calls to marketo.

SanfordWhiteman
Level 10
October 15, 2018

Do all these people qualify for the campaign in the first place? (And then are only removed from the send because of the antispam dedupe.)

If so, it's easy to bypass the dedupe and send them each a personalized email. No extra API calls or 'hooks (much as I love 'em) necessary.

Scott_McKeighe2
Level 4
October 15, 2018

We've been ruminating over a primary/master contact object to deal with this on the Salesforce side, but it sounds like you have a more elegant solution!

SanfordWhiteman
Level 10
October 15, 2018

You have the same situation where you want to send to people who would otherwise be filtered out by the send-time dedupe?