I’ve seen some buzz lately about an email Leadpages sent out announcing a change in the way they integrate with Keap, formerly known as Infusionsoft. (What’s Leadpages?)
This announcement naturally prompted a few questions, so I started doing some research. Questions and answers below:
What is the change?
Leadpages is changing how they Integrate with Keap, or, in their words, Keap is changing how they integrate.
Regardless, they’re switching from a form based integration to a tag based integration.
So, previously you’d build a LeadPage or a LeadBox and then choose one of your Keap forms to link it to; now you’ll build your LeadPage or LeadBox and then choose an Keap tag (or 10) that will be applied when this form is submitted. (Complete details here.)
Does this affect me?
Yeah, maybe. It definitely affects me.
Basically it affects anyone who is using Leadpages to connect to Keap, and has built Drag and Drop Landing Pages, or LeadBoxes with their drag and drop editor.
From what I can tell, this does NOT affect pages or LeadBoxes built using their standard builder.
Do I have to do anything?
Again, probably.
If you have forms that are affected by this change you’ll want to decide what to do with them by November 30th.
My understanding is that you can either switch them to the new tag based integration (which basically means they’d be applying a tag in Keap instead of achieving a web form goal), or, if you were using the Drag and Drop LeadBoxes, you can switch them to a Standard LeadBox.
Here’s a video that talks you through all of this, let me know if you have any questions, or if I overlooked something:
Note: This method of using Standard LeadBoxes with the drag and drop builder has been working for me lately, but it’s possibly that at some point Leadpages or Keap will stop supporting this style of integration as well.
At some point I’m going to switch to using the Keap Landing Page Builder entirely (see a demo here), but I don’t see that happening any time soon.
It’s come a long ways, but Leadpages is still a ways ahead in terms of feature-to-feature functionality.
So dang helpful.
Thanks for reading homie. Hope you’re having a great trip.
Greg, thank you for this!
Question: What are your thoughts on bot detection and LeadPages? LeadPages will not work with Infusionsoft’s solutions for this, but they don’t seem to offer their own solution. Have you experienced any issues with this, as we have? Any suggestions or other thoughts?
And, a Side Note: Sometimes you offer free content so good –like this– that it makes me want to pay you something for it! Don’t know if you’d ever consider adding a “Tip” button somehow, or if you wouldn’t care for that — but I for one would use it!
Hey Troy, that’s a really interesting idea. I hadn’t thought about letting people tip for the content I put out! I do have my paid courses and my membership group – if you like this type of stuff, the membership may be of interest to you. If you like this type of stuff, and want to “tip”, feel free to share it! That always helps me out!
Oh, and to answer your question more directly: I don’t have a strong opinion on bot detection through Leadpages, it hasn’t become an issue for me yet, so I’ve sort of been thinking “I’ll cross that bridge eventually”. I have heard of people having good luck with the WP plugin Sucuri, but not sure how that’d work with LP specifically.
This is awesome – thanks so much for putting this resource together!
My pleasure, thanks for reading Paige!
My issue with any kind of API-based landing page is that the following either don’t work at all, or need a major science project:
– Bot detection: any API-based opt-in won’t benefit from Infusionsoft’s bot and spam detection. So unless the software provides their own protection, be prepared for lots of Russian spammers!
– Lead source tracking: I’ve yet to see any API-based landing page platform give you a way of tracking Google Analytics utm parameters and enter this data in the the Infusionsoft lead source fields. That’s a big fat fail for me.
– Referral partner tracking: unless you take advantage of Infusionsoft’s work-around (and only if the landing page platform specifically supports the ?affiliate= URL parameter), you won’t be able to track which affiliate sent your new contact to the landing page. No thank you!
So I’ll stick with HTML integrations for now, thank you very much 🙂
If you rely on any of the above-mentioned features, be VERY wary of moving to the new integration and do lots of testing!
GREAT points Adrian. All very valid considerations. Thanks so much!
Greg you are the man! Was struggling with this!
All good Dimitri! Thanks for reading. Hope you’re well!
So, how do they handle email compliance with the tag based system?
We have a large list and a few times our email sending ability was blocked until we could PROVE to IS that all of our leads were valid.
They were looking for the source of the leads and generally leads that submitted a web form, were fine, but leads that got in through the API were a much harder case to proof.
I would strongly recommend to make sure you use webforms instead of the API and tags. It’s very easy to have a run-in with the IS compliance team – even if you do everything by the book.
Ugh. Fair question. I haven’t personally had any issues with leads added through the API for my other integrations (PureChat, WebinarJam, etc); but what you’re saying is definitely worth consideration. I guess I’d be clear about what tags are being applied, and document where those are coming from as best you can. Maybe the first step in the campaign once they’ve been added should be a note to document their entry point and referring URL?
Is it possible to somehow get the referring URL without manually hardcoding it? You would need a separate tag for each “form”, wouldn’t you?
Would this help handle that?
https://youtu.be/8z48XJscenI
THANK YOU!!! This was very helpful and no doubt saved me a ton of time. You’re a great teacher. 🙂
Hey, my pleasure Jenny! If you know anyone else who it may benefit, please feel free to share!
AWESOME summary – THANK YOU for sharing the action steps to getting this fixed Greg, I’ll be sharing this with our clients.
You are welcome Mandy. Quite welcome indeed.
Hey Greg,
Thank you for putting this together. We sadly were caught out mid-launch by this scenario. We tried all the work arounds and they don’t seem to be functioning now. Seems like the standard pages and boxes are now slowly being disabled, as you indicated may happen.
Our biggest issue was the affiliate tracking, of course! Thankfully our product is ultimately sold via an interview to ensure compatibility, so we are able to ask where they learned about us.
Has anybody else recently experienced this after having implemented the work around?
Thanks!
Quinn
Oh man, I haven’t heard anything about the standard LeadBoxes being disabled, I really hope that’s not the case already. I’m sorry your launch was affected, that’s a bummer. I’m guessing Leadpages support hasn’t been able to save the day?
Well, we working overnight to try to correct things and we just decided we had to keep the customer front and centre with proper opt-ins and registrations and thus reverted to the regular drag and drop lead box. So, we will now circle back and see if LP support can help.
Thanks for your support and work, Greg!
My pleasure. Good luck!