Jump to content


Photo

Web form not creating new lead

leads webform

  • Please log in to reply
7 replies to this topic

#1 eugeneb

eugeneb

    Advanced Member

  • Members
  • PipPipPip
  • 317 posts
  • LocationCenturion, south Africa

Posted 24 March 2016 - 06:05 AM

Hi guys,

 

my x2 is for some reason not creating a Lead from a web form. I tried everything I could see. On the form it's selected including a lead source. But when completing the form, the contact is created but not a lead. Also no notifications are sent.

 

Can you advice please.

 

Thanks

 

Eugene



#2 eugeneb

eugeneb

    Advanced Member

  • Members
  • PipPipPip
  • 317 posts
  • LocationCenturion, south Africa

Posted 28 July 2016 - 04:23 AM

Hi guys,

 

i am still struggling with this. My web-forms arent generating leads or basically any settings related to the webform creation such as adding tags or email the user or so. The contact however is created correctly.

 

please help with any advice.

 

Thanks



#3 alt_f4

alt_f4

    Advanced Member

  • Premium Members
  • PipPipPip
  • 325 posts
  • LocationGermany

Posted 02 August 2016 - 01:06 AM

Got (maybe) a similar problem: http://community.x2c...pdated-weblead/



#4 eugeneb

eugeneb

    Advanced Member

  • Members
  • PipPipPip
  • 317 posts
  • LocationCenturion, south Africa

Posted 02 August 2016 - 05:35 AM

Hi Alt-f4,

 

the forum url is locked by password. Think its for Premium Members maybe.

 

Have you got the solution for the problem?

 

^_^



#5 alt_f4

alt_f4

    Advanced Member

  • Premium Members
  • PipPipPip
  • 325 posts
  • LocationGermany

Posted 02 August 2016 - 05:46 AM

Oh, sorry, here´s a copy of my post. Unfortunately no solution...

 

 

We´re using webleads to send out some brochures using the trigger "New Weblead".

 

Form:

 

asks for some data like mail etc. and X2 creates a new contact. Also X2 tags the contact with "new info request".

 

Flow:

 

New weblead -> if the tag "new info request" is found, a mail is sent to the contact.

 

If the weblead is new, everything works fine.

 

But if an existing contact fills in a form, the trigger isn´t pulled --> how to realize, that also an existing record gets triggered (and a mail is generated), if the weblead is filled out?

I want to use the flow module, to get more control -- like wait 5 minutes to send the email and do some other stuff. The "weblead inbuild" feature to directly send an email is not useable for us.



#6 X2Raymond

X2Raymond

    Advanced Member

  • Administrators
  • 972 posts
  • LocationSanta Cruz, CA

Posted 02 August 2016 - 02:10 PM

Answered in other thread, pasted here for community:

 

 I've just looked into this one and it appears that triggering on new webleads has been hardcoded in the WebFormAction. To trigger on existing leads, remove the condition around line 206:

if($newRecord) { 
    X2Flow::trigger( 
        'WebleadTrigger', array('model' => $model, 'tags' => $tags)); 
}

It might make sense to make this option configurable in the future.

 

Eugene, can you confirm whether this behavior may also be related to existing records?

 

Raymond



#7 eugeneb

eugeneb

    Advanced Member

  • Members
  • PipPipPip
  • 317 posts
  • LocationCenturion, south Africa

Posted 03 August 2016 - 05:05 AM

Hi Ray,

 

It doesnt seem to be related to new or existing contacts for me.

 

I tested by placing two forms on a 'hidden temp page' - http://www.codingfor...za/x2-webform/ 

 

I completed the forms with new contact details as well as existing details.

  • The new contact details created a csrf token error.
  • The existing contact wrote 'background field info back into the form.

This is on our coding-for-kids site. On our primary site it seems to work.

 

Not sure if this info help at all.

 

Eugene



#8 X2Raymond

X2Raymond

    Advanced Member

  • Administrators
  • 972 posts
  • LocationSanta Cruz, CA

Posted 03 August 2016 - 10:22 AM

Hi Eugene,

 

To avoid being picked up as a dupe by the fingerprinting system, you might want to test in another browser or remove your existing fingerprint data from the system.

 

Regarding the CSRF token error, this is usually due to a combination of client browser settings and domain the web form is served from. Moving the second form to a subdomain of your coding-for-kids domain should resolve the CSRF token error.

 

Raymond







Also tagged with one or more of these keywords: leads, webform

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users