If you read the opening post of Product Marketing Month, you would have read about the concept of Productizing Our Technology (POT).
Productizing Our Technology
By taking our core tech, combining the available features, with new jQuery scripts, CSS, and some 3rd-party integrations, it’s possible to create a plethora of new “mini-products” that if embraced by the community, could inform future product direction.
When we created an initial list of product ideas, expanding upon what the base product can already do, I realized that — as we’ve moved from a single product to multiple — we’d not changed our perception of who the functional buyer persona is.
If you look at the table below, notice how product #1 is a standalone landing page used primarily for paid ad campaigns, but products #2 and #3 are designed to be used primarily on your website.
|#1 Landing Pages||#2 Popups||#3 Sticky Bars|
|Primary Use Case||Use standalone landing pages to convert more of paid (AdWords) traffic.||Use on website pages to convert more organic traffic.||Use on website pages to convert more organic traffic.|
|Primary Persona||Campaign Strategist||Website Owner||Website Owner|
|Secondary Persona||Designer||Campaign Strategist||Campaign Strategist|
|Tertiary Persona||Copywriter||Web Designer / Developer||Web Designer / Developer|
Note: that for the personas listed, these are intentionally general, as it’s still part of our discovery. My goal is simply to show that they are most likely different.
We didn’t immediately realize that the teams using these products may not even be in the same department (marketing vs. web team vs. software development), for example. Or if they are in the same department (marketing), they might not work together on a daily basis.
This is a huge problem because it assumes that someone who runs paid campaigns is also going to be optimizing the organic traffic to a website, and is no doubt one of the reasons for low adoption of product #2 and #3.
A WTF Moment – How Could We Be So Blind?
When we talked to our customers and community members, we uncovered a startling fact: most people thought that the new products could only be used on Unbounce landing pages.
WUUUUTTTT! Not true.
Yes, you can, if you want. But the primary use case for the new products is for your website. We really didn’t see this misconception coming, which shows how important it is to always talk to your customers.
Who uses your products?
If you have more than one product, or if the users of your single product have different job roles, are you targeting and communicating with them in different ways? Or have you assumed that everyone will understand the same messaging?
Web developers are not very likely to be downloading an ebook about marketing, and thus will not be on our mailing list to hear about new products that could, in fact, make their job easier and more productive.
So, today, I’m going to share some of the functional use cases of popups and sticky bars that would be used by the UX and web teams that work on and manage your website. This is a very different market than we normally speak to, but super important as some of our research has indicated after the initial launch.
As I explore these use cases, try to follow along with your own products, to see if there are ways that you can create new mini products from the technology you possess.
Across the top (in yellow) are the core products, their features (such as targeting, triggers, display frequency), and the different hacks, data sources, and integrations, that can be combined to produce the new products listed in green in the first column.
To recap, each mini product is labelled as either NOW/MVP/NEW depending on how easy it is to create with our current tech:
NOW: These products are possible now with our existing feature set.
MVP: These products are possible by adding some simple scripts/CSS to extend the core.
NEW: These products would require a much deeper level of product or website development to make them possible. These are the examples that came from “blue sky” ideation, and are a useful upper anchor for what could be done.
The core technology is denoted as LP (Landing Pages), POP (Popups), SB (Sticky Bars).
In the table below you’ll find 25 of the ideas we came up with — that I selected from of a total of 121.
|#||Product Name||Product Description||Where Used||Core Tech||Core Features||Extras|
|NOW: Can be built with existing features|
|1||Microsites||By using the URL targeting feature, a single Sticky Bar with links to multiple Landing Pages can effectively create a microsite.||Landing Pages||LP + SB||Targeting: URL
|2||EU Cookie Law Bar||You’ve probably seen them all over the place. “All websites owned in the EU or targeted towards EU citizens, are now expected to comply with the law.” The EU has always been very strict and this requirement is why these bars have been popping up everywhere. Good news is, they’re wasy to make with geo-targeting.||Website||SB||Targeting: Geo
|3||Two-Step Opt-In Form||Instead of showing a lead gen form, you use a button or link that shows the form in a popup when clicked. This can help remove the perceived friction that a form conveys, and applies a level of commitment when the button is clicked that makes people more likely to continue and fill out the form.||Website, Landing Pages||POP||Trigger: Click||N/A|
|4||Cart Abandonment||Use an exit Popup on your ecommerce product/cart/checkout pages to provide an offer to encourage a purchase.||Website||POP||Trigger: Exit||N/A|
|5||Multi-location GEO Redirect||If you have websites for multiple countries, you can present the entry Popup that uses geolocation to ask if the visitor would like to visit the site in their own country.||Website||POP||Targeting: Geo
|6||Poll/Survey||Add a form to a Popup of Sticky Bar to present poll or survey questions.||Website||POP or SB||Trigger: Entry, Exit, Scroll Down, Scroll Up, Delay||N/A|
|7||NPS Survey||Present a Net Promoter Score in a Sticky Bar to ask your visitors and customers to rate how likely they are to recommend your product or brand to others.||Website, Landing Pages||SB||Targeting: None, Cookie
Trigger: Exit, Scroll, Delay
|8||Outage Notification||Present an entry Popup or Sticky Bar when there is site maintenance happening.||SB or POP||Website||Targeting: URL, Cookie||N/A|
|9||Tooltips||Present a popup when someone clicks to show more info/instructions.||Website, Landing Pages||POP||Trigger: Click||N/A|
|10||Referrer Contextual Welcome||Present a contextually relevant message to people arriving from another site.||Website, Landing Pages||POP or SB||Targeting: URL, Cookie, Geo
|11||Co-marketing Contextual Welcome||Present a contextually relevant message to people arriving from a campaign run by you and a comarketing partner. This could show the relationship (both logos) and the joint offer.||Website, Landing Pages||POP or SB||Targeting: Referrer, URL, Cookie
Trigger: Entry, Scroll Up, Scroll Down,
|12||Mobile GPS: Closest Store||Present a Sticky Bar when someone on a mobile site would benefit from knowing where the closest store is to them (potentially with an incentive to visit the store).||Website, Landing Pages||SB||Trigger: Entry, Scroll Up, Scroll Down,
|13||Holiday Hours Announcement||Show details of changes in store hours. Could be used on exit to provide some urgency “We’re closing in 1 hour”.||Website, Landing Pages||SB or POP||Trigger: Entry, Exit||N/A||MVP: Can be built with existing features|
|14||Sticky Navigation||By removing the standard close button [x] from a Sticky Bar and adding smooth scroll anchor links, you can create a sticky navbar which can help increase page engagement.||Website, Landing Pages||SB||Trigger: Entry||CSS: Hide close button
|16||Mobile Hamburger Menu||A hamburger menu is the three lined icon that opens up a navigation menu. They typically slide in and out from the left side or top.Check out a demo in the Unbounce Community.||Mobile Website||SB||Trigger: Click||jQuery: Slide in/out|
|17||Progress Bar||Similar to a microsite, a progress bar could be targeted to appear on several pages. Using cookie targeting and CSS the progress bar could be updated to show which pages (steps) have been completed and which steps are remaining.||Website, Microsite, Landing Pages||SB||Targeting: URL, Cookie||jQuery: Set/Read cookies
CSS: Prev/next step visual state
|18||“Maybe Later”||Maybe Later is a new concept for ecommerce entrance popups that I will explore in depth on day 9 of Product Marketing Month. A large number of ecommerce sites have discounts/offers that show on arrival. This can often be a major disruption to the experience, even if the offer is of interest. The way ML works is that the popup would present 3 options: Yes/No/ML. If “Maybe Later” is clicked, the Popup closes and a persistent Sticky Bar appears at the bottom of the page to act as a subtle reminder of the offer – ready for when the visitor wants it.||Website||POP + SB||Targeting: Cookie||jQuery: Set/Read cookies, Log “Maybe Later” click|
|19||Video Interaction Offers||Having a CTA embedded in a video is great, but it’s very limited in its ability communicate more than a few words.
This product idea enables you to launch a popup when the video is complete, or when it’s paused, or when you’ve watched a series of videos. It’s seriously badass. Click here to visit a demo of this concept (created by Unbouncer, Noah Matsell).
|Website, Landing Pages||POP||Targeting: Cookie||jQuery|
|20||End-of-video Talk to Sales||Present a popup to someone who completes a video such as a demo.||Website, Landing Pages||POP or SB||Trigger: Custom script||jQuery|
|21||Sticky Video Widget||You may have seen this on news blogs, where a video at the top becomes a smaller video stuck to the side or bottom of the window as you scroll. It’s a great way to ensure higher engagement with the video. Noah made a demo of a sticky video widget in the Unbounce community.||Blog||SB||Trigger: Scroll||CSS|
|22||Guided Tour||Show a popup that begins a guided tour of the page/product. If you close it, the tour is over. If you click a next button it closes and a new popup is opened, positioned close to the feature it’s describing.||Website, In-app||POP||Trigger: Click||jQuery||NEW: Can be built with existing features|
|23||Ship it Faster||By setting a cookie based on the shipping method on an ecommerce site, an exit Popup or Sticky Bar could be used to suggest a different shipping method (more expensive) to get it delivered faster. A smart upsell feature.||Ecommerce Website||POP or SB||Targeting: Cookie
Feature: Dynamic Text Replacement
|24||Out of Stock||By setting a cookie based on stock availability on an ecommerce site, an exit Popup or Sticky Bar could present an email address field to ask if the visitor would like to be notified when the item is back in stock.||Ecommerce Website||POP or SB||Targeting: Cookie
|25||Sold Out: You Might Like||By setting a cookie based on stock availability on an ecommerce site, a Popup or Sticky Bar could be shown that presents a set of recommended products related to an out of stock item.||Ecommerce Website||POP or SB||Targeting: Cookie
Feature: Dynamic Text Replacement
As you can see, there are a ton of new use cases for the products, which are useful to a completely different set of functional users. Unless we do something to specifically target these new functional users, adoption won’t be our only problem, acquisition will be too.
How can you target different functional users?
Approach 1: Product Pages for Organic & Paid Traffic
One way to start validating these use cases is to create new product pages for them to see if you can attract some organic traffic. In our case, this would allow those searching for this type of product to arrive on our website where we may be able to demo the product as part of the experience.
Approach 2: Cross-Function Advocate Email Marketing
Another approach is to explicitly connect the different team members, through suggestive email copy. For instance, we could email our customers and educate them that our product can help others on their team – getting the conversation started. This has the benefit of communicating through an established brand advocate.
Prioritizing Product Development
One of our goals with POT is to gather insights into which new product ideas are in demand. There will without question be an increase in technical support questions based on the implementation requirements of these ideas, but I consider that a good problem to have. If there’s enough call for full productization, that’s a great way to increase adoption and the stickiness of our products.
How many new products could YOU build?
I’d love to hear in the comments how you can imagine doing this with your own software/products/services. Please jump into the comments and let me know. If you’re worried about your competitors stealing your ideas (I definitely thought about that when I decided on this approach – but I’m erring on the side of our core Transparency value), you could simply mention how many you think you could come up with, which is also very cool.
Now, everybody POT!
p.s. Tell your web/UX teammates about this blog post