The Events Problem Hiding in Your Past Squarespace Projects

Somewhere in your client list is probably a business with an events problem.

The client may not call it that. They may run workshops, classes, retreats, trainings, photo walks, tastings, member events, seasonal gatherings, or live sessions. They may already have a workaround in place: Acuity, Eventbrite, Luma, a Squarespace product page, a form, or a manual process.

The setup may even be working.

But if the business depends on gathering people at a date and time, there is a good chance the website is carrying more weight than it was originally built to carry.

That is what stood out to me after a recent conversation with Kelsey from Week of the Website about Eventually, their new event ticketing tool for Squarespace.

For years, event-related Squarespace projects have lived inside a messy middle.

Acuity works when the thing is basically an appointment. One person books a time. Maybe a small group books a class. The flow is simple enough.

Eventbrite and Luma work when the event needs public discovery. They are useful when part of the job is helping strangers find the event in the first place.

But a lot of Squarespace clients sit between those two worlds.

They already have a site. They already have a brand. They already have an audience. They are not trying to make Eventbrite the center of their customer experience. They need their own website to support the way their business gathers people.

That is the missing middle.

Acuity is for appointments.

Eventbrite is for discovery.

Eventually is for the client who wants to run events through their own Squarespace site.

A client usually does not show up saying, “I need branded event infrastructure.”

A client says,

“We’re running a workshop next month.”

Or, “We want to offer this class every Friday.”

Or, “We need to know who is coming.”

Or, “We’re using Acuity, but it feels weird.”

Or, “We’re using Eventbrite, but it does not feel like us.”

That is the moment to pay attention.

The issue is not only ticketing. It is the relationship between the event and the rest of the business.

If the event is peripheral, almost anything can work. But when events become part of how the business earns, teaches, gathers, launches, or builds community, the website has to do more than point people somewhere else.

It has to hold the experience.

It has to make the event feel like part of the brand, not a detour. It has to collect the right information. It has to respect capacity. It has to help the client run the event without duct-taping another workaround onto the business.

That is the client pattern Eventually makes easier to see.

Not every Squarespace client needs it. Most probably do not.

But the clients who do need it are not hard to recognize once you know what to look for.

Their offer happens at a date and time. Their revenue depends on people showing up. Their community forms around shared experiences. Their website is not only presenting information. It is helping coordinate participation.

Kelsey used the phrase “calendar-centric sellers.”

These are businesses where the calendar is not just an admin tool. The calendar is part of the business model.

Once you see that pattern, past projects start looking different.

The photographer who now runs photo walks may not need a new website, but she may need a better registration flow.

The bakery with decorating classes may not need a redesign, but it may need ticket types, attendee details, and capacity control.

The coworking space with regular programming may not need another landing page, but it may need a cleaner event calendar and checkout experience.

The consultant running paid live trainings may not need a new brand, but he may need a better way to manage hybrid attendance.

That is a much more natural reason to reach back out than “just checking in.”

You are not reminding the client you exist. You are remembering something about the business and bringing a useful possibility back to the relationship.

“I saw a new way to handle event ticketing directly through Squarespace, and it made me think of your workshops.”

That is a good email.

It is specific. It is relational. It is tied to something the client is already doing. And it opens a conversation around service, not pressure.

A lot of designers think growth means finding a new lead source. Sometimes it does. But a lot of growth also comes from seeing a new layer of service inside relationships that already exist.

A client you built a site for two years ago may have changed. The audience may be larger. The offers may be more experiential. The operations may be more complicated. The original site may still look good, but the business may now need the site to do something it was never asked to do before.

That is where a designer can become useful again.

Eventually gives Squarespace designers a new answer for a familiar problem.

Not the appointment problem.

Not the public event discovery problem.

The branded gathering problem.

The client already has people. The client already has a place online. The client already has something happening on the calendar.

Now the question is whether the website can support that part of the business properly.

That is the question I would bring back to my own client list.

• Who is gathering people?

