Webhook making an anonymous lead known | Community
Skip to main content
Grégoire_Miche2
Grégoire_Miche2
New Participant
March 27, 2017
Solved

Webhook making an anonymous lead known

  • March 27, 2017
  • 2 replies
  • 5374 views

Dear all,

We had a weird surprise today. A customer of ours has its database full of empty leads (no names, no emails). About 3000 of them. e.g.:

When looking at the activity logs of these leads, they all have in common to have navigated the web site and suddenly the score triggers have fired, following the ones that computes total score, which is done through a webhook (as you will see, all this happens in the same second...):

The very weird thing is that the detail of the "new person" activity shows that the lead was created by the webhook:

The smart campaign that call the webhook fires on the following triggers:

I just cannot make any sense of this!

All of these smart campaigns are not supposed to fire on anonymous leads in the first place, but only when the lead becomes known...

we have opened a support ticket, I'll let the community know.

-Greg

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 Mike_Reynolds2

Hi @Grégoire Michel

Can't speak officially for something I'm not personally familiar with, and webhooks were never really my personal strong suit. I'd have to defer to the Support ticket on this one.

As for the lead promotion part, the smart campaigns not triggering off of anonymous leads will only apply after the instance has been moved to Munchkin V2. Not all instances have actually been moved to Munchkin V2 yet. There was a rolling deployment of Munchkin V2. The removal of access to anonymous leads was done already, but the next step after that is the changeover to Munchkin V2, which is a more complicated upgrade being made and is taking time to implement. So if you're not seeing the Munchkin V2 behavior (anonymous leads go through trigger campaigns while still anonymous, not through the campaign replay activity used in Munchkin V2), then your instance likely hasn't been switched over yet.

2 replies

Grégoire_Miche2
Grégoire_Miche2Author
New Participant
March 27, 2017

Hi @Mike Reynolds,

Any insight and official statement here would be welcome, and probably necessary.

-Greg

Mike_Reynolds2
Mike_Reynolds2Accepted solution
New Participant
March 28, 2017

Hi @Grégoire Michel

Can't speak officially for something I'm not personally familiar with, and webhooks were never really my personal strong suit. I'd have to defer to the Support ticket on this one.

As for the lead promotion part, the smart campaigns not triggering off of anonymous leads will only apply after the instance has been moved to Munchkin V2. Not all instances have actually been moved to Munchkin V2 yet. There was a rolling deployment of Munchkin V2. The removal of access to anonymous leads was done already, but the next step after that is the changeover to Munchkin V2, which is a more complicated upgrade being made and is taking time to implement. So if you're not seeing the Munchkin V2 behavior (anonymous leads go through trigger campaigns while still anonymous, not through the campaign replay activity used in Munchkin V2), then your instance likely hasn't been switched over yet.

    Grégoire_Miche2
    Grégoire_Miche2Author
    New Participant
    April 4, 2017

    Hi Mike,

    The issue is that we have no clue whether or not a given instance has been upgraded. And honestly, more than a year after the announcement, I am very surprised that not everyone has been upgraded yet. Furthermore, there is no calendar available, and we find out the hard way, which is, IMHO, not the best of customer friendliness

    -Greg

    Grégoire_Miche2
    Grégoire_Miche2Author
    New Participant
    March 27, 2017

    Here is the answer from support:

    "In order to prevent anonymous leads from going through campaigns that call webhooks, which in turn convert the lead records to "known" leads, I would recommend adding a filter to the smart list of any campaign calling a webhook. This filter can be anything like Email or First name > Is Empty. You'll want to use some filter based on a field that you know anonymous leads will have empty, so that adding the filter to your campaign's smart list will keep them from getting to the webhook flow step."

    The fix is easy, but this is really amazing to me since nowhere I have read that webhooks could make an anonymous lead known!

    -Greg

    Dan_Stevens_
    Dan_Stevens_
    New Participant
    March 27, 2017

    Thanks for sharing this with us, Greg.  I, too, didn't think this was possible to create a new lead from an anonymous lead.  I need to ensure this isn't happening to us!

    Grégoire_Miche2
    Grégoire_Miche2Author
    New Participant
    March 27, 2017

    That would be a funny way to come back to Marketo previous behavior, when the anonymous leads were accessible. Just create a dummy webhook that updates a field and call it on a "visits web page" trigger. That would make all web page visitors known... And also probably kill the performance of you instance if you have some volumes.

    The database size would increase dramatically, though, but if I remember well, the contract says that only the leads who can be reached (email, phone, address) really count. So these ones would not...

    -Greg

      Terms & ConditionsAccessibility statement

      Loading footer...