Andy Cook

I’m going to mark this ticket as resolved because I haven’t heard back from you yet and one of the two fixes above will most likely take care of the issue. Please do let me know if it’s still not working for you and I’ll look into it more deeply.

Hi Scott –

I’m going to mark this issue as resolved because we recently started delivering your email notifications through SendGrid if you’re on Leadin Pro. The update should really help with deliverability and also save you some money by not eating into your Mandrill account. Let me know if that works for you or if you have any thoughts.

Cheers,
– Andy

To follow up with everyone else reading this thread, the issue here ended up being Backup Buddy not backing up the Leadin tables, so they got dropped. To fix this, all you need to do is manually recreate the tables:

CREATE TABLE li_leads (
lead_id int(11) unsigned NOT NULL AUTO_INCREMENT,
lead_date timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
hashkey varchar(16) DEFAULT NULL,
lead_ip varchar(40) DEFAULT NULL,
lead_source text,
lead_email varchar(255) DEFAULT NULL,
lead_first_name varchar(255) NOT NULL,
lead_last_name varchar(255) NOT NULL,
lead_status set(‘contact’,’lead’,’comment’,’subscribe’,’contacted’,’customer’) NOT NULL DEFAULT ‘contact’,
merged_hashkeys text,
lead_deleted int(1) NOT NULL DEFAULT ‘0’,
blog_id int(11) unsigned NOT NULL,
company_data mediumtext NOT NULL,
social_data mediumtext NOT NULL,
PRIMARY KEY (lead_id),
KEY hashkey (hashkey)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 AUTO_INCREMENT=1;

CREATE TABLE li_pageviews (
pageview_id int(11) unsigned NOT NULL AUTO_INCREMENT,
pageview_date timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
lead_hashkey varchar(16) NOT NULL,
pageview_title varchar(255) NOT NULL,
pageview_url text NOT NULL,
pageview_source text NOT NULL,
pageview_session_start int(1) NOT NULL,
pageview_deleted int(1) NOT NULL DEFAULT ‘0’,
blog_id int(11) unsigned NOT NULL,
PRIMARY KEY (pageview_id),
KEY lead_hashkey (lead_hashkey)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 AUTO_INCREMENT=1;

CREATE TABLE li_submissions (
form_id int(11) unsigned NOT NULL AUTO_INCREMENT,
form_date timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
lead_hashkey varchar(16) NOT NULL,
form_page_title varchar(255) NOT NULL,
form_page_url text NOT NULL,
form_fields text NOT NULL,
form_selector_id mediumtext NOT NULL,
form_selector_classes mediumtext NOT NULL,
form_hashkey varchar(16) NOT NULL,
form_deleted int(1) NOT NULL DEFAULT ‘0’,
blog_id int(11) unsigned NOT NULL,
PRIMARY KEY (form_id),
KEY lead_hashkey (lead_hashkey)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 AUTO_INCREMENT=1;

CREATE TABLE li_tags (
tag_id int(11) unsigned NOT NULL AUTO_INCREMENT,
tag_text varchar(255) NOT NULL,
tag_slug varchar(255) NOT NULL,
tag_form_selectors mediumtext NOT NULL,
tag_synced_lists mediumtext NOT NULL,
tag_order int(11) unsigned NOT NULL,
blog_id int(11) unsigned NOT NULL,
tag_deleted int(1) NOT NULL,
PRIMARY KEY (tag_id)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 AUTO_INCREMENT=1;

CREATE TABLE li_tag_relationships (
tag_relationship_id int(11) unsigned NOT NULL AUTO_INCREMENT,
tag_id int(11) unsigned NOT NULL,
contact_hashkey varchar(16) NOT NULL,
form_hashkey varchar(16) NOT NULL,
tag_relationship_deleted int(1) unsigned NOT NULL,
blog_id int(11) unsigned NOT NULL,
PRIMARY KEY (tag_relationship_id)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 AUTO_INCREMENT=1;

Hi there –

I just wanted to follow up that this should be fixed in the latest version of Leadin so I’m marking this topic as resolved. Thanks so much for reporting the issue.

If you want to add the Leadin tracking, just drop the following lines of code in your template file, preferably in the <footer> tag. If you don’t have a footer tag, just make sure you are including them after jQuery is loaded. You’ll need to change out the parts in bold with your WordPress URL:

<script type=’text/javascript’>
/* <![CDATA[ */
var li_ajax = {“ajax_url”:”http:\/\/your_domain.com\/wp-admin\/admin-ajax.php”};
/* ]]> */
</script>

<script type=’text/javascript’ src=’http://your_domain.com/wp-content/plugins/leadin/assets/js/build/leadin-tracking.min.js’></script>

Let me know if that doesn’t work for you and we’ll go from there. Cheers!

Thanks for letting us know about this issue and sorry about the issue. We recently did an update for our Leadin pro users that sends all your contact notification emails through an email delivery service instead of your default PHP mail server. The goal here was to increase the chances of your emails actually get through your spam filter and into your inbox. We admittedly ran into some issues with that upgrade, but have since figured them out.

So if you’re not already on Leadin 3.1.6, do you mind upgrading and then letting me know if the notification emails still aren’t sending? Thanks!

Thanks for the positive vibes 🙂

The popup should only show itself when the users scrolls 50% down the page. If it’s popping up immediately that’s probably because the page is short, so technically you’re already scrolled 50%.

A timed popup is a great idea. In fact, it’s such a great idea that we’re already working on adding a timed-popup option along with a few other improvements. I’ll make sure to mark you down on the list of people to contact when we get that featured launched.

Thanks for the suggestion and have a great day!