• Who is running recurring events?

• Who is using Acuity for something that is not really an appointment?

• Who is sending people to Eventbrite when the event should feel like part of their own site?

• Who has a business that now revolves more around classes, workshops, or community experiences than it did when the site was first built?

Not everyone on that list will need Eventually.

But the exercise will train you to see your past work differently.

A website is not finished just because the project ended. It sits inside a living business. The business keeps changing. The client keeps learning. The offer keeps evolving. The audience keeps growing.

Every so often, a new tool makes it possible to serve the same relationship at a new level.

That is what I see here.

Eventually is not just another event ticketing tool for Squarespace.

It is a reason to look again at the clients whose businesses run on gatherings.

And for the designers paying attention, that may be the bigger opportunity.

Related

For the tactical comparison, read: Acuity vs Eventually: When Class Scheduling Isn’t Enough.

You can also browse more Squarespace plugins and tools for extending what Squarespace can do.

Kleemt Review: Ready-Made Squarespace Sections and Blocks Without Code

The problem usually shows up when the page is almost there.

The copy works. The brand direction is clear. The site structure makes sense. The page does not need a full redesign.

But one section still feels too plain.

The proof section needs more weight. The testimonials need a better layout. The map looks generic. The before-and-after images need a cleaner interaction. Something on the page needs to feel more considered than the default Squarespace version.

That is where Kleemt gets interesting.

Kleemt is a Squarespace tool that lets you add ready-made sections and blocks directly inside the Squarespace editor. I would not think of it as a replacement for Squarespace, or a substitute for good design judgment. It is more useful than that: a way to keep a build moving when the page is working, but one section still needs a better design moment.

Squarespace gives you the page.

Kleemt gives you more finished sections to work with.

What Is Kleemt?

Kleemt is a no-code section and block library for Squarespace.

Instead of starting from a native Squarespace section, hunting for a code snippet, or asking a developer to build something small, you can add a pre-designed Kleemt section and customize it inside the editor.

That matters because a lot of Squarespace projects do not get stuck at the big strategic level. The offer is clear. The page order makes sense. The content is mostly there. The thing that slows the project down is usually smaller and more annoying.

A logo row needs to scroll.

A comparison section needs to feel cleaner.

A proof section needs more presence.

A visual break needs to feel more custom.

A client wants “just a little more” from a section that Squarespace can technically create, but not quite in the way the page needs.

That is the kind of gap Kleemt is trying to fill.

Native Squarespace Is Usually Enough

I would not add Kleemt to every Squarespace site.

Squarespace already gives you a strong base. You can build pages with text, images, buttons, galleries, forms, products, lists, videos, and layouts without touching code. For a lot of sites, native Squarespace is enough.

And when it is enough, I would leave it alone.

A tool does not need to be added just because another tool exists. If the native section looks good, works on mobile, and gives the client what they need, there is no problem to solve.

The better question is what happens when the native section is close, but not close enough.

That is where the project can start to get heavier than it should.

Where Squarespace Starts to Feel Limited

The phrase I would listen for is:

“I just want this section to feel better.”

That sounds simple. It usually is simple in the client’s mind.

But inside a Squarespace build, that request can send you in five different directions. You can settle for the native version. You can start writing CSS. You can search for a plugin. You can ask AI for a snippet. You can bring in a developer. You can spend too much time forcing a default section into a layout it was not really made for.

None of that is dramatic, but it adds drag.

The page did not need a full custom build. The client did not ask for some wildly specific interaction. The section just needed to carry the content better.

That is the native wall.

Not because Squarespace is bad.

Because every website builder has edges.

The Small Design Change Becomes a Coding Task

This is the part Kleemt is really responding to.

A small visual request can become a coding task very quickly. The desktop version looks right, but mobile breaks. The spacing changes on tablet. The button wraps strangely. The image crop looks off. The section works in one template but not another. You fix one thing and accidentally change something else.

That is fine when the requirement deserves code.

