 Well, I guess we'll go ahead and get started. They wanted to wait a little bit for some of the traffic to get up the escalators. Kind of starting off today, I was kind of wanting to get a feel for what type of websites you guys are working with. Ah, boy, I'm not going to be able to walk around with that. I think I'll not use the mic. If anyone can't hear me, let me know, and I'll go back to using the mic. But I think I want to be stuck at a podium the whole time. So we're going to get an idea of what kind of websites people are building. So how many people are building nonprofit websites? Good number, about 40%. How many people are building business websites? OK, so there's going to be a lot of people are building multiples. How many people are sort of managing a website versus how many people are managing websites? And if I'm the sense that you are the owner of the website or working for the company who owns the website, OK, how many people are agencies or consultants and so forth? OK, so a good mix there. How many people are working at publishing websites, content publishers, and so forth? That's a decent number. OK, all right. That kind of helps. One of the tricky things about how intelligence works is it's different depending on what your goals are. Different types of websites will have different types of goals. So I want to talk to you guys about something actually I'm really excited about. It's what I sort of see as the future of the web. It's something that we call intelligent websites. And so what is an intelligent website? Well, really intelligence is just sort of a system that starts to integrate in data analytics and other types of metrics to help people make better decisions. So it's not just about managing content. It's about data that can help us do things better, engage visitors better, create better content, and so forth. In only many ways, I think it's interesting the way we build what the traditional websites built. It's almost sort of like building this robot that you send out to the world and you have no feedback to know if it's actually succeeding. You don't know if it's just out there bumping into walls. And so really, you wouldn't see a biological system like this. You wouldn't see a mechanical system like this. We all have feedback mechanisms. We can touch and we can do things that as we do things, our brain then knows if we're doing it right or how to adjust and those kinds of things. That's really what an intelligent system is about. And so over the years, I work for a company called Level 10 and we've been around about over 15 years and we've gotten a lot of questions. In fact, in the early days, we actually did a lot of usability work, mainly in the banking world, when people didn't really know how to put together an online banking website. So you go on prototype sites out and you would videotape people and so forth. Well, now we do a lot of building with heuristics. So rules of thumb, bunch of experts get together, they wireframe things out. It's a very efficient way of working. It definitely doesn't require the huge budgets in some of those projects in the back of the 90s, but it comes to a lot of questions. Everything from what kind of content, what type of text, what kind of content terms are our visitors interested in? To flat menus versus drop-down menus versus mega menus. We keep having this conversation. It seems like over and over again. Here's all kinds of these little things and a lot of times we think we know what the best thing is. We don't really always have the data to back it up. And so we want to solve this problem, but ultimately, well, we're wanting to answer all the different types of questions. There's three main questions we're trying to answer with a system like intelligence. The first one is, when we make a change to the website? Do we have a positive or negative effect? Because again, most of it's just based on heuristics. And a lot of times it's actually for if you're a professional services, it's based on the clients who may not necessarily have a huge background and come to conferences like this. It's sort of what they want. They sell the latest cool thing on some other website. Well, when we implement that, does it really have a positive or negative effect? The second thing we're trying to do, and this is something that's always fascinating because of the Proto Principle. And many, many years ago, when we were less on the marketing side, I heard a marketer tell me at a conference I was at that we know that 80% of results come from 20% of our efforts. The problem is we don't know what 20%. And so one of the things I've always wondered is what if we could know the 20% and could focus on that side of things? That's another thing I want to do. And then another area, and this does get a little fuzzy, but I hope that it's a way to help people ask the most elusive question in marketing. It's not all about marketing, but most elusive question in marketing is what's our ROI? I'll go to say social media conferences and things like that. And when everyone brings up ROI, they're always kind of hand waving well, we really don't know what the ROI is. They're like, why not? The web's very measurable. Why can't we figure out the ROI? Is there at least come up to a good estimated guest to get in the ballpark? So as an intelligent system, really I see there's kind of two sides to what we're trying to do. One side is about behavior. What are people actually doing on the website? And when we make changes, what kind of changes in behavior are we seeing? The other side is identity. Who are the people coming to our website? What can we learn about them? You know, a lot of times, if you're kind of building your websites properly, you start out your building personas and all these kinds of things. What if I actually start to understand when people come to the website, which personas they fit into? Or other things, such as are they, what's their cloud score, and are they an influencer and so forth? The, my kind of goal with a system like this goes back to a book I read several years ago called The Fifth Discipline. Anyone ever read The Fifth Discipline? Nobody. Okay, I'd recommend reading this good book. It is a bit academic. And it's kind of one of the most typical business books where it's kind of making the same point over and over again for a while. But in general, it's a very good book. It's actually written by the guy who used to be the director of MIT's Institute for Memory and Learning Now. And his hypothesis is that the most important thing organizations need to do to be competitive is to learn faster than other organizations. And so his passion and the whole Institute that he directed at MIT was all about how do we create better learning organizations? And we came up with five core components to a great learning organization. The first one's personal mastery. Basically, you have people that are interested in learning. Pretty straightforward. Second one is mental models. And again, this goes back to the heuristic, those rules of thumb. These are things that we believe to be true. So responsive design is more valuable than non or different things like that. Well, great organizations actually challenge these mental models on a regular basis. Why we see a lot of big companies stop innovating is because they have these ingrained mental models and they stop challenging them and just kind of keep going down the same path. Third one is shared vision. So that as a group, we need to be working to learn together and we need a shared vision towards doing that. The fourth is team learning. People collaborating. People sharing and dialoguing information. And really, most good learning organizations they have these for. The fifth one is the one that the book's about and the one that's actually the most elusive and it's systems thinking. This is really developing conceptual framework for thinking of things in systems terms. And so what I actually thought was interesting, probably one of the reasons I gravitate towards this book is I'm actually a chemical engineer of education. And I always wondered why people don't really, I think most engineers who are trained in process control and systems thinking. So I don't think really any other discipline is. And we had a few electrical engineers that were in our process controls class. But I don't really know how many, I don't know if computer scientists actually get into process control. Because this is something that's kind of natural. You think of a system as a box, it has inputs, you can measure those inputs. You have an output. And how do you adjust those inputs to change what you're getting on your outputs? And so this is actually what they talked about something that's missing. In fact, there's an interesting experiment they talked about at the beginning of the book and you can look it up online. There's something called the beer game. And so the beer game is sort of this game, they actually do this with incoming MIT MBAs. And they break everybody up into four groups. One group is a wholesaler of beer, or as a retailer of beer, another wholesaler, another distributor, another manufacturer, and they all have to do orders. So they pass orders back and forth in paper and you get docked points if you accumulate inventory, or if you can't be custard man and things like that. And out of all the people who do it, only 5% of teams actually achieve an optimal rate because they're not applying systems thinking. There's not these feedback loops that they need to understand, they just see how they're doing things from their point of view, not how the entire system is performing as a whole. And so there's one of the things that we want to implement with a website intelligence system. So the interesting thing, of course, is I'm sure you're thinking, well, there is analytics. How many people are running analytics on their website? How many people have looked at their analytics in the last month? Pretty good, much better than normal groups, smart group. How many people have their goals set up in Google Analytics? Ah, decent numbers, better than the average. How many people are having their developers and content people and their creative designers looking at their analytics? Wow, very sharp group, cool. Actually, when I asked that question in those places, very few people have looked at their analytics. I'd say normally less than 5% have looked at their analytics in the last month. But there's still, so we're starting to think about why is an existing analytics system sufficient enough to give people the feedback they need to build better websites? I think the first problem is, is that you have to measure what you value. And so most people, when they look at analytics, they just go, well, I'm getting this much traffic, or these pages are getting so much traffic, or there's many page views, that's not a particularly meaningful measure. Now, of course, if you're implementing goals, which is great, it looks like a decent number of you guys are implementing goals, again, that's something that you find very few people are doing. It's a wonderful tool. Now you start to get into more, we can measure things that are of value. And that'll change from site to site. If you're an e-commerce site, it might be someone purchasing something. If you're a B2B, it might be generating leads, or what have you. But we also found that there's actually kind of a whole category of things that when people are setting up their goals, they're missing. And it's mainly engagements. Things like who's sharing content, who's commenting, who's playing videos, who's doing these things. And actually Google Analytics is a particularly well set up for this. It actually has a mechanism for doing it, but it doesn't push any of that data automatically. You have to have your websites push that data. So one of the first things we wanted to do is we wanted to set up a system to push extra events. And there are some basic things you can do, say the Google Analytics module in Drupal, such as if someone clicks a certain link out of a site, but really, the types of things that are kind of easy to do weren't things that we really wanted to measure. We wanted to measure more things like who's engaging with our content, who's clicking on calls to actions, what landing pages are converting, whether they're converting ratios and things like that. And so we need a system that pushes a lot more events over into Google Analytics. So I'll say, when we started to build the system, I was planning on, there's actually an Analytics system that we built years ago. But then as I started looking at Google Analytics, I realized, oh, there's actually a whole bunch of untapped features in Google Analytics. So then we decided just to piggyback the system on top of Google Analytics and push a lot more data and then pull a lot, and I'll kind of shoot a second half of it later. So then, of course, we need a way to manage different types of events. And of course, that's the great thing about Content Management System. It gives us a way that we can set up and say, okay, well, we want to create this event that we now want to push over to Google Analytics, all that kind of stuff happens in JavaScript. But we don't have to be dealing with JavaScript all the time, in order to just first say, if someone wants to measure something in particular. So we can set all that kind of stuff up in the triple add-on. And then some of the things I think are really interesting to monitor are things like CTA click-through rates, landing page conversions. And so something we might want to do is that whenever a CTA called action, so these are like these little graphics that might be, hey, click over here to download this e-book, or donate to our cause, or even sign up to the website. Well, we don't know how many times are these being shown versus how many times are being clicked through. And so if we push it, there's an oppression event every time it's shown, and then every time someone clicks on it, we push a click-through, and then they go to a landing page, and then we can do something like push a landing page view, which are sort of these numbers, and then you can look at how many times they actually submit, which then would create a CTA conversion and a landing page conversion. So we start to get an idea of what calls to actions and what landing pages are converting best, even doing A-B testing, and putting ones that are similar, but changing certain things to find out which ones we're getting the best performance from. Now, the second challenge that we found with traditional analytics is that particularly once we've gone and set up a bunch of extra events that we're pushing over into it, is that there is currently, if Google Analytics has over 200 different data points, and a lot of people don't really, the question kind of comes up, one of the ones that love is time on site. There's a lot of people that say, oh, we want to increase our time on site, but we've actually found through usability, we actually decreased time on site, which is not a bad thing. People found what they were looking for faster. Oh, and so there's a lot of these metrics, it's hard to say like, what does it really work? And so in economics, there's actually a pretty good mechanism for dealing with this situation. We have all these different products, and you're trying to understand what's more valuable, what types of things we want to produce more of, and it's a concept called utility. And basically the way utility works, it's almost a little bit like money in some ways, except money is a bit of a flawed mechanism for dealing with the situation. Like I was almost saying, if you were to have an orange, and you were to have an apple, and you would like both in the same, you'd say, okay, both represent one utility as a unit. And then you can do things like, well, if you have two apples that you want a half orange, and you actually start to create these in different curves, as you understand the type of utility that different products create. And so we wanted to apply this, basically to come up with a single number. Instead of having to look at 200 some different data points, I want to look at a single number to know, are we doing better? Or are we doing worse? This is great for managers. The analysts will want to go deeper than that, but the number is great, is a great measure for people that want to do a quick look. And so what we want to do is set up something where we can measure things like traffic. So out by default, we'll do something like, every visitor we have is worth 0.05. If someone sticks on the website, in other words, they don't leave, they hit a second page, that's not worth 0.1 to us. And every page they hit after that is 0.02. Then we can start scoring events. Every time someone shares a piece of content, say on Twitter or Facebook, that's worth five to us. If someone comments it might be worth 10, we're getting value things like if people are clicking back from social media, and so forth, then you've got your goals. So goals are if someone submits this form over here, normally it's a conversion thing, maybe e-commerce or buying something. How much are those things worth? So we start to select certain data points and say every time we get one of these, it's worth so many points. And we'll see how that number gets used a little bit later on. One of the other challenges that we found, actually I was actually really impressed that people are actually logging into Google Analytics and looking at their stuff, or whatever analytics package they're using, because that's another challenge we found. It's this other system over here. And while normally there's a marketing manager or someone similar content, someone who's maybe doing content that's looking at it on a regular basis, generally people don't look at this data. So what I felt was really important to build a great system for creating systems thinking was to bring that data where people are living. People are logging into this content management system on a regular basis, so we want to weave analytics data in so that people are seeing it. So for example, this is a typical, just a standard Drupal content admin, but we're hooking in and pulling data out of the analytics. And remember all I was talking about the scoring? That's where these numbers come from. Trying to get people away from thinking about entrances and page views and towards value. We'll still talk about interest and views because they're fun, but we like, these are the things that are really important. And so one of the things we're doing here is we're saying, okay, we're gonna score all these different things. And so this page here, how much value is it driving per day? And then we actually have a threshold that says if it's above a certain amount, it's green, if it's below a certain amount, it's red, and otherwise it's yellow. But so that when people ever go in the app and page, they now see, oh, we ended up blog post over last week. Oh, it's scoring, it's scoring in this area. The other thing we wanna do is that on every node, we wanna put an analytics tab. So that when people are creating contents, and more and more what you're seeing is particularly, when you say B2Bs, you've got engineers and you've got other subject matter experts that are creating content, not necessarily expert writers. But we wanna give them ways to understand what type of engagements going on with their content. So let's give them an analytics tab. And so I'll show you a little bit what's in a second, what's behind the analytics tab. But another quick example is just looking at form submissions. So like one of the challenges we have, this is actually some of the stuff we built specifically for our website. And one of the challenges we have is that we tend to work in a local area, Texas for the most part. And so we wanna know how many people when they're submitting a form, are they actually local to us? So for this kind of just looking at the forms that are being submitted and integrating that data in from Google Analytics. So the other thing that I wanted to do and another challenge that I found with Google Analytics is there's a lot of great data, but it has to be pieced together. And you find yourself, like there's some people that we work with sometimes that work with big agencies and they pay big bucks to spend a lot of time putting a lot of spreadsheets together because they can't get all the data they need in a single report. And so that's one of the other things we wanna do is we wanna say, well, we wanna get some comprehensive views. So for example, we're talking about that analytics tab, this is what we want behind that tab. So we can see traffic, we can see what types of events are happening. So this would be a typical blog post. So it's the A, this blog post has gotten 10 social shares, it's gotten one comment, it's got one CTA click. No one has converted from this form, but if they had it would show up here. And then this is actually sort of more of a downstream. So like after they left that page, did they share something else? And this is the bottom of this page, it's got a long page, so I chopped it here. And so then over here's all the different traffic sources. So where are we getting traffic from? Do this thing getting picked up by Reddit or by StumbleUpon or where are we getting traction or the search engines pick it up and we're getting some traffic from there. And then the thing we wanna do is maybe we wanna do a deeper dive. So for example, we're getting a lot of social traffic, maybe we wanna understand it. So there's actually a whole series of reports that are all focused around this one particular node that allows us to understand better different components of what's going on with this specific page. What are the other things that we find interesting? So it's great that, one of the first things we did was implement the whole kind of system where you could see pages and you could see storing, but then people started asking sort of like why? The last report was showing things like the why as far as this happened and this point happened, but we wanna understand trends across like why was this page actually creating better engagement. And a lot of times it's hard to tell from a single page. And so a mechanism that we wanted to use is segmentation. So that we could look at a larger set of pages and group them together and see what their performance was. And of course, what's great about a content management system like Drupal is it gives you all the mechanisms for doing that. So for example, we can group things together but we wanna look at all our different content types. How are they performing compared to each other? And of course you can then click into something like blog posts and then look at all the blog posts filter down from all the other types of pages. Or maybe we wanna look at authors. What authors are creating the most engaging contents? And so we can score them based on a sum of how all the pages they're publishing are performing. Another one is taxonomy. So what terms are performing the best? And so there's all kinds of tools of doing that. Organic groups might be another one. So that's, you can say which groups are sort of creating the most value, most traffic. And so one of the things we wanna do is have a whole way of creating these segments. Again, Google only supports this stuff but you still have to push it from the content management system. You've got to have a way of sending all that information over. And so we wanted a way to organize it. So it's kind of a typical thing. So we'll set up authors, content types, entity types, publish time. It's actually kind of, it's kind of, it's a pretty interesting thing so you can compare like how does this blog post do in its first 30 days versus how does this one do in its first 30 days? It's not quite fair to compare them when one's pretty old and one's new. So I think people are gonna add what they want to be able to do various different types of page attributes. So then one of the other areas that I think is important, so you know, there's a lot of things you can do with content but we also wanna do a lot of things about visitors. So one thing that I wanna be able to do is to be able to track visitors as they went around our website. So what happens is when someone comes to the website they're still anonymous. We don't actually know who they are. You know, we don't have a name for them, we don't have an email address, anything like that. But we can look at what they're doing when they go around the website. Actually what I like is from a usability standpoint. You use it in call centers. We always have this problem where someone would be confused on the website, they'd call it the rep. And the rep wouldn't really, we always try to figure out like, what was it you were doing? They had to manually explain it. What we wanna do is create click streams. So we're tracking every page that people are doing, all the events they're doing and then based on the token that they're being tracked with, we can reconstruct their path through the website. And we can reconstruct their months of path as long as they haven't cleared out their bookings. So as long as Google Analytics can track it, then we can track and know what are people doing. Even kind of did a fun little timeline so you kind of like, you know, get the little screen grab and all that kind of stuff. So you get kind of a more, like what are they, what are they kind of experiences they went through the website? And of course so then, just like we had, we had a way of setting up page segmentation. We want a way to set up visitor segmentation. So as people are moving through the website, we wanna understand things like, what are they interested in? Maybe we give them a score, say you're a B2B, you wanna do a leave score. Or maybe one of the ones actually, actually kind of like we just did recently is a job candidate score. So if people are applying with us, we wanna know, did they look through our blog? What types of blog posts were they reading? What videos were they planning? You know, things along those lines or did they just kind of come to our website, you know, submit an application and so forth. And so we want a way of understanding as people are doing various things on the website, what is they're doing? And then what gets really fun is when someone finally goes ahead and submits a form. So it might be a web form, we also integrated a HubSpot, a few others. Because then we can start summing all this data together. So we take data from Google Analytics, their location, their browser, information from, say, web form, like when they were submitting. We take their email address and ping it against the service, like full contact. And we might be able to figure out like what their cloud is, what their LinkedIn is, you know, some of those things. So now we can understand a lot better who this person is, maybe customize content to them. Push, so if we've monitored what types of things they're interested in, push that information into, say, MailChimp or what have you. And then we can do emails around their specific interests. So that is kind of, like I said, this is kind of a project we've been working on for about a year to help build more intelligent websites. What time is it? I'm gonna have a challenge that I won't be able to demo this with this projector. Oh, do we have any questions? Data that you're storing is coming out of Google Analytics, but I'm assuming you're storing a lot in your own tables for your module as well. What about the integration of some other stuff? So how would that work with activity? Sure. Yeah, actually kind of the way it works is when someone's anonymous, pretty much all the data is being stored in Google Analytics. So it doesn't take up, because otherwise you'd have insane amounts of data sitting in your Google site. And there's really, and so the thing is you can't actually push anything in Google Analytics that has personal identifiable information. So you can't push an email or a name or anything like that to Google Analytics. You can push a hashtag. So that allows it to seem everything back together. So basically when people are an anonymous visitor, pretty much everything's being tracked through Google Analytics. There's a couple exceptions for a few scenarios, but that's mostly what happens. Then when someone spends a form, still all the analytics stuff is going to Google Analytics, but now there is data sitting in Drupal. What actually then ends up happening is a trigger process where, sort of the hook process that says, what modules have you enabled? What am I synced with? So like a typical scenario might be hook syncing with HubSpot at full contact, which is like a part of our API, full contact and MailChimp. So the first thing it does is, okay, I've got this person, I've got an email address. I'm gonna go get all these different sources. What data do you have for me? Or even LinkedIn or what have you. What data do you have for me? And it pulls that all back. And then after it turns through, it saves it in Drupal. Drupal sort of ends up acting. There's an entity called an Intel visitor. So it actually ends up being sort of the central store for the data, but then it'll push it back out to any of those platforms. So like a good scenario, something I found kind of annoying with HubSpot is that you don't know someone's location. Unless they actually fill out a form and I'm like, well, you have that data sitting in Google Analytics. So we use that process like, hey, pull the address and send it to MailChimp. You know, I wanna, and now when I push this data back out, I wanna push their address. I wanna push where they're located, geolocation information. So that way we have it. The other thing is like we'll push things like, you know, a lead score mechanism or something like that. So now in say HubSpot, we've got a lead score to work off of so that we kind of evaluate what types of mailings we're doing and so forth. So it's a combination of the three systems. Yeah, it's kind of a combination, exactly. It's kind of a combination of all three. Any other questions? This may be better to do. I'll see how well this works. So we've got a booth down the exhibit area. We've got kind of like a whole like six screen monitor setup done where one of the things I kind of did, I did, because a lot of times when we're demoing this, people will think of the whole real-time analytics thing and Google Analytics is really cool, but it's actually not very useful. So actually for the conference, I kind of did a little proof of concept of a real-time dashboard that's much more in depth than what you can get with Google Analytics. And so we've got kind of a whole full demo, but I'll kind of show you kind of a short version of what that might look like if I can get this projector set up. We are, well, okay, that is a great question. So there actually is a free version of this out on Drupal.org. So it's a little bit like Molem where there's an API key, but there's a free API key. And with the free version, it actually will do all the stuff around content. What you don't get is all the visitor stuff, because that is the stuff that we actually need to do a bunch of data storing and so forth around. And so what we're doing, and then the what we call the pro version of the service, which gives us a full access to everything. At some point, we are gonna be selling that as a kind of like just a monthly, sort of like Molem, kind of like a monthly fee. At this point, it's still in beta. And you know, saying we're using with our clients. What we are doing though is we have a offering that we're doing called the R&R reports. And so what that'll end up being is that you'll get the full system, and then we'll produce a report. Like we'll kind of look over the data. Because that's the other thing we're trying to get a better handle on. It's been built around sort of like content marketers, a lot of it has, but then we've got a couple of clients that are doing things like communities and they wanna understand more. And so we're trying to get a better handle on the different types of things, different types of websites need. And what reports, because you kind of build reports forever on this thing. And so we're gonna be doing this R&R report, which is not gonna be, I think the starting price is gonna be like 600 a month. So it'll be a fairly expensive. We'll spend an hour and a half. We'll kind of give you all the recommendations on how to set it up, like what taxonomies you wanna follow, how you wanna set up all your content types and all that kind of stuff. And then spend an hour and a half each month kind of putting together a report, pulling out like kind of the important things to look at. That's another thing that a lot of people, some people said, like I don't have time to look at more data if someone could do that for me. And so that's why we're kind of like looking to go down that route. And so we'll probably, I'm hoping to get it out of it. I'm hoping to get the pro version out of beta in the next six months. One of the challenges we keep coming up with new ideas for it. So the beta works pretty well. I just don't know if we're quite ready to have millions of hits against the thing. So earlier, sorry, I missed it, but, does this help with the fact that Google's not showing a lot of the key organization stuff like that coming in because that's been a big issue? Yeah. Oh, Google Analytics, no, you can't get it unless you use networks. Yeah. No, it does not. They cannot solve that. That would require a special type of mojo. Yeah, no, actually, that was something I was really upset about because it was literally like three weeks before they stopped doing it. I actually put like a whole JavaScript thing in that would tell you what ranking you were and what key you were and all that kind of stuff. And then they were like, darn it. It actually went that hard to write to that piece of JavaScript, but. Yeah, yeah, I wish it could. Now, what's interesting though, I have seen some people talk about ways to get to some idea of what it is. So one thing it does do is it does push the terms that could be on a page. In fact, one thing we've done for one of our clients is we use the Alchemy module to kind of extract terms and then push those terms. So you're sort of like taking a guess, but it's still not really saying like, where you're ranking or anything like that, but it gives you some idea. What do you think is more like a partner or probably a reseller type? We do. Okay, yes. And that's actually a big part of this. This stuff, and along with our distribution, Open Enterprise, we've been selling as kind of our secret sauce to our clients. But as we've been showing this to a lot of people, they're like, oh, we'd really like them. It's kind of more showing it to like some other agency owners and like that just to kind of get their opinion and feedback, you know, a bunch of smart guys. And then when some people start asking us, like, could we license this or could we do whatever? And so yes, we are doing a partner program. In fact, we're basically kind of launching it here at DrupalCon. Probably the best thing to do is talk to us down and talk to us down at our table. There's some other people that'll be a little bit better to talk, I think I can talk about it, but there'll be some other people that'll be a little bit better to talk to about than I will be. Now, of course, the depth of, that is not the most, that is not the most online, extreme world, but perhaps a little bit more objective. That's a pretty good picture. That's a great question. All right. Well, let's close it. You can edit it. Now, of course, the always dangerous, scary thing of any kind of national live-down. I'm kind of a thing that was a proof of concept, but so, and so we're gonna be actually looking at what this is, is this is actually a real-time demo. What I like about this is actually kind of easier for people to understand how the data is getting assembled, how it's getting used. Is it back bone? Pardon? Is it back bone? It is actually not. If I had time to learn, if I understood Josh's script or something. Oh, I still don't know the best thing she's supposed to do. Is she great at jQuery? What? Is she great at jQuery? No, I know. No, no, no, it says how to go to the panel. Oh, how to go to the, okay, the panel itself, okay, that's a great, okay, another good question. Why won't it go in JS? Actually, it is, yeah, there's time on JS. With a bit of hacking as well. There's some annoying bugs in it. And there's really no good way to hack it. I mean, you have to hack it. Yeah, there's no way to hook into it. There we go. All right, that's awesome. Okay, so anyway, yeah, that is timeline JS, which is actually in the main system too, but it's just a fun JavaScript, fun JavaScript thing to kind of click streams. So one of the things I like about the real-time dashboard is actually kind of, you can kind of get a better idea of how this data is coming together. So let's say, for example, I am hell, I was hoping to have two screens to do this. I will probably pull out my iPad to do the navigating around the website. Likely connected to the Wi-Fi. Well, actually somebody's on it. So this is actually a live website. So I'm gonna get that way downstairs or actually we do get some search engine traffic too. So actually what's going on here is this actually is three visitors have come to this. And it might have been when I, probably one of them was when I went there to log in. And so each time, actually I am gonna show this on the, I am actually gonna go ahead and show this. Oh, but I have an incognito window. So let's say, so this is just kind of, this is just how to kind of simulate, I refer coming from external. So let's say someone said, hey, I wanna go and learn more about mobile design. So now that was off the website. So this is now on a website that's being monitored by intelligence. Okay, so, yeah, this thing's gonna be on the screen. Okay, it's a little smaller read, but so this is the hit that just came in. And then what it did was this one hit, remember we said that it's worth 0.5. So what happened is that whatever the traffic source was, that it got increased by 0.05. And then it breaks down into campaigns, keywords, whatever else might be tracked. Then the page that got hit, it got a 0.05. But that page also pushed a bunch of other data. It's way too small to read, but it pushed it into blog posts. It pushed it, the author was Kyle. That the past, the two taxonomy terms, and yeah, someone's on the site. So, but anyway, so the pastoralist taxonomy terms, so what happened is all of those things, Kyle is an author, he gets bumped up 0.05. I think usability, UX and development were both his taxonomy terms. So both of them get bumped up 0.05. The visitor, which is the people over here, that person gets bumped up 0.05. And then of course the whole site. Now, as if I hit a second page, then all those things will all get bumped up by 10 cents. Or if you go and do something like, or if you do something like, okay, well I'm gonna share on Twitter. So that's actually this orange piece. That's basically saying we've got a valued event that just came through. Actually all these other events that are coming through, these are blue. Google visualization does some odd things in anime mode. We start getting a lot of lines on there. But so you start to see that, so you can see that that got pushed through and of course it shows up underneath the events that we now got a social share. I shared on Twitter and so when this rotates through, it'll say yeah, we've got to share, we've got to share through Twitter. And then we might have something where the person, they click on, they click on this call to action. And you actually kind of say, if you saw the color real quick, it actually kind of bumped up. That we just hit a landing page. So we triggered it. Now we've hit a landing page. The CTA click comes through. Actually it looks like we've got a ton of people on the website. So this will make very, very difficult. Should have put up a different website for this. Okay, that's actually pretty psychedelic. Yeah, I'll say this. I did a whole lot of testing with a whole lot of people on the website. And if I could find my user, I could actually keep him selected. What we're going to do with that system. Actually, I think this is my user right here. Let's see, here we back up. Yeah, there's a social share. There was the entrance. Okay, so that's how the click streams work. So now I was, okay, so I'm asking about how this specifically put together. What this is actually doing, I was originally hoping to use Google Analytics. Actually it has a real-time API, it's a data. I was hoping to use that originally. But then I realized I'm going to go over. There's API limits. And I wouldn't have been able, I wanted more like a five-second polling rate. And I would burn through our daily allowance of API calls. So what I ended up actually doing to make this work is I'm echoing all the data that goes into Google Analytics. Basically back to a simple little log. It doesn't actually run through Drupal. Although I'm storing the Drupal database, but I don't have to. It's just kind of a simple little API that just stores log items. And then this is a whole JavaScript thing. It just grabs it and kind of assembles all the data they're needed for all the different reports. That's how this thing gets built. And then things are kind of fun like this. These two things down here, these are actually coming from AdVis. The AdVis API will actually tell you where, when people share stuff. And so it's kind of neat, it's like, you know, AdVis is on about 10 million websites. And so when people are sharing, it keeps a profile of who that person shares on. And if you implement the AdVis API, they'll let you have that data. You just got to tap into their JavaScript API. So that's one of the things we save. This is actually not Google Analytics. This is actually coming from AdVis. Just because Google Analytics takes a little bit more work to get the data back out. So they've got a bit more of a real time. Although what I found with AdVis is sometimes I think they're kind of keeping, like, where you log in the most, not necessarily where you're logged in currently right now. So like, you know, if you live, like I just yesterday when I was logging in, it's still having Dallas. So I think what's trying, it's basically like, where am I normally? Not where I am right now. Google Analytics is where am I right now? So you kind of do different pieces of data. But so anyway, so as we're moving through the website, as we hit things, you know, pushing that data, and then the visitor is also having, it's a little small to see it again. You guys were gonna see it, it was a great, the demo is very visible, very easy to see that we've got downstairs. But you see that now these points are starting to add up on this user. So this user has a user experience of one, an interest in user experience of one, an interest of development of one. As we say, hit another blog post or hit other things on the page, we can increase this number, decrease them, you know, as we see fits. So, you know, that's how, like I said, it's gonna be hard to demo with all these people on site, but anyway. So, but please come down and see the booth. I think it's kind of a cool monitor set up. Plus if you wanna see like six screens, everyone know how to do that, because I've tried several different ways to get that to work. So are there any other questions? Yeah, so can I see if this is gonna be rules-aware, and I can show that one in blocks to people based on the screen? It does have some rules-awareness now. We haven't done as much with rules because we haven't really, the challenge is our clients find rules too difficult. We do rules, so eventually we've got a couple of clients who are using this more to monitor communities, and they wanna see like when people are logging in and people are doing other things, and they were using rules there, because there's already Drupal hooks for all that stuff, and there's already rules hooks for all that stuff, but a lot of things that we're trying to measure, there's not rules hooks for, so like when someone shares in social, that's really more part of that, that's for whatever platform you're using. So we have some integration with rules. I actually like to get a few more things, a few more things integrated, but yeah, you can trigger any of these events based on a rule that gets triggered in Drupal. Do you have much familiarity with Occhia Lyft? I know a little bit about this. Is there a solution for that? You mean like they're kind of attacking similar problems? No, no. Yeah, I think that's gonna, I think the future, more of what I understand Lyft is more, Lyft is more around like dynamic content, which is actually a rule side of personalization. Oh, okay, yeah, I think they're using cosmetics for that. And yeah, and actually so there's a system, when we kind of started this project, I really couldn't find anything that was like it, which is actually not a good thing. I mean normally I want to find other things that are similar because it's kind of maybe means you're on the right track. And actually a lot of this came out we found some content, some marketing automation platforms like Marketo and HubSpot were lacking in certain areas and there's certain data we couldn't get to and so we, or some of our clients wanted to get to, so we started building this. But so yeah, I know that there's a thing called Occhia Analytics and it's KISS metrics is what it is, which is sort of the same concept, you're tagging visitors and you're moving through. The big difference though is it's not integrated into Drupal. You don't get the reports in Drupal. And there is an integration of rules, but you have to set all the rules up yourself. You install this and there are some things like if you need to add this running to do the social tracking right now, it's just a matter of when we have a client that wants us to do something else. But it works automatically. You don't have to sit there and set up all these rules to do it. And then it works well because in comments they have all the rules are set up. So if you have distribution, it's great. They give a regular website. Now you gotta go figure out how to set up all these rules and the rules are kind of a varied play way. Actually, I actually wanted to pick up the pants and I was trying to do all the rule stuff. You gotta have the right version of JQuery and all that kind of stuff. You gotta degrade all your JQuery and all that kind of stuff to get it to work right, which is a lot of fun to figure out. Like, again, this page in our admin run this version of JQuery. This page run this. I'll do like Drew said at the keynote, you know, make it more complicated on the back end easier on the front end. Yeah. A lot of different rules. Yeah, yeah. But yeah, I said there's a lot of people trying to deal with dynamic content and so forth. And right now, this is not really a dynamic content platform. It's much more about trying to, it's much more about usability and trying to understand what people are doing. But content, dynamic content will be where we're going with it at some point. Other questions? Hope you're trying to go like that. Do you see, I mean I can see lots of different users for this, now if you see the primary user as the content creator or the sales person or what's your vision for some of your primary stakeholders? It'll depend on the organization. My hope is everybody's. That is the thing that I think is kind of, like there's some really great analytics. You know, say, you know, marketing automation platform, but only the sales team wants that. And it really, there needs to be, like let's say you are like inbound marketing, content marketing type organization. There needs to be collaboration between the subject matter experts, the marketing team, and the sales team. In fact, we're a HubSpot partner. And they've taught us marketing. You know, we're sales and marketing together. And so the hope is that there's, you know, pieces that the sales team is gonna use more than others. But our hope is that everybody wants that. One of the things I actually got a kick out of is, you know, one of the little debates we have sometimes is the contrast of fonts. And I'm a little bit of a Jacob Nielsen camp where I like a very high contrast. You know, of course, designers, they like to do these nice grays on a wire or something like that. We've had a few people comment on our blog saying, hey, could you turn up the contrast? You know, I'm having a hard time reading it. Well, I wanna go see who they are. Cause I wanna know, like, you know, maybe get an idea of, okay, well how much, how much does this person come to our website? Is this person gonna come to our website? You know, those kinds of things. And then I wanna go to my designer and go, okay, well, okay, these are the types of people that we might be having some usability issues with. And so, you know, that's really the hope, is that to take the analytics and the intelligence out of the hands of just a couple of analysts that made it to salespeople and make it so that everybody's got access to it so everyone can make their decisions. In fact, the thing I thought was really fun, you know, so like what we do on our blog is we ask our developers to blog once a month. And we don't really give them the same topics. We're like, whatever you're learning, whatever you think's just cool and you think other people might wanna know. So they're writing and then other people project management and so forth. And remember when I first got this on our website back to like last July, we had this lunch and learn and several of the developers, I kind of walked into the room and some of the developers were sitting there going, oh yeah, so my blog post got this score. He's like, oh, I'm gonna write this topic because I think I'll get this kind of engagement. You know, all of a sudden, you heard them having conversations they never would have had before. Because now of course they're gamifying the whole thing around the score. But I was like, hey, that's great. You know, I did, you know, for several weeks after that, you hear people going, oh, my blog post got picked up and read it and I drove this kind of traffic, you know. And the other, oh my God, it's so well open. It's so well fun traffic wasn't as valuable. You know, they didn't engage as much and so forth. They're like, those are the kinds of conversations you wanna be having, but people like really build background in those kinds of areas. So Doug, do you have a question? Yes, this is a smorgasbord of very useful data. You anticipate people wanting more bite-sized but focused information, I guess. And that's where the R&R report is, exactly. And so the idea is, yeah, there does start to become a lot of data. And so, you know, kind of going in there and spending some time, what it does is with not a whole lot of time, we kind of dig through the data and kind of go what's significant versus, you know, what's some of the other things. So that's a little, that's the thought behind the R&R right now. And then, you know, eventually we'll have, we'll have the R&R if people want help with their analytics. So we've got a few different versions, the levels, but then we'll also have the DIY, you know, you just run the analytics and you can go and analyze it yourself. Do you have Intel if you didn't have R&R? They're actually two separate, so. Well, R&R is really a service on top of Intel. So in other words, you have to have Intel and so it's really just us spending some time to help you analyze the reports. And so then we send you a deck, you know, kind of pulling out, you know, different pieces of information, sort of nuggets, if you will. Got to write an executive summary. But yeah, it's all based around Intel. It's one of those things where to this point we haven't been really ready, other than our own clients and a few select, you know, a few select people. We haven't really wanted to give out the pro version. So we haven't really gotten a stress test on it yet. And so now we're trying to kind of take it to the next step. We want to get more people involved in the beta. And so that's, they're like, oh, this would be kind of a good controlled way. Plus we'll also get a better handle on the different types of data people are trying to get at, the best way to kind of design reports and segmentation for that. Who just said earlier that pricing is possibly six or a month. Was that for the R and R? That's for the R and R, yeah. Probably, you know, right now we're targeting for just the you install it and you pay monthly. It'll be like 120, 150 for a website to say up to a certain volume. And large volume websites might become bigger than that. So yeah, that'd be for the R and R reports. That's like getting all the pro version of all the data and then sending you a report each month, kind of pulling out different nuggets any time. And yeah, we're doing a real seller, you know, a partner program around it too. Where partners will get a discount on it. And then actually instead of us going to the clients, we would be giving those reports to the developer and they can figure out like, they want to go sell, they want to go sell their client or services based around some of these recommendations. They want to filter some of them out, you know, what they want to do with it. So cool. Thanks guys. Thanks for the help. Do you guys want to do any of the work in the future? I bet you already did. Oh, no, probably not. Actually, what's interesting, we're talking to someone that doesn't, they do an agency that does a bunch of amateur work and they want to move to this because it's just kind of very expensive. Do they got to get all the stuff all customized? Yeah, yeah, yeah. It's gotten very expensive to bring the consultant in and do all these customer reports and everything. So, like a lot of this is hopefully to replace, of course I mean it only works in Drupal, you know, so tightly integrated Drupal right there. But for a Drupal website, replacing the beach or something like that. Right. Cool stuff. Thank you. Yeah, go down and see us. I'll get some people off the demo and show it to them. How would you place this on the demo? So generally, it depends. We actually have done a market upgrade on one. So, we do HubSpot as a way to work with HubSpot. Mostly what it does is that it's tracking alongside of HubSpot and then the way we do of like submissions, like I don't know if you saw that screen, but it was a combination of webform submissions, even discussed comments, comments and submissions, HubSpot submissions. So what is happening is that with HubSpot when a form is submitted, it hooks in and that way we capture the person's token. If data is sitting in HubSpot, then we want to do that whole sync system. Then it goes and pulls the data from there, brings it over to the Drupal, and then you can modify stuff there and push it back and forth. And so that's the typical scenario that it kind of works side by side with this little bit of marketing on the machine, a lot of the time. There are some other things we've done, like doing some clicks on the email to the app and we're also tracking mainly for like when you have some kind of cell phone and we want to be able to see tokens across like different devices and no clicks are going to be able to do that. So, but I would have to look specifically at how the form is actually going to work. Like even the stuff with HubSpot, so you can like squeeze it, we have another module called CTA module which I'm doing this over. And if you either put like regular graphics in a piece of the year, so like they're, you can put like a graphics CTA or you throw in like a HubSpot CTA and it will definitely appear on CTA. There's your JavaScript. So then it'll track those. So there's like for HubSpot it's a sub module that does how to do, that adds a JavaScript to deal specifically with that platform. So like we're ready to do, we've done more kind of integrations a few years back. We just haven't done one recently. So we probably just build a sub module that they would do the special things like the special form processing and all that kind of stuff. They hope you're gonna be able to do that. They hope you're gonna be able to do that. Right. Right. And then that's the other way to go. Normally you've got the JavaScript form that you did in bed. The other way to go, in fact that's like the way we run our contact form. And then it's actually very straightforward because the system kind of is meant to work really well with web form. And so it's almost even easier if you do a web form submission first because then all the data is there and the visitor gets created and all that kind of stuff. And it stores the HubSpot. Like it looks from a HubSpot because HubSpot is tracking them too. And so it's looking for that token that stores that, then it knows how to sync with the HubSpot visitor. Sure. Did you show like a demo or a video or something? I mean, say I ended up using a video. I was like between this and something else and the other one I was there for a while and realized this is not going to help work. So I should probably go over to Intel before. Yeah. Yeah. I did not, no, I was just running through a presentation. But people weren't happy to show a demo. You know, like I said, we got a system set up downstairs. He's got six monitors downstairs. Yeah. Yeah. I just wanted to say thanks for all your effort for creating that. Sure. I appreciate you guys for doing a lot. Oh, cool. You used your SEO modules for years now. Cool. Cool. You know, like, gosh, I've got all these options that I've been out to. Because we've been put a ton of work into this drill, which kind of brings together all the SEO stuff and social media stuff and Intel stuff. So that was all I got, all the little blogs and the keyword research and all that part of Open Enterprise. Yeah. Is that what Open Enterprise Pro is? I know this is one of your search points. So, yeah, so here's how it's... I was trying to, you changed it again, I guess, recently because last time I looked at it, you had something about Intel. But then just now I looked at it. Sure, yeah. Yeah. You got Open Enterprise Pro, Intel, R&R, and Pro almost like it's actually the site where you set it up so people can build sites or... Yeah. Yeah. A little bit of what I needed to do was tell my CFO that. So, because he sort of accidentally changed the brand name. It's a nice layout. I mean, I mean... No, no, no. I was actually confused, I was like, okay, I'm going to open Enterprise Pro. What ended up happening was, actually, Intel wasn't really originally called Open Enterprise Intel's level 10 intelligence. Yeah, that's what I remember about myself. Yeah. And then what ended up happening was, is that the guys organizing the main guy kind of organized his conference, or when you're doing the work, he has been kind of calling it internally OE Intel. And then I remember like one day I said, well, it's not called OE Intel. Like, you know, it's just your internal name for it, I never really record it on that. But then I was like, oh, okay. Hey, Tom. They're done. Thank you. Hey.