Andy Cook

We’ve admittedly had trouble with Ajax/Javascript form submissions since we started Leadin. Do you mind sharing the URL of the form that’s not working correctly? I can’t make any promises that we’ll be able to fix it in the short term, but we’re launching a new version of our form parsing script in a month or so that I hope will permanently take care of this issue. If you subscribe to our product updates you should hear about the changes we’re working on when they are live.

@matiasgys – we’re starting to think about how we could empower our users to update the information on their own, but it’s admittedly on the backburner for awhile.

If you want to email me with your corrected company information, I can manually update it for you until we have this feature.

1. Leadin Pro originally was supposed to be a paid upgrade, but we managed to get funding from our parent company to continue optimizing for growth of the plugin instead of revenue. You can read more in the “Why Free?” section of this blog post – http://leadin.com/pro-upgrade

The eventual plan is to have a paid version, but we’ll always use a freemium model where you get some of the functionality for free. We’re generally generous people, so we 100% have no plans to give Leadin for free, then hold everyone ransom to keep using it until they pay us. We’ll most likely come up with a fair pricing model based off usage.

2. We don’t have a baked in away to export contact’s activities on an individual basis. How are you assessing the contacts? We honestly haven’t figured out how to showcase that amount of data in way that makes sense inside of CSV export. If you really needed to export your data, you should be able to do so via MySQL by just exporting the entire li_leads, li_submissions, li_pageviews, li_tags and li_tag_relationships tables.

3. We don’t have a way to import contacts right now because we wouldn’t be able to tie the tracking code to that AWeber user easily. We do have a couple of ideas of how to make this happen though, so stay tuned.

Thanks for the nice review and I hope I answered all your questions. Please do feel free to ask me anything else. Cheers!

This issue should be fixed as of Leadin Pro 3.1.3. There is one small glitch where I still need to namespace the oauth files libraries which connect to AWeber, but it should be working now except for a few outlier instances.

Thanks for your feedback via your review. We really do appreciate your thoughts and I’ll try to address each point here with how we’re working to make the plugin work better for you.

We do collect usage data in the Pro version of the plugin because it helps us build a better product that is more reliable and can work across the different PHP, MySQL and WordPress version permutations that exist. We <b>never</b> collect data about your visitors and contacts. We are actually working with our lawyers on a Terms of Service and Privacy Policy that lays out what kinds of data we are collecting and how we are using it. It’s admittedly slow going and we hope to have that out in the next few weeks.

As for the blank record contacts, it looks like you uncovered a bug through a use case we didn’t anticipate. Leadin using an algorithm to merge submissions by the same contact together over different browsers. It sounds like in certain circumstances you’re receiving a form submission from a person in one session which triggers an email, and then that same person submitted a second form in a different browser, so Leadin merges the data from the first session into the second, and deletes the original contact. If you click through the email from the first submission, it’ll show up as a broken contact. It’s a good point and I’ll try to write an automatic redirect to the most up-to-date contact record soon. Thanks for reporting that bug.

Hooking into Gravity Forms spam filters is also a good idea and I’ll look into it.

I have to agree with you on your conclusion – that Leadin is a good start. We built the entire original version of the plugin with only two people, and there are admittedly issues and we’re missing some functionality. That’s why the plugin is free right now – because we’re still working out the kinks. We know it’s not perfect and we’re working as hard as humanly possible with our resources to improve Leadin as quickly as we can to get it to a point where it meets later-adopter’s standards. We released early and often so we made sure to actually build something that people wanted instead of trying to get it perfect from the start, which we knew we wouldn’t if we built the product in a closed box. Thanks again for the feedback – we’re working hard to address all your concerns and hopefully over time we’ll have a product that provides the type of experience you expect.

Thanks for the A/B testing idea. I think that’s an interesting one as well and I wrote it down to discuss as we decide what we’re building into the populs tool next. Cheers!

It seems like we’re running into a conflict with Elegant Themes. I just bought their suite of plugins and will look into what is happening here on my work computer tomorrow when I have access to my local development environment. Thanks for letting us know and I’ll circle back here tomorrow with what I can find.