Customobject record is linked to inactive email address | Community
Skip to main content
R
raochikati
Level 3
April 21, 2025
Solved

Customobject record is linked to inactive email address

  • April 21, 2025
  • 1 reply
  • 690 views

Hi,

I have an use case, Marketo is linking customobject record to an inactive email address

  1. Customobject is defined with email address as linking field
  2. An unique Id as de-dupe field

When I bulk import data to Customobject, Marketo is linking the CO data to an inactive email address(There are dupe email addresses) because of which active email address is not showing up in the list derived by a smart list.

 

I would not be knowing email address status at the time of bulk import  data. Is there any way we can force Marketo not to link CO data to an inactive email address?

 

 Thanks,

Babu

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by SanfordWhiteman

“Inactive email address“ isn’t really a concept in Marketo.

 

A person’s Email Address may be invalid, but that doesn’t stop that person from being related to a custom object record. As long as they’re in your database, they’re as “active” as any other person.

 

In general, if you have duplicate people with the same Email Address, it is not safe to use Email Address as a link field because you cannot predict which person will be linked upon CO creation — and note it will be only linked to one person in the duplicate set. You should use ID or another guaranteed-unique field.

1 reply

SanfordWhiteman
SanfordWhitemanAccepted solution
Level 10
April 21, 2025

“Inactive email address“ isn’t really a concept in Marketo.

 

A person’s Email Address may be invalid, but that doesn’t stop that person from being related to a custom object record. As long as they’re in your database, they’re as “active” as any other person.

 

In general, if you have duplicate people with the same Email Address, it is not safe to use Email Address as a link field because you cannot predict which person will be linked upon CO creation — and note it will be only linked to one person in the duplicate set. You should use ID or another guaranteed-unique field.

    R
    raochikatiAuthor
    Level 3
    April 21, 2025

    Thank you, Sanford!

     

    I will check on if there is an Id which can be used as link field. I believe I need to come up with new CO to have link field updated to new field(s), that means changes in campaign logic if existed any.

     

    Thanks,

    Babu

      Terms & ConditionsAccessibility statement

      Loading footer...