Display.Church: How it works with Pushpay (CCB)

Learn more about the specifics of the D.C - CCB/Pushpay integration.

Jason Alexis avatar
Written by Jason Alexis
Updated over a week ago

This article is a quick overview of how Display.Church (D.C) connects with your Pushpay/Church Community Builder (CCB) data. A 'deeper dive' overview is available here.

Which Display.Church products are available?

At the moment, all of the D.C products are available to CCB users: Calendar views, Groups widget views, and Event ALERTS.

Which event filters are available?

Filtering is done in the Setup Tab. Here is a list of the data filter options:

  • Show private events: Display those events which are marked as hidden in CCB.

  • Show events with images only: Just show those items which have some sort of picture or other image.

  • Merge recurring events: Show only 1 occurrence of events which repeat.

  • Filter by group(s)

  • Filter by campus(es)

  • Filter by department(s)

  • Filter by location(s)

Can we include CTA forms?


For calendars, D.C. can link to your CCB sign up forms and RSVP forms.

For groups views, we offer up to two CTA buttons and a number of linking options (see dropdown menu in image below).

What does the integration process look like?

Basically, you will need to log in to D.C, go to the Integrations page, and give D.C permission to access your CCB data. This is called SCOPES.

There are four permissions:

  • Mandatory: This scope is used to identify either Calendars or Groups data across your Church.

  • Calendar: Permission to pull your events from your public, groups and individuals calendars.

  • Groups: Permission to pull your groups so you can filter events by groups.

  • RSVP: Used when a person RSVPs to an event.

Each permission requires certain API services to be turned on.

How to give permission:

Check the items you wish to use. The box will turn blue.

Uncheck the items you do not wish to use. The box will be greyed out.

Did this answer your question?