But not every design improvement deserves a mini development cycle.

Sometimes the project just needs a better starting point. A section that already has the bones of the thing you are trying to create. A layout that already understands the pattern. A block that lets you get back to the page instead of opening a new rabbit hole.

That is why “without code” matters here.

It is not anti-code. It is anti-making-small-things-heavier-than-they-need-to-be.

The AI Snippet Loop

AI has made this even more tempting.

You can ask ChatGPT for a Squarespace code snippet and sometimes it works. Sometimes it almost works.

And “almost” is where the time goes.

You paste the snippet. The section looks right on desktop but breaks on mobile. You ask for a fix. It gives you new code. You paste again. Now the spacing is better, but the button moved. You ask again. Now something else changed.

By the time it finally works, the original request does not feel small anymore.

That does not mean AI is useless. It just means copy-paste code is not always the best interface for visual design work.

Kleemt is interesting because it moves the work closer to the place where the design actually lives. Instead of leaving Squarespace to generate a snippet, paste it back in, and troubleshoot the result, you can add a designed section and adjust it in context.

That is a cleaner workflow for this kind of problem.

What It Feels Like Kleemt Is For

Kleemt is best when the page already makes sense.

It is not there to rescue weak strategy. It is not there to magically make bad content persuasive. It is not there to replace the work of deciding what the page needs to say.

It is there for the moment after that.

The moment when you know what the section is supposed to do, but the native version feels too plain.

That could be a proof section, a logo strip, a map, a testimonial layout, a comparison section, a before-and-after block, or a more interesting visual break between parts of the page.

The value is not only that the section looks more polished.

The value is that you can keep moving.

That matters during a real build. Momentum is fragile. Every time a small section turns into a separate technical problem, the whole project gets heavier. Kleemt gives you another path: add the section, shape it, keep building.

What Makes Kleemt Different

The cleanest distinction is this:

Kleemt is more about adding ready-made sections and blocks.

SquareKicker is more about giving you deeper design control over existing Squarespace elements.

Spark is more about quick visual enhancements and one-click customizations.

There is overlap. These tools all live in the same general world: making Squarespace sites feel less default without writing everything from scratch.

But the buying question is different.

If you want to style and control the design system more deeply across the site, SquareKicker may be the better fit.

If you want quick effects, visual upgrades, and lighter customizations, Spark Plugin may be enough.

If you need a specific plugin, snippet, template, or component, Ghost Plugins may be the better place to look.

If you want a finished section or block that already feels designed, Kleemt is the one I would look at first.

That is the difference.

Kleemt Alternatives

There are a few ways to solve the “this looks too native” problem in Squarespace.

Use native Squarespace when the default section already works. This is still the cleanest answer when the design does not need anything more.

Use SquareKicker when you want broader no-code design control. It is a stronger fit when you want to push existing sections, spacing, styles, animations, and visual behavior across the site.

Use Spark Plugin when you want fast visual enhancements without getting too deep into custom design control.

Use Ghost Plugins when you need a specific plugin, snippet, template, or component for one particular issue.

Use custom CSS or custom code when the requirement is specific enough to justify building and maintaining it.

Use Kleemt when the page is close, but the section needs to feel more polished than the native option.

That last point is important. Kleemt does not need to replace all the other tools to be useful.

It just needs to solve its particular problem well.

Who Kleemt Is Best For

Kleemt makes the most sense for Squarespace designers, developers, and site owners who want better sections without turning every visual improvement into a technical task.

It is especially useful when a page needs:

• A stronger proof section

• A better testimonial layout

• A more polished logo strip

• A custom-feeling map

• A cleaner comparison area

• A before-and-after interaction

• A more interesting visual break

• A section that feels less like default Squarespace

The common thread is that the page does not need to be rebuilt.

The section needs to be elevated.

That is the Kleemt moment.

Who Kleemt Is Not For

Kleemt is not for every Squarespace design problem.

If the native section already works, use it.

