Andy Cook

Hi David –

Thanks for the positive words and encouragement 🙂

Leadin should start tracking your visitors as soon as you activate the plugin inside your WordPress dashboard. The 30 day window that I think you’re referencing is only on the stats dashboard, which shows your contacts from the last 30 days. Even if a contact was created over 30 days ago, Leadin will still track that contact indefinitely. We created a help document explaining in more detail how Leadin tracks visitors if you’d like to learn more.

As for your WordPress.com dashboard showing new users that Leadin didn’t catch, that could be due to a number of things. Leadin should work with most WordPress form plugins and custom built HTML forms. The only exceptions are forms that are not enclosed in a HTML <form> tag or if the form is loaded through an iFrame. If the form submits through Javascript we can’t detect that it’s a form, or if it’s an iFrame we can’t detect the submission because of cross site security reasons. So it could be that one of your forms that hooks into WordPress.com isn’t being tracked for the two reasons I mentioned above.

That’s strange that the Leadin popup doesn’t work after you toggled it off then on. Off the top of my head, that could be caused by one of two reasons:

1. Does your theme call the wp_footer method anywhere? It sounds like it does if the popup was working initially which leads me to believe the popup isn’t showing for reason #2, but if you removed the call to that method since turning off the Leadin popup it would prevent our scripts from being included. Usually you’ll see a call in your main theme to get_footer, which includes the footer.php file. Inside of footer.php is where wp_footer() is usually called. Leadin’s javascript files are loaded in the WordPress footer and if wp_footer is never called in your theme, the Leadin scripts fail to loaded properly.

2. Can you trying clearing all your caches cache and then load the page to see if it works on a fresh page build?

I hope I answered all your questions and please let me know if I missed anything. Always happy to help our users better understand how Leadin works from a technical perspective and get the kinks straightened out.

Cheers!

Hi Jeff –

Thanks for the kind words about Leadin 🙂

Do you mind posting the URL for the site that doesn’t seem to working here or email it directly to support@leadin.com?

Off the top of my head without seeing the actual source code for the site, this could be caused by a few different issues:

Is the form housed in an iFrame or is the form submitted with a jQuery submit event? Leadin should work with most WordPress form plugins and custom built HTML forms. The only exceptions are forms that are not enclosed in a HTML <form> tag, if the form is loaded through an iFrame or if there is already a jQuery submit event attached to the form that overrides our own parsing logic. If the form submits through Javascript we can’t detect that it’s a form, or if it’s an iFrame we can’t detect the submission because of cross site security reasons.

The other issue off the top of my head is that the Leadin scripts might not be included in your page source. Can you please inspect the HTML source code for your page and make sure the leadin-tracking.min.js file is included? If it’s not, it might be one of two reasons:

1. Does your theme call the wp_footer method anywhere? Usually you’ll see a call in your main theme to get_footer, which includes the footer.php file. Inside of footer.php is where wp_footer() is usually called. Leadin’s javascript files are loaded in the WordPress footer and if wp_footer is never called in your theme, the Leadin scripts fail to loaded properly.

2. Can you trying clearing all your caches cache and then load the page to see if it works on a fresh page build?

Let me know what you find and we’ll go from there.

Sorry for the issue. It sounds like there is a database error with your Leadin tables. This usually happens if one of the Leadin tables crashes or a funky character breaks on of the MySQL queries for the contact list.

Do you mind creating an administrative login for andy@leadin.com? I’m happy to take a look to get to the bottom of this for you. Thanks in advance.

I’m so sorry Leadin crashed your site and took down your front-end as well as your WordPress Dashboard. Our team has tried really hard to build a stable, reliable plugin that can run on any permutation of WordPress, PHP, and MySQL while avoiding conflicts with the tens of thousands of plugins that exist, but the reality of the situation is that it’s impossible for us to predict every issue before it happens. I can assure you though that we take situations like this very seriously and will be looking into why Leadin caused your server to crash.

Usually this is the result of a PHP error, like when two plugins have the same function name or are using the same third-party library. We try very hard to follow all the best practices of WordPress development, including writing object oriented code, appending all our shared functions with a “leadin_” prefix, and “namespacing” all our third-party libraries with “LI_” to avoid conflicts with other plugins. I’ll be the first to admit we are not 100% perfect, as evidence in this situation we’re we let you down. I want to say I’m sorry, and we’re working towards improving the stability of the plugin. The first steps we took is admitting our tiny, two-person team isn’t equipped right now to build a plugin of Leadin’s power – while doing it all for free – so we’re brought on three more “real” engineers recently who will be working to make the backend of Leadin more reliable by moving off some of the more advanced functionality off your local WordPress server and onto the cloud. This should really cut down on conflicts with other plugins, MySQL query timeouts, or any of the other hundreds of issues we encounter by building on the WordPress stack.

I can assure you we’re working as hard as we can to build the most reliable and powerful inbound marketing tool for WordPress while keeping it free. We messed up in this situation, and I’m sorry. Thank you for your patience and support while we work to make the plugin better for all the WordPress users our there. I hope you understand what happened and I hope we can regain your trust soon. Please do let me know if I can make the situation right or if you have any suggestions for how we can improve – my personal email address is andy@leadin.com.

Hi Richard –

Right now Leadin doesn’t have the ability to create a tagged list based off a specific value in an form. It’s a good idea though, so I’ll mark it down as something to take to my team soon. I’ll circle back here as we make progress and let you know what shakes out.

Cheers!

Sorry for the issue. Do you mind sending andy@leadin.com a link to your form so I can take a look?

Also, what other plugins are you using in conjunction with Contact Form 7? To my knowledge, Contact Form 7 usually just shoots off an email with the contact information so it sounds like you have a separate plugin other than Contact Form 7 which is storing the contacts in the database.

For everyone reading this thread, we tested this site in a few different browsers and the forms seem to be working now. The most likely culprit was local caching which may have excluded the Leadin Javascript files originally.

I’m going to mark this ticket as resolved since the CSS code above should help you over ride the styles. Thanks for posting here so that future readers can find this answer.