Planning Center Giving on Your Website: What's Public, What Isn't, and What Breaks
This is not a post about how to run year-end giving. We are not your accountant, your administrator, or your stewardship committee, and the decisions those people make are theirs.
This is a post about the seam between Planning Center Giving and your website: what Planning Center will and will not hand over, where the responsibility changes hands, and which parts of the website side tend to break quietly. December is a bad month to find out any of it the hard way, which is why September is a good month to check.
Planning Center decides what is public — your website does not
This is the single most useful thing to understand, and it is the source of most "why isn't our fund showing up" questions.
A fund appears on your website because it is set to be visible to everyone inside Planning Center. Not because of anything on the website. If a fund is not marked visible there, no amount of work on your site will make it appear, and that is correct behavior rather than a bug.
The same principle runs through every piece of Planning Center data you can surface publicly. Your website never decides what is public. Planning Center already did, and your website is only allowed to reflect that decision.
Two practical consequences:
When something is missing, check Planning Center first. The website is almost never where that problem lives. Start with the fund's visibility setting before anyone opens the site.
Your visibility settings are your publishing controls. Whoever manages funds in Planning Center is, whether they think of it that way or not, deciding what the public sees. That is worth saying out loud to the person doing it.
Where the handoff happens
Your website's job ends earlier than most people assume.
A giving element on your site can show your public funds, and campaign progress if you use campaigns. When someone decides to give, the gift itself is handed off to Planning Center. The transaction, the card details, the receipt, the fund accounting, and the contribution record all live on that side.
That boundary is a feature, not a limitation. It means your website never touches payment information, and it means the record of a gift lives in the system your finance office already works in rather than in two places that can disagree.
It also means the website is not where you fix money problems. If a gift went to the wrong fund, or a receipt did not arrive, or a statement looks wrong, none of that is a website issue and none of it gets solved by changing the site.
What actually breaks, and it is always the website side
The embed broke and nobody noticed. Any change to your site since last December — a theme update, a plugin, a redesigned page, a new cookie banner — can stop an embedded giving element from rendering. It fails silently. No alert, no bounced email, no error anywhere you would happen to look. The only way to know is to check.
Giving is only obvious on a desktop. Church websites get designed on a laptop and visited on a phone. When navigation collapses into a hamburger menu, "Give" often collapses with it.
The page is slow on cell data. Test it on a phone that is not on the church wifi.
There is no giving link where the thought actually occurs. The giving page is rarely where someone decides to give. Sermon pages, the livestream page, and the weekly email are.
Test it the only way that works
Pick up your phone, go to your website the way a visitor would, and complete a real gift. A few dollars is enough.
Almost nobody on staff does this. Staff navigate from memory, or from the admin side where everything already works. The visitor's path is the one nobody walks, which is exactly why it is the one that breaks.
Where we are not the authority
Some of the most common year-end questions are not ours to answer, and we would rather say so than guess:
- What date you should stop counting gifts toward the current tax year
- How mailed checks and online gifts differ for that purpose
- When contribution statements should go out, and what belongs on them
- How your funds should be named and structured
Those are decisions for whoever prepares your statements and advises you on them. What we can tell you is where the settings behind them live in Planning Center, and how whatever you decide gets reflected on your website. Ask the right person the first four questions, then come to us with the fifth.
One honest limit
If your giving runs through a standard embed, it will largely look like the platform it came from rather than like the rest of your site. Fonts and colors will not match, and there is a real ceiling on how far that can be pushed. That seam is worth knowing about rather than being surprised by, and closing it is the reason wtxLabs Sync exists.
The bottom line
Check the fund visibility settings in Planning Center. Give to your own church from your phone. Fix whatever that turns up on the website side, and send the finance questions to the person who owns them.
None of it is difficult. All of it is easier in September.
Questions about connecting Planning Center to your website — Giving or anything else? Get in touch.