If you need deep site-wide design control, I would look at SquareKicker.

If you want quick visual effects, Spark may be enough.

If you need one specific function, Ghost Plugins or another dedicated plugin may be better.

If the client needs something highly custom, code may still be the right answer.

That is not a weakness. It is just the category.

The useful thing about Kleemt is that it gives you a middle option for the projects that do not need custom development, but also do not feel finished with native Squarespace alone.

Final Verdict: Is Kleemt Worth It?

Kleemt is worth looking at if your Squarespace page already works, but one or two sections need to feel more polished, more custom, or more useful without becoming a coding task.

That is the simplest way to understand it.

Use native Squarespace when the default blocks are enough.

Use custom code when the requirement deserves custom code.

Use SquareKicker when you want deeper design control.

Use Spark when you want quick visual enhancements.

Use Kleemt when the section already makes sense, but needs to feel better.

The decision test is simple:

Does the page need a new strategy, a new structure, or one better design moment?

If it needs a new strategy, step back.

If it needs a new structure, redesign the section.

If the section makes sense but still feels too plain, Kleemt may be the right tool.

Sometimes the site does not need more code.

Sometimes it just needs a better design moment.

Kleemt is a no-code tool for Squarespace users who want more polished sections without building everything from scratch.

Instead of searching for a code snippet, hiring a developer, or trying to force a native Squarespace section into a layout it was not really designed for, Kleemt gives you ready-made sections you can add into a page and customize.

That makes it especially useful for designers and site owners who are already comfortable building in Squarespace, but occasionally run into the same problem:

The page works, but it needs one better section.

Not a whole new site.

Not a full custom build.

Just a better way to show the content.

What Problem Does Kleemt Solve?

A lot of Squarespace design problems are not really development problems.

They are block and section problems.

You do not always need custom code. You do not always need to redesign the whole page. You do not always need a developer to step in.

Sometimes you need a stronger testimonial layout. Or a better logo section. Or a more useful comparison block. Or a cleaner gallery. Or a more polished visual moment between two important parts of the page.

That is the gap Kleemt is trying to fill.

It is for the moment when native Squarespace is good enough to build the page, but not quite flexible enough to create the section you actually want.

Native Squarespace Is Often Enough

To be clear, not every Squarespace site needs Kleemt.

Squarespace already gives you a strong foundation. You can build pages with text, images, buttons, galleries, forms, products, lists, and layouts without touching code. For a lot of projects, that is enough.

A tool does not need to be added just because another tool exists.

If the native section works, looks good, and the client is happy with it, leave it alone.

The question is not whether Squarespace can build good pages.

It can.

The question is what happens when the page needs a block or section that feels more custom than the native options make easy.

Where Native Squarespace Starts to Feel Limited

The phrase I would listen for is:

“I just want this section to feel better.”

That sounds simple, but it can quickly become a development problem.

A client asks for a more interesting proof section, a better layout, a custom-feeling map, a more polished comparison area, or a block that feels more elevated than the default Squarespace version.

None of these requests sound huge.

But inside a Squarespace project, they often create a choice: settle for the native version, search for a code snippet, buy a separate plugin, ask a developer, use custom CSS, or spend too much time forcing the default section into something it was not really designed to be.

That is the native wall.

The design idea is not unreasonable. The site may not need custom development. But the block or section needs more than Squarespace gives you out of the box.

The Small Design Change Becomes a Coding Task

This is where the project starts getting heavier than it should.

The designer does not need to rebuild the whole site. They do not need to create a custom app. They do not need to turn a small visual upgrade into a technical project.

They just need a better way to make the section work.

That is why “without code” matters.

Not because code is bad.

Code is useful when the requirement is specific enough to justify it.

But if every polished section requires CSS, snippets, testing, and troubleshooting, the project starts to feel heavier than the request.

The design idea should not always become a coding task.

The AI Snippet Loop Is Part of the Problem

AI has made this more interesting.

