Over the last few weeks, there’s been a bit of excitement in the world of Church Community Builder, also affectionately known as CCB.
I use “excitement” loosely as many churches using CCB’s API were informed about CCB implementing a new per-minute rate limiting policy in addition to its per-day allotment of 10,000 calls per day — which they hope to retire sooner rather than later, yet it’ll remain in place for now.
As of August 20th, this new rate limiting strategy aims to restrict how many times per minute an API user can access an individual API Service — noted in New API Rate Limiting documentation.
So, what does this truly mean to you, and more importantly, how does this new strategy impact developed applications and environments using CCB’s API? 🤔 Read This Tutorial
I’m back this week with a tutorial that is sure to get the wheels spinning in your head about your church and where its attendees and members live.
The purpose of today’s tutorial is to show you how to create two simple dashboards containing the following:
- Number of people and percentage based on Zip Code
- Number of people and percentage based on City, State (next week)
Why is this information important? Well, thanks for asking. 🙂
If your church is a growing church, no matter the size, then such reporting gives greater insight as to where attendees and members live and travel from to reach your church.Read This Tutorial
Today’s tutorial will help many of you plan for custom application development using CCB’s API.
You could meet the daily CCB API call maximum if you’re not careful. Maxing out to the CCB API limit could leave reporting, emailing, backup, syncing and other API-dependent applications dead in the water for a day.
I suggest planning out how many API calls are made within a given day. Also, don’t forget to define and plan for how many applications are created that use the CCB API.Read This Tutorial
Today’s tutorial is sure to open the flood gate of opportunities for how you use your CCB account data in an automated manner.
Most of us are quite familiar with CCB’s Process and Queues. From Connection Card follow ups to church Membership to messaging and communications, Process and Queues provide a structure and system for tracking attendees and members for a variety of church workflows and processes.
Although Process and Queues provide a church with an advancement in system tracking and communicating, one of the areas that it lacks is true automation. What I mean by true automation is that CCB lacks an automated method to message, communicate and process persons via Process and Queues.
This means that for every Process and Queue created, there always has to be someone to man the system. This can be good and bad depending on the size of one’s church they manage, and church staff to man the system.
So what does this automation business have to do with backup? Well, I’m glad you asked! 🙂 Although CCB backs up your data, I’m going to show you how to backup your data to an external source other than CCB.
As for further automation, I’ll have to cover more of this in up coming tutorials. For now, let’s get started on getting your data out of CCB.
Keep in mind that today’s tutorial can help you if you’re looking to migrate away from CCB to another provider, and help you if you seek to automate some simple tasks without hiring additional staff or putting more on the plates of your current staff.Read This Tutorial