Help Identifying Records with Updated Emails After Hard Bounce in Marketo after 90 days | Community
Skip to main content
A
akshat_goyal
Level 3
June 12, 2025
Solved

Help Identifying Records with Updated Emails After Hard Bounce in Marketo after 90 days

  • June 12, 2025
  • 1 reply
  • 1459 views

Hi,

 

We’ve encountered an issue in our Marketo instance where several person records are still marked as Invalid due to a hard bounce on an old email address. However, these records have since had their email addresses updated via CRM sync.

For example, a record originally had the email akshat@efgh.com, which hard bounced and marked the record as Invalid. Later, the email was updated to akshat@abcd.com, but the Invalid flag remains.

The Challenge: There doesn’t seem to be a straightforward way to create a Smart List that identifies records where:

  • The current email address is different from the one that triggered the hard bounce.
  • The record is still marked as Invalid.

I attempted to use the {{lead.Email Address}} token in the Email Bounce activity filter, but it returned no results—likely because tokens aren’t supported in that context.

The Ask: Is there a way—perhaps via the Marketo API—to:

  1. Retrieve the email address associated with the Email Bounce activity.
  2. Compare it to the current email address on the record.
  3. Identify records where the bounce was tied to a previous email, not the current one.

This would help us clean up our database and ensure valid records aren’t incorrectly flagged.

Any guidance, workarounds, or API tips would be greatly appreciated!

 

I tried marketo api as well but it is not giving me the data that i am looking for? 

 

Thanks in advance!

Best answer by PeeyushSachdeva

Hi @akshat_goyal,

 

You're absolutely right—this is a known challenge in Marketo. The Invalid flag is sticky and does not automatically reset when the email address is updated, because it reflects the email deliverability status for that person ID, not necessarily the current email address.

 

  • The Email Bounced and Email Bounced Soft filters do not support tokens (like {{lead.Email Address}}), so you can’t dynamically compare past vs. current email.

  • Marketo does not track email address history natively in the UI.

 

Workaround:

  1. Use the Activity API to pull Email Bounced activities.

  2. Each activity includes:

    • leadId

    • The email that bounced (details field contains this)

    • The bounce reason and timestamp

  3. Compare this email (the one that bounced) to the current email on the lead (retrieved via Get Lead by Id or Get Lead by Email endpoint).

  4. If the bounced email ≠ current email AND the lead is still marked Invalid ("invalid": true), you’ve found a record for revalidation.

  • Pull leads where invalid = true

  • For each, check recent Email Bounced activity

  • Compare bounced email vs. current

  • Flag mismatches for review/reset

1 reply

PeeyushSachdeva
PeeyushSachdevaAccepted solution
Level 4
June 12, 2025

Hi @akshat_goyal,

 

You're absolutely right—this is a known challenge in Marketo. The Invalid flag is sticky and does not automatically reset when the email address is updated, because it reflects the email deliverability status for that person ID, not necessarily the current email address.

 

  • The Email Bounced and Email Bounced Soft filters do not support tokens (like {{lead.Email Address}}), so you can’t dynamically compare past vs. current email.

  • Marketo does not track email address history natively in the UI.

 

Workaround:

  1. Use the Activity API to pull Email Bounced activities.

  2. Each activity includes:

    • leadId

    • The email that bounced (details field contains this)

    • The bounce reason and timestamp

  3. Compare this email (the one that bounced) to the current email on the lead (retrieved via Get Lead by Id or Get Lead by Email endpoint).

  4. If the bounced email ≠ current email AND the lead is still marked Invalid ("invalid": true), you’ve found a record for revalidation.

  • Pull leads where invalid = true

  • For each, check recent Email Bounced activity

  • Compare bounced email vs. current

  • Flag mismatches for review/reset

    A
    akshat_goyalAuthor
    Level 3
    June 12, 2025

    I tried this below payload for the get api 

    { "format": "CSV", "filter": { "createdAt": { "startAt": "2023-12-13T23:59:59-00:00", "endAt": "2023-12-16T23:59:59-00:00" }, "activityTypeIds": [ 6 ] } }

    but thing is i am only getting 1 month of data at a time, not abel to extract more than 1 month of data, and i am not abel to extract the email ID with this api. - /bulk/v1/activities/export/create.json @peeyushsachdeva 

    Terms & ConditionsAccessibility statement

    Loading footer...