 Well, welcome to the dig-in session with Emma. We're excited to have you here. We're going to talk about how the International Mountain Bicycling Association built a system in Drupal 9 with Civis Herum for peer-to-peer fundraising and campaign to support trails all across the country. So, you're here and you should care about this because I think that this is a great example of a project that really does have it all. It was a big enough project that there was a good discovery phase. There's lots of different people at the table who needed to be involved. There's lots of money involved. This is a very physical job of shovels, building trail, impacting and benefiting local communities and the infrastructure of local communities. And there's really good tech. There's both the use of a little bit of custom development, lots of contributed models, so creative and strategic site building, all to have a system that's really been running solid with no issues, minimal issues since 2020. So this is not a recent build. It's been upgraded into Drupal 9. It was in Drupal 8. And that's a success that there's been that stability in the growth and the time and is why you are here and why you should care and be excited. Okay. Hi, all. My name is Leah Worley. I am the Digital Projects Coordinator at the International Mountain Biking Association. We call it EMBA for short. That's a really long name. I work into departmentally with EMBA and then I basically coordinate and manage all of our projects in the digital atmosphere. A little bit more about EMBA. Our mission is to create, enhance and protect great places to ride mountain bikes. Our current focus right now is more trails close to home. Our goal is to grow the quality and quantity of trails throughout the United States. So that basically everyone has more trails close to home and iconic backcountry experiences. We've been the world leader since 1988 and are the only organization focused entirely on trails and access for all types of mountain bikers. So we teach low impact riding, grassroots advocacy, sustainable trail design, and we love cooperation among all user groups. We are a national network of 280 local chapters and affiliates. We have about 36,000 member base that is comprised of individual mountain bike riders and passionate volunteers. And I'm Jenna Dillett and I work with Square and I like to say about myself that I love people and I happen to work with software and that's really been my journey. And I work with Square as I mentioned, we're open source software champions. So we've been in the Drupal space as an agency since 2008. We also work with a lot of CRM systems and so very much I think a back end shop. We do front end too but we spend the most of our time with our clients supporting them with their membership structure, donations, event management, email campaigns. And because it's hand and glove integrated systems, how does those systems work together? How can we help improve the processes of the team members that are in these systems day in day out? So over the course of the years since we started, since 2008, we've also, 10 years ago, then started into hosting. We have our own mail server and so we're a long term technology partner to the organizations that we work with, which one happens to be EMBA, which we're excited to present together today. Alright, let's get in to dig in. Dig in is a peer to peer crowd sourcing software that was built by Square on EMBA.com in 2019. We launched it in 2020 and it was made possible by our founding partner Shimano. Our first ever dig in campaign was in 2020 like I said and we've been hosting the campaigns year round since launch. We found great success with this platform. Dig in truly bridges the gap between national and local fundraising efforts. The dig in program is for our not for profit local partners, so EMBA chapters and local affiliates. We recognize that all trails are local and we built this platform to give mountain bikers a way to support projects in their own backyard and at the national level. So we host an application period every quarter where local leaders are encouraged to apply with a specific project in mind. We consider various types of projects. Some include projects on public lands that are free and open to public users. That's with mountain bikers as the primary user group. We also consider projects that result in a visible and sustainable increase in access, improve mountain bike experiences and generally provide a greater community benefit. Lastly, we consider projects that promote community development, youth riding, new rider engagement and engagement with marginalized communities. Some examples of projects that have completed a round of dig in are the Central Michigan Mountain Biking Association. They needed new tools for trail building. We also worked with B Street jumps in Southern Oregon to improve local built bike jumps. Another example right at the end there is in Central Iowa and they wanted to integrate trail in green space. So the dig in platform displays a full listing of current projects as well as individual project pages. The individual projects pages include a story about the project itself and a donate link. Communities are encouraged to get involved in raising funds. And dig in is often referred to as a kickstarter for trail building. IMBA collaborates with partners to put as much money as possible to local trail efforts. Our ongoing partnership has direct benefit for local communities. No matter what, the first $2,000 that's been raised on our dig in platform is matched by Shimano for the project. Getting into some statistics after, so we launched a project in 2020. We've had five rounds of dig in so far. That's with 52 completed and approved projects. We've had nearly 1,400 donors give over $190,000 resulting in a $77,000 corporate matching support. What's really astonishing is the impact that projects have had with dig in have gone on to leverage $895,000 in additional support for trails. So this is just a little graph of dig in quarter after quarter for the five quarters that we've hosted it. As you can see $25,000 has been raised in online donations for each round. Distributions to most chapters has been even higher due to that corporate match. We can kind of see how important community fundraising efforts are and they truly are what makes dig in so successful. So rather than list all the projects because that would be long and boring. This is an interactive map that displays all IMBA local chapters that have received dig in funding. As you can see projects actually follow a mountain range, the Appalachian mountain range. Sprinkles of projects are in the Midwest and West. Our next application period starts on May 1 with projects going live in June. So let's get into the technology and how we built it out. Yeah, so how did we do this? Which I think what I want to point out and we'll hopefully remember is this is one use case of the same tool set, which is the beauty of Drupal. It's just a pile of Legos and a little pile and you get to put them together in a different way this way. And so I think that there's a lot that we're going to show that could apply depending on what kind of organization you're with. Maybe it's a grant application that's not for public display. Maybe it's case management. Maybe it's some sort of other application process in a way that's managed and displayed. It's the CRM integration component that really opens the door of capabilities. And this is just one use case, of course, a case study, but there's lots of ways that the same model could be applied. So looking at the technologies we used, basically use this. We used Drupal and we used CVCRM. Like I mentioned, we used Drupal web form. We used web form CVCRM and CVCRM entity and Drupal views. And that's what we used to build this. I think there's one little custom related to views, but otherwise everything I think is strategic site building and some theming. One of the things we considered was the web form content creator Drupal module, where you can have a web form submission and that automatically creates content. Then you could have content moderation. We went down that path when we were in the discovery process. We ended up not using that, but just thinking about other tools that are out there that could achieve a similar variation to what we built here. I do want to touch on, we are at DrupalCon. So I wanted to touch on what is CVCRM since it is a piece of this project. You could have a similar project and have a completely different CRM system that would still work with this and have the same model. But in the case of this is a good opportunity and plug for another fantastic open source project out there, which is CVCRM. And it has all of these features. You can read the bullet points for yourself as far as what it can manage. And it's what EMBA and many organizations rely on and it's hand in glove with Drupal. And so it lives with Drupal, it can't live on its own, it lives with a CMS system. You can see that it lives with Drupal WordPress, Backdrop and Joomla. Are the CMSs that it can live with? So how we use CVCRM, it's basically our house. We configured CVCRM to fit our needs. Most of the functionality is out of the box features as well as contributed extensions. We primarily use it for memberships, donation management, event management, email marketing, tracking corporate support. Campaign management and most importantly is revenue sharing, which we will get into in a little bit. So this is our leader dashboard. It's unique to EMBA. It's a custom Drupal model that leverages CVCRM data. For local chapters and affiliates, it's essentially a CRM for individual chapters. So chapters can manage current and expired memberships. They can track their donations and contributions. They have access to EMBA provided resources. They can send mailings to their members and they can apply to programs like Digin. So looking at what we wanted to do with this project is that what you're seeing here is the application within the leader dashboard. Any chapter leader across the country of the over 300 chapters of EMBA would log into, it's on the website, it's all integrated in one place. This is where they can go and see all the memberships that they have, the statuses of those memberships, run reports, send mailings because of those statuses. With the Digin project we needed to integrate that in the same place that they were already used to go and keep everybody centralized and taking action where they're already taking action where they're already going for information. And so thinking about that application process, they should be able to view previous submissions that they have from other campaign periods or request a change to an application. All of that is within the same user interface that they have to do all their reporting and the actions that they can take, which is a significant value offering that EMBA provides by being a chapter leader. You can easily be a bike club, a mountain bike organization. That does not mean that you're an EMBA affiliated organization. And so that technology offering that EMBA provides to the chapters, which is administered through this dashboard, which is all Drupal and Drupal module that happens to display. CIVICIRM data, because it's all within the one integrated system, is a powerful offering and having Digin, that project embedded within the offering, expands the capacity and that value offer that EMBA provides to all the chapters. So the application features in general, we should have these application desires whenever we're filling out anything online. Can I save it as a draft? If you're going to ask me a bunch of questions, I don't want to have to know all that right now. Or I need to be able to know all the questions and be able to collect that information so I come prepared. It updates contacts automatically because it's directly interfaced with CIVICIRM, then it updates or creates new contacts. And so with those contacts come relationships. So I'm a land manager of, I am the executive director of. So then EMBA can view and track and create groups and run searches based on relationships that exist and track the engagement of those individuals over time that they may be part of multiple campaigns or multiple organizations that EMBA is working with. If you know web form, Drupal web form is super powerful, easy to use with some training of conditional logic, validation rules. All of that applies to keep an application process, only asking the questions that it needs to. Once information is filled in, provide more questions or more clarifying information. And all of that is site building, right? That's configuration. There's no custom there, just building a smart web form in the integrations. So this is the web form, right? This looks like a web form. You can see in the key, you see this little thing, CIVICIRM. That's because those are CIVICIRM elements. And so if we look on the next slide, we'll see what that looks like with the integration of Drupal with CIVICIRM. There's this nice little check box of, do you want to enable CIVICIRM processing? Yes, check the box. And then what that does is allow you to select through this UI what fields of CIVICIRM do you want to have as part of the form. Those become then web form elements that then you can manipulate and control and have logic and everything that you would with a normal web form component. So in this case, you can see along the left-hand side, we have up to five contacts that the web form submission automatically creates or updates upon web form submission. And from this UI, we can decide which fields are being collected, even if I want to collect, say, multiple mailing addresses. This one is a billing, this one is main, for example, of different address types, which depending on the CRM structure you have, those differences can be very valuable. Don't send mail to this one, send it to this one instead. The other powerful thing that the integration with Drupal web form, so it's Drupal web form, and then the other module is web form CIVICIRM. There's a training tomorrow that's happening I think at 11 a.m. that Karen Garretzen is leading that goes deeper into Drupal web form and all of the power and options related to integration with CRM. The other great thing about CIVICIRM in this project is the concept of an activity. So in CIVICIRM there's different activity types. You can have custom activity types. We can see upon this Drupal web form submission that automatically creates an activity type of dig in, and then it both assigns and adds participants of that activity. And so that's part of that ongoing management where Imba's team only has to change one thing on contact records. And then we'll see later on with examples of some views within the system, how that then automatically, because of site building, updates what the active projects are to front-end visitors to the website. So going in a little deeper into Drupal views, what we used heavily because a lot of the data itself is coming from CIVICIRM is the CIVICIRM entity module. And what's great about that is that people can develop in a CRM the Drupal way because with CIVICIRM entity it basically allows a lot of that CIVICIRM data, whether that's contact information, address, event participation, membership. All of those data points can become true Drupal entities, and then you have the beautiful collection of all contributed modules and tools that are available for development that then can be done the Drupal way. And so that's a beautiful thing about at Square of getting to do that work that we have our Drupal developers. We do a lot of work with CIVICIRM, but we can do that work using the Drupal skill set, the Drupal tooling that is robust and maintained by such a large community that's much bigger than the CIVICIRM community. So kind of the best of both worlds. So just want to highlight that as far as Drupal con and still being able to develop with CRM data and an integrated system doing it the Drupal way and taking advantage of tools that exist. So this is an example of a view. This is what it looks like on the front end, you know, we're pulling in the title, we're saying it's a project of what that's populating the name of the chapter. We're having a calculation that is dynamically saying how much has been raised so far out of the total and then the description and ability to view more details. Here's what that looks like. You can see from the filter prescript filter criteria is it's looking for specific activities based on that activity type that we talked about earlier and also the status of that activity. So all the EMBA team has to do is change the activity status and then that's what triggers and has the information show. Otherwise, all these fields that are displaying such as the funding goal, the location, the description, who the land manager is, all of that data is coming from the initial Drupal web form submission. And so there's no take a paper application or take an online Google form application and then somehow manually or import or bring it over. The application is approved, the data is there, they just decide on the overall status of the application approval and then with this, those projects can automatically show up on the website. So very little management is needed. And also it's site building, right? We've got a web form and a view so far that is doing this work. So learning more, this is kind of that landing page. This was on a previous slide. We've got the photo that again was part of an upload that's in the initial web form of the application and the ability to donate. And you can see the calculated total that displays above so people can know the standing at any given time, how much is being raised and what their impact will make. So the donation page is critical. When we thought about the way to do it, then everything points to one form, one form rule them all. So if any changes need to be made in the future, there's just one place that we need to do that. And so what we're using here is taking advantage of CVCM campaigns, which is a kind of a component within the CVCM system that's just out of the box. A contribution page and then reporting which you'll see a few examples of. So this is a donation form which you would expect it's very simple. You select the amount you want to give or you enter the amount that you want to give if that's not in the option list. And then you enter your information and there's a little, my donation will support. This is where we're having it automatically calculate and go to the specific chapter based on what the campaign was for. So if we look at the URL anatomy of that, then you can see how it's broken down. I copied it so you can look at it more easily than I can describe of which pieces of the URL component are pointing to what within the system and how that breaks down. So the photo at the bottom is just that basic profile. So in a sense when you set up a contribution form in many systems, you're specifying what are the fields that you want to collect about the donor, right? So you could add more fields in this example. This is the form and this is all the information that's being collected. The would you like your donation to be anonymous, that's important because that's related to the chapter reporting. If I'm a donor and I don't want you to know I just gave $10,000 because I was generous and I don't need you to follow up with me about that. I'm going to make myself anonymous. They can still see that they got $10,000. They don't ever get to trace that to me. But EMBA needs to know, right? So there's some accounting so receipts can be given, but that doesn't mean that the chapter gets that information. So that information is critical related to when we think back to the leader dashboard and that UI where chapter leaders are going and managing their information, downloading information, having their own marketing strategies for how they follow up, then that's the information that they need to only follow up with those people who have given them permission to follow up. Yeah, so let's get into revenue sharing. This is easily probably one of the most important things about this project. Our revenue sharing reports are as straightforward as possible. For dig in, we bundle the report by campaign realm. We can easily see how much the project is made in online donations and then we can also see our 10% retainer for each project. We can also see the $2,000 in corporate matching support if they reach that amount as well as the total to distribute to each project. It's straightforward. It's easy. It's important to keep our finance team happy and out of the weeds. And just by retaining that 10% in total donations, we'll be recouping the initial investment this year. And I want to add that was an important piece in the initial scoping of and we'll get into that later too, but thinking there are a lot of peer-to-peer fundraising platforms already out there. So why reinvent something and put it in a Drupal site when you have so many other options? And so looking at the math of what the project was going to take, but also what EMBA gets paid back and the other benefit of keeping donors, keeping chapters all within one place, there's a lot of added value of what else EMBA can do and teach and show and do shoutouts for by having the audience kept within the site that has maybe not always a direct financial value, but I think if that is the long game. And so there's a lot of intangibles separate from just the dollar's amount of having the investment done in the system and also being able to track because it is dollars to know when it's paying back for itself then absolutely makes it worth it and beyond the intangibles. So in the chapter reporting this is back in the leader dashboard like we've seen. So we're still in the kind of that dig in area of the system. So at any given time a chapter leader can log in via EMBA's website of emba.com slash user and can log in, go to their dashboard which shows their chapters information, see their membership and also if they have an active campaign see all of the donations that are being made on behalf. The way that shows up from a financial perspective is that though those chapters are soft credited on the contribution for the way that reporting happens within the CRM system. And then they can see the individual names and emails which we have blocked out for privacy, the zip code, the amount that was given and you can see the ability to download that amount in addition to the summary of how much do they get to take home automatically, what is the match for that and that's the big batch. Before I was on kind of the tech agency side of the table I did, I worked in fundraising for a human service organization in endowment building and I know from writing a lot of grants that it's projects like this that end up being the matching dollars for even another funding source. When you're doing physical projects like trail building it is the combination of so many sources that make something possible, so many different partnerships. And that can be the same thing in very different models for very different organizations that are likely represented in this room. And I think that the creative use of site building with a little bit of customs, that's the power and beauty of what can an agency do if you know the tools really well. You can know what you can get with lower effort and then that additional effort is very specific in what it's going to achieve and I think that this has been a good project for that. And a really easy straightforward UI for chapters to pull real-time information and download and take action further external to the system to grow their impact. Alright, let's get into a little bit of our marketing channels. So part of what makes Dig In so successful is due to our great marketing around each campaign. Some of the ways we market for Dig In is through targeted email based on locations. We email our members within like a 75 to 50 mile radius of each project. We also deploy mass emails to our entire member base just about Dig In as a whole and when it's opening up. We send emails to our local leaders to let them know that an application is soon to be opening. We promote individual projects via social channels primarily Instagram and Facebook. There actually are leading referral every time we host a Dig In. So Dig In pages are built with that campaign specific URL and that actually pulls in project metadata so it's great for individual sharing as well. So search in CVCRM is a great tool that we utilize for basically actions based on data results. We create smart groups. It's essentially a saved search. We use basic groups for mailings. We do bulk updates in CVCRM search. And then we also export the donor list for comparisons. So donor logs are really useful for both us and our local partners. Personalized thank yous go a long way in nonprofit fundraising. This is actually how we learned a pro mountain biker donated to Dig In and we actually ended up reaching out to him and he did a promo for us and for his local trail. So yeah. Yeah. The other thing I want to add about separate from CVCRM is just a way to gauge CRM power in general is how many steps are there between getting the results you want and being able to take action on those results. And so I think as a gauge of any CRM system or even when you're looking at strategies of building out something on your website. What are the steps taken between the results you want and the actions you want to take. And ideally there's as few steps as possible. And so that was something that we looked at to knowing that that'll be the success of the project. How quickly can the team be able to find and then update find and modify find and do anything related to the data with this. And we wanted to keep those steps as short as possible. So this is basically how we send out mailings via CVCRM. We basically just use generalized tokens. We also have quite a few custom tokens that are basically chapter name chapter URLs stuff like that. Our mailings are generated through CVCRM core and then we also provide the same interface in our CLD our leader dashboard so that chapters can send mailings about dig in directly to their members. So we want to talk about the process a little bit which gets into how our projects like this run because it's a really good reminder and especially having a couple years since it was launched to be able to reflect back and look at other projects that we've done together. Whether that's with IMBA or with other organizations to have a reminder for ourselves and everyone here at Drupalcon as far as what what leads to success or what would lead to better success in the future. We were to do this again. So the first thing I want to talk about is people and that should be no surprise since I like people and happen to work with software. One thing that I've always been really impressed at at IMBA is the way that they think very smartly engaged their board leadership. In this project we actually had a couple liaisons from the IMBA board of directors who are also chapter leaders of their local mountain biking club that had a very unique perspective. They've been involved with the organization for a long time. They had a vested interest in their local community for this to be successful and how they would raise funds and expand the effort of their local initiatives and also inform and work with a technology partner. Being on a call with a technology vendor is not often the case and shouldn't often be the case for board members but I think for unique projects unique involvement is critical. And so the important thing of having a lot of people around the table sets clear expectations from the very beginning. One thing I want to celebrate is the surprise that Leo was not involved in the original project and is not involved in the maintenance of the system. And that is a success because that shows that after since 2020 it hasn't needed to be maintained beyond the security updates that may impact it or have to be tested again. And that a good system is built when it doesn't have to be taught extensively to someone when it's easy to pick up and clear to know what needs to be done. And that a key to that is documentation which we'll get to so having the right people doesn't mean that it always has to be that person. It's having the right people in positions knowing that people change but the system needs to live out whoever is in a specific role because people change jobs. The next piece to point out is having a clear discovery process having things thought through with due diligence understanding those expectations and having that in writing and going through the full workflow before anything begins. And of hailing back to the old grant writing hat. It was really important for our team to understand the expectations from a reporting standpoint of Shimano or any of the other corporate supporters that Mba has. That way if they need data we need to make sure that that data is being collected in some way and is reportable in some way by Mba rather than finding out after lunch. Oh you need to send what kind of report for who. I guess we should figure out how we're going to pull that together. So putting all of that on the table of even reporting requirements to funders that very much impacts the technical implementation. And that may not be solved with code but that's absolutely a critical question that needs to be included in from the very beginning. The next is roles and accountability. The old tagline of having the right people on the bus and also in the right seat. I think that was important from a testing perspective of who was going to do what. What was the square team going to do. What was Mba going to do. At Square we support organizations who have all levels of technical ability. That may mean that for some organizations we do things that we don't technically have to do that with a little bit of training they could do themselves. Which means that it's always a choice or can be a choice of who is doing what. And I think as far as due diligence for organizations to make sure that they can own and do what they can own. That's something that is good to ask and remind a technology partner. That's which is like a little rabbit trail which Leah knows I like to go down. But as far as accountability and being able to do and own what you can do as an organization instead of having things kind of hidden behind a curtain of well that's technical. It might not actually be that technical or technical at all. And sharing that work can also help share and lower the cost. And so having those honest conversations and questions with your technology partner then directly affects that time spent report which directly affects budgets. I mentioned documentation before and that's really been the thing that has kept this a really well oiled machine smooth sailing ship. We had very clear written instructions with with screenshots of what needed to be done at every quarter. And so this is quarterly. So there's one update that needs to happen on the web form once a quarter. The campaign period needs to change instead of quarter four twenty twenty one quarter one twenty twenty two changing the quarter. And then also bulk updating all of the previous applications that were already submitted. And so it's really three main actions that the team needs to take with clear screenshots. And once that documentation was developed then the team has been able to follow it. Another really simple thing that has been very valuable is within the system. There's a Drupal content type called documentation and based on permissions only in the staff can see it. And so not only is it a place that they can put their own SOPs for whatever sort of technical function or reporting or content management workflow that they want to have for everybody. It's a place that our team puts documentation that way if we ever have some sort of bad breakup which I don't expect. It's not like documentation and training resources are living with us. We think that it makes a lot of sense for training materials to live within the content management system that it's about. And having that centralized and using Drupal as a content management system to also manage documentation. You've got tagging. You've got beautiful views to have filters of resources. And then having that tied into when new staff are onboarded into EMBA makes it that much easier to know where things are. And stuff doesn't get lost in emails or Google folders or wherever stuff often ends up. And so having that clear plan and having documentation for this project live within the documentation architecture of how we have all the other SOPs that we develop as well as SOPs that EMBA develops for their own purposes that may have nothing to do with the way we work with them has also been a key to success that this utilized but is used across the board with other things they do. And then marketing. I think a lesson learned the hard way is that sometimes on the agency side if we're focused so much on the technical what's going to be implemented. Does that work right? Does it look good in all screen sizes? Then one question that we have not always asked is how is this going to be launched? Do you have a communication plan because so much of that acceptance of the end user base depending on how much of a change the new technology represents. That has its own life and can affect the technical project in unintended and interesting ways. And so I think I've learned the hard way to realize that we need to support and partner and make sure that there's a communication plan and strategy. So when this is launched have there been communications that have timed out in enough advance that people know what's coming and how they can interact with it and take advantage and then that's really a success. It can work great to everybody else. But if no one knows what it's supposed to do or that it's newer that it was coming. Those kind of riffs can take a beautiful technical project and it might not be as well received as you were hoping. Unfortunately that was not at all the case with them because we did think about that from the beginning of what is a communication plan. Yeah so Diggin continues to evolve. Originally it was a lot of hands on work for someone who is in my position but now it's a well-oiled platform and I am completely hands off when it comes to running Diggin. You know Diggin has provided a platform for local leaders to bring trail and mountain bike projects to life. We collaborate with our industry partners and successfully like accelerated the pace of trail building across the country. We really bring together the bike industry and local communities to make all these fundraising efforts a reality. That's Diggin. Yeah so reach out to us. Contact us if you have questions. Again I want to reiterate the power of a good partner is knowing the tools well enough to know what you can start from and what you can start with. And I think that's one of the things I'm most proud of with this project is that our team knew the tools that existed which meant for a very straightforward after all the discovery is done as far as what implementation look like. It's really fairly simple tech and it has had a significant impact and there's so many use cases related to I think applications of any kind. Any time you have a form online you want people to enter information. You want to share that information back with them or with others in some way. You want to have that tied into a CRM system. It doesn't have to be city CRM. Drupal is such a powerful tool for that and that does not mean that you have to have an experienced developer do the work. A lot of that is knowing what the system is capable of and really good business analysis and I think that this is a great showcase for that. So we'd love to have conversations afterwards or follow up later. We do have several minutes. So if anybody has questions or follow up on any of this we'd be happy to answer. Yeah question in the back. They are anonymous. That was critical to lower any sort of barrier at all. So you mean I was thinking so the donors so that give to campaigns on the donation form. Those are all anonymous as far as the ability to submit a dig in application. That is absolutely authenticated. That's only allowed for in but chapters and so it can't just be any organization. That's why it's through that leader dashboard which is very much a permissioned authenticated space where you have to have even an organization. And a specific leadership within the chapter in order to access that space since it has all that personal information of members contribution history of members and also the UI in order to submit an application to be considered a dig in project. Yeah that would be that would be quite the vetting process. Yeah. Yeah that's a great question. So most of our chapters have their own websites so whenever they're looking at Google analytics or anything like that. They're looking at their own Google analytics. As far as our leader dashboard I believe they do have access to mailing reports so click through summaries. Link clicks everything like that amount of opens views stuff like that they do have access to within our leader dashboard. No we generally do not share that information. They're a team uses brain tree as a payment processor so that allows for either payment by credit card or PayPal. Yes that is hosted so as part of core CV serum then it you can set up with all of the major payment processors. So Stripe PayPal authorized on that many others and brain tree being one of those. And so that's configured those settings for what the payment processor in is configured within CV serum and so that's automatically you never leave the website. You enter in your credit card information click submit and are redirected to whatever page and but wants you to be on after you submit the contribution but it's all within one system that hand and glove of civilian Drupal living together right here. I mean it was like was it 2012. I mean it was a choice of the organization so long ago. We started working together. Square started working with Mba in 2008. And 1818 and the system was already really established by then I think when you have as large of an organization and as complex of a data structure a number of members and contacts and relationships between contacts and events then it's never been a question on the table just because a change would be so significant. And the system meets their needs. I mean I'm under no delusion as far as what the UI experience is. It can look a little dated but that's that's the engine in the car right is the engine good is or is it just the paint. But that's for another conference. I mean I absolutely would. I work at an agency that we are just as strong Drupal developers as we are city serum developers. And so I think we know the unique power of both systems. I think like any serum evaluation process it should come down to what are the needs of your specific organization and depending on those needs it could be that there is another serum tool that's available. I think because we work we work with so many membership associations or universities where they want to have that integrated experience and with the power of the two systems together there's so much that can be done through the UI which just lessens the learning curve of what can be done since a lot of it is configuration based that that puts a lot on the table. And especially at Drupal Camp knowing how many fantastic contributed modules there are and even what's in core to be able to leverage that and have that available for your serum data as well and have that in one centralized place. I'll take a bad UI any day that can be improved over time as far as the flexibility that that provides but that doesn't mean that that's the solution for everybody. I just know I've seen that the benefit over and over again of that flexibility that pile of Legos the open source nature of both platforms represents just that much bigger of a pile of Legos on the floor that we can creatively build what we want. Any other questions any other mountain bikers out there. Dabble awesome. Yeah well thanks so much I think everyone gets to have 10 extra minutes or if we I don't remember maybe we're actually two minutes and we're right on time. Thank you so much for coming.