Skip to main content
Itay_Billet4
Itay_Billet4
Level 8
May 24, 2017
Question

Lead Cleanup

  • May 24, 2017
  • 3 replies
  • 2467 views

Hi Team, I'm trying to identify leads that shouldn't be relevant to the SDRs based on the lead's common fields (name, company name, email and phone). For example: we saw a lead appear as:

  • Last Name : a
  • Company name: a
  • Email: a@b.com
  • Phone:  1232132434

We want to mark these leads in a certain status, so they won't be visible to the SDRs.

I saw the existing discussions in the community that were very helpful (Invalid Lead Cleanup , http://developers.marketo.com/blog/how-to-clean-your-marketo-database/ ) , but I was wondering if someone was able to enhance that.

Many Thanks!

Itay

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

    3 replies

    Devraj_Grewal
    Devraj_Grewal
    Level 10
    May 24, 2017

    Itay,

    For complete spam leads like these, I would just delete them altogether so they don't count towards your database limit. If you need to keep them for some other reason, I would create a lead status so they can be easily identified by Sales. I would also mark them "marketing suspended: true" so you don't accidentally include them in an email send.

    SanfordWhiteman
    SanfordWhiteman
    Level 10
    May 24, 2017

    What's specifically bad about a@b.com, though?

    OK, b.com in particular can't receive mail because it has no mailserver.  But a@z.com, a@i.net and a@a.org are all publicly sendable mailboxes. Similarly, I routinely fill out forms with my initials -- that doesn't mean I'm a fake lead.  213-2434 is a legitimate phone number.

    Just sayin': a single value or even multiple values can't always tell you if a lead is bogus.

    That said, if you can articulate what you're trying to catch, there will usually be ways to do it so the lead can be discarded. For example, "Domain has no MX record" is a rule that would catch a@b.com. "First three digits don't exist as a North American area code" would catch 1232132434.

    Itay_Billet4
    Itay_Billet4Author
    Level 8
    June 1, 2017

    Thanks @Sanford Whiteman​, that's very helpful.

    ow do you catch these kind of messages? (i.e. "Domain has no MX record")

    SanfordWhiteman
    SanfordWhiteman
    Level 10
    June 1, 2017

    For a batch lookup, by exporting and running a command-line check (dig/nslookup) and reimporting.

    In a trigger I would use FlowBoost, something to the tune of:

    var domainMatch = {{Lead.Email Address}}.match(/@(.+)/),
        domain;
    if ( !Array.isArray(domainMatch) ) {
      failure('No domain found in email address');
    } else {
      domain = domainMatch.pop();
      FBUtil.dns.resolveMx( domain );
      // ... etc...
    }
    Darrell_Alfons2
    Darrell_Alfons2
    Level 10
    May 24, 2017

    Create a new lead status called Junk.

    Create a workflow in Marketo or Salesforce when a lead is changed to junk status, to automatically assign it to a holding user, or delete.

    Terms & ConditionsAccessibility statement

    Loading footer...