You can ask ChatGPT or another AI tool for a Squarespace code snippet. Sometimes that works. Sometimes it almost works.

And “almost” is where the time goes.

You paste the snippet. The section looks right on desktop but breaks on mobile. The spacing is off. The button is in the wrong place. You ask for a fix. You paste again. Now something else changed.

Half an hour later, you are still adjusting margins for a design change that should have taken two minutes.

That does not mean AI is useless.

It means copy-paste code is not always the best interface for design work.

The interesting thing about Kleemt is that it points toward a different workflow. Instead of asking for a snippet somewhere else, pasting it into Squarespace, debugging it, and repeating the cycle, you can add and edit the section closer to the place where the design actually lives.

That is a very different proposition.

What It Is Like to Use Kleemt

Kleemt is best understood as a section and block library for Squarespace.

You add a section, choose from available Kleemt layouts, then customize the design. The value is not only that the sections look better than a default block. The value is that you can keep moving.

That matters during a real build.

A small design issue can interrupt the whole flow of a project. You stop designing, start searching, test a snippet, fix a bug, check mobile, adjust spacing, and suddenly a small visual request has taken over the session.

Kleemt gives you another path.

Add the section. Adjust it. Keep building.

That is the appeal.

What Makes Kleemt Different

The main difference is that Kleemt is not just about styling what already exists.

It is about adding ready-made sections and blocks that already feel designed.

That distinction matters.

If you want broad design control across a Squarespace site, SquareKicker may be a better fit.

If you want quick visual effects and one-click style upgrades, Spark Plugin may be enough.

If you need a very specific plugin, snippet, template, or component, Ghost Plugins may be the better place to look.

Kleemt is strongest when the page already makes sense, but one section needs to feel more finished.

That is its lane.

Kleemt Alternatives

There are a few different ways to make a Squarespace site feel less native.

SquareKicker is useful when you want deeper no-code design control across the site. It is more of a broad design-control tool for styling existing Squarespace elements, adjusting layouts, creating effects, and pushing the visual system further.

Spark Plugin is useful when you want quick visual enhancements, effects, and style upgrades. It is more about adding polish and customization without going deep into a custom build.

Kleemt is useful when you want a polished section or block that already feels designed, without turning the idea into a custom development task.

Custom CSS is useful when the requirement is specific enough to justify writing and maintaining code.

That means Kleemt does not replace every other option.

It solves a particular kind of problem.

The page is close.

The section is not.

Who Kleemt Is Best For

Kleemt makes the most sense for Squarespace designers, developers, and site owners who want to move faster without making every custom-feeling section from scratch.

It is especially useful when a page needs:

• A stronger proof section

• A better testimonial layout

• A more polished logo strip

• A custom-feeling map

• A comparison section

• A before-and-after interaction

• A more interesting visual break

• A section that feels less like default Squarespace

The site does not need to be rebuilt.

The section needs to be elevated.

That is the moment when Kleemt is worth looking at.

Who Kleemt Is Not For

Kleemt is not for every Squarespace design problem.

If the native Squarespace section already does the job, use the native section.

If the client needs deep site-wide design control, SquareKicker may be a better fit.

If the client needs quick style effects, Spark may be enough.

If the client needs one very specific function, Ghost Plugins, a dedicated plugin, or a code snippet may be better.

If the client needs a fully custom interactive experience, custom development may still be the right path.

The point is not that Kleemt replaces every other option.

The point is that many Squarespace projects do not need every other option.

They need one better block.

Or one better section.

Final Verdict: Is Kleemt Worth It?

Kleemt is worth looking at if your Squarespace page already works, but one or two sections need to feel more polished, more custom, or more useful without becoming a coding task.

That is the best way to understand it.

It is not a replacement for Squarespace. It is not a replacement for thoughtful design. It is not a replacement for custom development when custom development is truly needed.

It is a middle path.

The simple decision test is this:

Does the page need a new strategy, a new structure, or one better design moment?

If the page needs a new strategy, step back and rethink the page.

