phoneboy
Director
Joined 8 years ago
User Profile
User Widgets
Contributions
Re: IgniteTech acquired Khoros to rebuild it. Here’s what that looks like.
"This wasn’t AI-written" and yet you're an "AI-First" company. To the point where your "introduction" presentation was so obviously AI generated, I didn't need for IgniteTech to admit that it was (they did). The results will speak for themselves, but the initial impression is...not positive.456ViewsSign in to react to this post0CommentsRe: Driving Growth in Community with Banners & Content Gates
That's good to hear, and I'm sure that's true of other features we might be using (the basic functionality being called "something else" in Aurora). We know that we eventually need to move to Aurora, but it's difficult when a bunch of custom functionality needs to be re-implemented. I assume it's also going to involve Professional Services, since we will have to map data from the "Classic" method to the "Aurora" methods :) It's an ongoing discussion we're having with our CSM.ViewsSign in to react to this postCommentsRe: Driving Growth in Community with Banners & Content Gates
Lief we're on Classic and, due to the massive amount of custom components we've developed, and of course missing functionality like custom tags, which are used in other components as well, I don't see a path where we can successfully migrate to Aurora anytime soon.ViewsSign in to react to this postCommentsRe: Driving Growth in Community with Banners & Content Gates
It's a bit complicated to explain as it requires components, CSS, and layout changes. At a high level, I created two new components (one for blogs, one for regular forums) that embed several of the components of the BlogArticlePage and ForumTopicPage in a DIV that is hidden. Why? So Google can still index the post, but the end user will see the prompt to log in. To reference a component in another component, do something like the following: <@component id="topic-message" /> The exact components you will embed depend on your existing page layouts. To determine IF a post is gated, I use something like the following: <#-- This query should only return a single result if the tag is set in the post. Otherwise it should return zero results --> <#assign gated_query = "SELECT custom_tag_scope FROM messages WHERE custom_tags.id = 'isgated' AND id = '${id}'" /> <#assign gated_result = rest("2.0", "/search?q=" + gated_query?url).data.size!0 /> <#if gated_result gt 0 > <#assign gated = true /> <#else> <#assign gated = false /> </#if> isgated is the ID of my Custom Tag and it's an "is present" type. Based on that plus other logic (some blogs aren't gated by design, for instance), we can render a partial message in place of the topic-message component. That code fragment looks like this: <#assign subject = (page.context.thread.topicMessage.subject)!"" /> <h2 itemprop="name" class="message-subject"> <span class="lia-message-unread"> <div class="lia-message-subject" style="font-size: 22px;color: #2d2e31;margin-bottom: 5px;">${subject?no_esc}</div> </span> </h2> <#assign body = (page.context.thread.topicMessage.body)!"" /> <div class="short-message" style="font-size: 16px;"> ${utils.html.truncate(1200, body, "...")?no_esc} </div> <div class="footer_bottom"> <div></div> </div <span>TO READ THE FULL POST</span> <div class="buttons"> <a class="read-more" href="yourRegistrationURL" target="_blank">REGISTER</a> <a class="read-more" href="yourLoginURL" target="_blank">SIGN IN</a> </div> <span class="extra-info">it's simple and free</span> <@component id="thread-pager" /> The body is truncated to 1200 characters (you can obviously adjust this). Also, to make it easy to assign the custom tag to the message, I added the modbar-toggle component to the ForumMessage and BlogArticle layouts, which allows me to easily set the is_gated flag easily.ViewsSign in to react to this postCommentsRe: Driving Growth in Community with Banners & Content Gates
We haven't gotten any complaints from anyone about it.ViewsSign in to react to this postComments- ViewsSign in to react to this postComments
Driving Growth in Community with Banners & Content Gates
Recently, CheckMates introduced banners aimed at encouraging our community users to log in or register. This fairly simple idea has already proved successful, so I thought it could be helpful to others. In thinking about this, it was just one stop on a much longer journey. So first, a little history. Check Point was a Jive customer, but there wasn’t any actual formal program before the CheckMates community program started in 2017. In 2015, a different community lived on JiveX, which became CheckMates, and migrated to the Lithium/Khoros platform in 2019. We dialed in on tracking Member Registrations to demonstrate overall community growth to our execs. We recently started being interested in Member Entrances, but first, let’s look at the metrics we’ve been tracking consistently, Completed Registrations, as these metrics are related. Historically, we’ve been getting roughly 1,000 registrations a month. When this number dips below 1,000, we start looking at what we can do to encourage more registrations. Most of our content is available without logging into the community platform. But we have some content restricted to only logged-in users for various reasons, including ensuring users log into the platform. In the old JiveX platform, the only way to make content available when logged in was by putting it in a space that isn’t accessible to someone not logged in. The downside to this method is content won’t be indexed by Google—an important consideration when you consider the vast majority of our traffic comes from search engines. When we moved to the Lithium/Khoros platform in 2019, we developed a custom component to “gate” specific posts. If users have not logged in and hit a gated post, they’ll be presented with a preview of the top-level post in the thread, and the rest is hidden. Below is a visual of the preview, or you can see this in action here. When we first implemented these custom components, I hard-coded the thread IDs into the components. The downside is that it requires pushing code changes through Studio anytime I wanted to gate a post. I now use Custom Tags, which made it possible to not have to push a code change whenever we wanted to update which posts were gated. Note that our general guidelines for gating posts are as follows: Top 25-50 threads by visits (reviewed quarterly) Content related to events (always gated) This idea kept the numbers above 1000 a month for a while. Earlier this year, we started noticing the numbers dipping below 1000 a month (our low was 800, I think), so we started looking for new ways to bump that back up. So, we added a banner to remind community members to log in and encourage prospective members. Sometimes, innovation isn’t complicated. Showing a popup on a specific page when the user is not logged in is pretty easy by including the component in relevant layouts. We had been experimenting with a third-party service to display this popup. But I decided to roll up my sleeves and write my own. Learning how to keep it from not showing after the user has clicked on the X to close required me to understand how to work with cookies. 😊 One thing I failed to account for in the design was that the Khoros platform doesn’t provide a way to track these clicks (Google Analytics wasn’t showing me either), so I had to route the clicks to a URL shortener. That meant the results weren’t directly tracked for a few weeks. And the results? Member Entrances increased noticeably, from 37k/mo in July to 42k in August and 45k in September. Completed Registrations went up from about 1,100 to about 1,200, the delta corresponding to the number of clicks received to create a new account. These simple tactics can help maintain momentum for those using the Community product, as our early returns suggest they directly contributed to moving the needle for our community.ViewsSign in to react to this postComments- ViewsSign in to react to this postComments
phoneboy
We can use the below context object to get the article ID inside the TkbMessage quilt on the TkbArticlePage.
${env.context.message.uniqueId}
For article ID on TkbArticlePage.
${page.context.thread.topicMessage.uniqueId}
For message/comment ID on TkbArticlePage.
${page.context.message.uniqueId}
Re: Khoros Communities 24.2 Release
Yet another example of the inconsistent experience I receive when I need to engage Khoros TAC...I was never offered this workaround! I ultimately decided to move away from using Products for the purpose I was using them for. Seems like this functionality was never fully developed and, given the eventual migration to Aurora, it doesn't seem prudent to waste further time attempting to use it.ViewsSign in to react to this postComments
456Views
0Comments