If the page needs a new structure, redesign the section.

If the section already makes sense but feels too plain, Kleemt may be the right tool.

Sometimes the site does not need more code.

Sometimes it just needs a better design moment.

How to Run and Rotate Sponsor Ads on Squarespace Without AdSense

The question usually comes up after the first sponsor ad is already working.

Your client has a leaderboard space. Or an MPU-style ad space. Or a sponsor banner in a sidebar, directory, article, or resource page.

One banner is easy enough to place in Squarespace.

The problem starts when the client wants more than one ad to run in the same space. They do not want AdSense. They do not want to join an ad network. They want to run their own sponsor ads, rotate banners, track performance, and manage the placements they already sell.

That is a different problem.

At that point, the question is no longer, “Can Squarespace display an ad?”

It can.

The better question is, “Can we manage sponsor ads on Squarespace without turning every campaign into a manual website edit?”

This is not about AdSense

There are two very different kinds of website advertising.

The first is ad network advertising. That is the world of AdSense, programmatic ads, auto ads, and third-party networks that fill ad space for you.

The second is direct sponsor advertising. That is when your client sells ad space directly to a sponsor, advertiser, vendor, partner, or local business.

This article is about the second one.

A sponsor buys a leaderboard. A vendor buys an MPU placement. A local business buys a rotating banner. A partner pays to appear in a resource section. The site owner already has the relationship, the placement, and the audience.

They are not looking for an ad network to fill empty space.

They are looking for a way to run the ads they already sold.

When one sponsor banner is easy enough

If the client has one sponsor, one banner, one link, and one page, a simple Squarespace setup may be enough.

You can add an image block, button, code block, or embed block. You can link the image to the sponsor’s website. You can add a small “Sponsored by” label. You can remove or replace the ad when the campaign ends.

That works when the placement is simple and easy to remember.

A manual setup is usually fine when:

• There is only one sponsor

• The ad appears in one place

• The campaign does not need to rotate

• No one needs performance reporting

• The start and end date are easy to track

• The sponsor relationship is informal

• The client is not selling multiple placements

There is no need to add a system when one block solves the problem.

When one ad space needs to rotate multiple ads

The setup changes when the client wants more than one sponsor ad in the same space.

Maybe they sell a leaderboard at the top of the page, but two sponsors want to share that placement. Maybe they have an MPU-style ad space in a sidebar and want a different banner to appear when the page refreshes. Maybe they sell several sponsor placements across a directory, resource hub, or niche publication.

Now the ad space is no longer just a static image.

It is inventory.

The client needs to know which ads are active, where they run, when they start, when they stop, and whether the sponsor got what they paid for.

That is where a normal Squarespace image block starts to feel limited.

The block can show the ad.

It does not manage the campaign.

The DIY code block option

You can rotate ads in Squarespace with custom code.

A developer can create a simple script that cycles through a list of images and links. The ad might change every few seconds, or a different banner might load when the page refreshes.

For a very small setup, that may be enough.

The DIY version might include:

• A Squarespace code block or embed block

• A list of sponsor image URLs

• A list of sponsor links

• A script that randomly displays one ad

• Manual updates when sponsors change

That can work when the client is comfortable with code and the campaign does not need much management.

But the DIY version has limits.

Someone still has to update the code when an ad changes. Someone has to make sure the right sponsor is active. Someone has to remember start and end dates. Someone has to check the links. Someone has to handle tracking if the sponsor asks how the ad performed.

The rotation is only one part of the problem.

The management is the part that keeps coming back.

Where the manual setup starts to break

The first sponsor is easy.

The second sponsor is where the system starts to show.

A client may start with one leaderboard or one MPU placement. Then another advertiser wants in. Then someone asks to reserve a specific month. Then a sponsor sends new creative. Then someone wants click stats. Then an old banner stays live too long because nobody remembered to remove it.

None of this is dramatic. It is just a pile of small obligations.

Did the sponsor pay?

Which banner is approved?

Which ad space did they buy?

Is the campaign live?

Should it rotate with another ad?

When does it end?

Did the sponsor ask for reporting?

Can they renew?

That is why direct sponsor ads become frustrating inside a manual website setup. The work is not hard enough to feel like a big project, but it is important enough that forgetting something creates a real problem.

What sponsor ad management actually requires

A sponsor ad has a lifecycle.

It has to be sold, submitted, approved, scheduled, displayed, rotated, tracked, ended, and sometimes reported on.

The visible ad may only be a banner. But once someone pays for that banner, the placement carries a promise.

The sponsor may need to know:

• Where the ad will appear

• What size or format to send

• When the campaign starts

• When the campaign ends

• Whether the placement rotates with other sponsors

• Whether the placement is exclusive

• How many clicks or impressions it received

• Whether they can renew

• What other placements are available

That is the difference between putting an ad on a page and running a sponsor ad program.

One is a website edit.

The other is a small ad operation.

Where Ad Manager fits

Ad Manager is useful when a Squarespace site needs to run direct sponsor ads without joining an ad network.

It is for the client who already sells, or wants to sell, their own placements. Leaderboards, MPU-style placements, sidebar banners, directory ads, sponsor cards, resource page promotions, newsletter site placements, and other direct ads can all create the same kind of management problem.

If the client only needs one static ad, they may not need Ad Manager.

But if they need to rotate multiple banners in the same ad space, schedule campaigns, track performance, and manage sponsor placements without hand-editing the site every time, Ad Manager becomes much more relevant.

The point is not that every Squarespace site needs ad management.

Most do not.

The point is that a site selling private sponsor ads eventually needs something better than scattered emails, image blocks, spreadsheets, calendar reminders, and memory.

Manual Squarespace setup vs. Ad Manager

Use a manual Squarespace setup when the ad is simple.

Use Ad Manager when the ad space has become something the client sells and manages.

Use a DIY Squarespace setup when…	Use Ad Manager when…
You only need one static sponsor banner.	You need multiple banners rotating in the same ad space.
You are comfortable editing code or image blocks manually.	Your client wants a cleaner way to manage sponsor ads.
No one needs performance tracking.	Sponsors want clicks, impressions, or campaign visibility.
Campaign dates are easy to remember.	You need scheduling, start dates, end dates, or campaign management.
The site owner is not selling ad inventory regularly.	The client sells leaderboard, MPU, sidebar, directory, or sponsored placements.
The ad is a one-off placement.	The ad space has become part of the business.

The key question is simple:

Is this just one sponsor banner, or is this an ad space the client sells?

One sponsor banner can stay simple.

A sellable ad space needs a system.

How Squarespace designers can use this with clients

For Squarespace designers, this is a useful distinction.

A client may not ask for “ad serving.” They may not know that phrase. They may simply say:

“Can we have two banners rotate in this spot?”

“Can sponsors see how many clicks they got?”

“Can businesses pay to be featured here?”

“Can we run different ads in the same space?”

Those are not just design requests.

They are ad management requests.

The client may already be selling attention without having a clean way to manage what they sold. That creates an opportunity to help them think through the setup before it becomes messy.

If the client needs one sponsor image, keep it simple.

If the client is selling leaderboard space, MPU space, directory placements, sidebar ads, or rotating sponsor banners, it may be time to treat the ad space like inventory.

The simple decision test

Ask this:

Does the client need to display one ad, or manage multiple sponsor ads?

If they need to display one ad, a normal Squarespace block may be enough.

If they need to rotate, schedule, track, and manage sponsor placements, a tool like Ad Manager is the cleaner path.

This is especially true when the client wants to run their own ads without AdSense or an ad network.

Because the problem is not whether Squarespace can show a banner.

It can.

The problem is whether the client has a reliable way to manage the sponsor ads they are already selling.

When the answer is yes, the site has moved beyond a static ad placement.

It has become sponsor inventory.