Low ticket sales call for a diagnosis before a spend decision. Decide in advance what counts as
a stall, check the cheapest explanations first, and match the response to the cause and to the
time you have left.

A quiet week is not a stall, and by the time a stall is obvious on a cumulative chart you have
lost the weeks when you could have done something about it. Most teams argue about the chart
for a week and then buy more paid media, whatever broke.

## What counts as stalled, and how is that different from noise?

Weekly registration counts are noisy. A holiday, one large delegation, or a newsletter sent on
Thursday instead of Tuesday can move a week by a fifth without telling you anything about
demand. A stall is a deviation large enough, or sustained long enough, to be unlikely as
ordinary variation. Saying that with rigor takes three things: an expected weekly number, a
measure of the gap, and a band of normal variation built from your own history.

**Expected registrations in week W = Share of the final total that arrived in week W in prior cycles × Current forecast total**

**Cumulative expected to date = Sum of expected weekly registrations from cycle open through week W**

**Pace index = Cumulative actual registrations to date ÷ Cumulative expected to date**

**Weekly deviation = (Actual week W − Expected week W) ÷ Expected week W**

The arrival shares come from your own last two or three cycles, not from a published curve.
Registration has moved late. The Maritz Registration Insights Report analysed more than 360,000
registration records across 30 trade shows and found that in 2023, 45% of registrants signed up
in the final 4 weeks before the event and 9% on site
([PCMA Convene](https://www.pcma.org/rethinking-early-bird-pricing-other-event-registration-strategies/)).
A curve built on older assumptions reads every early week as a disaster, so recompute your
shares each cycle.

The pace index is a ratio against a forecast. If the forecast is wrong, the index is wrong in
the same direction, which is why the
[registration forecast](https://eventiq.io/md/blog/conference-registration-forecasting) should be a range and should
be rebuilt every week.

## Where should the threshold sit?

Set it from the spread of your own weekly deviations, and write it down before the cycle opens.

**Noise band = Mean weekly deviation across prior cycles ± (2 × Standard deviation of weekly deviation)**
| Status | Condition | What happens |
| --- | --- | --- |
| Green | Deviation inside the noise band and pace index at 0.97 or above | No action. Note it and move on |
| Amber | One week below the band, or pace index below 0.95 two weeks running | Run the diagnostic below within 48 hours |
| Red | Two consecutive weeks below the band, or pace index below 0.90 | Diagnostic plus a decision meeting with budget authority present |
Two details decide whether this works. The threshold has to be agreed before the cycle opens,
or it becomes a negotiation about whether the number is bad. And amber has to trigger a
diagnostic, not a spend decision. The common failure is treating amber as permission to buy
media before anyone has checked that the tracking is intact.

If you have no history to compute a band from, do not borrow one. Use a placeholder this cycle
and record the actual deviations. Kyle Jordan, director of meetings at INFORMS, told
[Skift Meetings](https://meetings.skift.com/2026/06/22/late-registrations-are-not-the-only-thing-stressing-planners-out/):
"Our old registration pacing models are not as reliable as they used to be." That is an
argument for rebuilding your band from recent cycles, not for skipping it.

## Which cause is it? A diagnostic that takes an hour

Run the checks in cost order. The cheapest are also the most likely to be the answer. Work top
to bottom and stop when a check fails.
| Check | What to look at |
| --- | --- |
| 1. Tracking break | Do platform-reported registrations match your dashboard for the same week? Did anyone change the form, URL, or redirect in the last 14 days? Are source and campaign parameters still populating on new records? Did a consent banner or tag manager change deploy recently? |
| 2. Channel failure | Email: sends attempted, delivered, and opened, by stream. Paid: impressions, spend, and landing-page sessions, by campaign, in the ad platform itself. Did any campaign exhaust its budget, get disapproved, or lose an audience? Did organic sessions to the registration page drop? |
| 3. Pricing deadline effect | Did a price tier close in the prior week? Compare with the equivalent post-deadline week in prior cycles |
| 4. Competing date | Any adjacent industry event, holiday, or reporting deadline in the window? Are the missing registrations concentrated in one segment or region? |
| 5. List fatigue | Send frequency and unsubscribe rate against prior cycles. Unique reach: what share of the target list has been touched already? Open rate trend across the last six sends to the same segment |
The order matters because the first item is the most common and the least visible. A form that
still works but stopped writing a source parameter looks exactly like a paid-channel collapse,
and the usual reaction, cutting the channel that seems to have died, makes it worse.

## What is the response for each cause?

Each response has a lead time, and past a point some stop working. Write the lead times into
the playbook.

**Tracking break.** Fix the tracking, then reconstruct the missing weeks from platform-side
counts before re-reading the trend. Do not restate the forecast on broken data. Lead time:
days, and no attendance is lost if you catch it.

**Channel failure.** Restore the channel first, then decide about budget. If the channel is
underperforming and not broken, reallocate before you add. Lead time: one to two weeks for paid
to re-accumulate, longer for organic.

**Pricing deadline effect.** Usually not a problem. A post-deadline trough followed by recovery
is the expected shape. The useful question is whether the spike before the deadline pulled
volume forward or created it, which is the subject of the
[early bird registration](https://eventiq.io/md/blog/early-bird-pricing) page. Do not spend against a trough your own
pricing created.

**Competing date.** You cannot move the competitor. You can change the offer for the affected
segment: a virtual option, a one-day rate, a group arrangement. Lead time: three weeks minimum
for a new offer to produce registrations.

**List fatigue.** More sends make it worse. The response is new reach, through partner lists,
chapter channels, speaker networks, and sponsor audiences, plus segment-specific content in
place of another general send. Lead time: two to four weeks, which is why fatigue found at three
weeks out is mostly a lesson for next cycle.

## Why does a tracking break look like a slowdown?

Because both present as a number that fell for no visible reason. The difference is shape. A
tracking break shows a clean step down starting on a specific day, often at a deploy. Genuine
demand softness shows a slope. Check step against slope first, then reconcile against the
registration platform's own counts.

Source data is thinner than people assume, and a form or tag change can remove it silently.
That is the case for keeping the source and the original identifier on every record, so a
suspicious number can be traced to the rows behind it and not debated.

## What should you not do in week four?

Do not discount reactively. A mid-cycle price cut trains your audience to wait next year, and
it lowers yield on registrations that were arriving anyway in the final two weeks.

Do not restate the forecast on one week. Restate when the rule fires, and record both figures
so the forecast can be judged afterward.

Do not fund a new channel in the last three weeks. A channel with no history at your
organization needs time to learn and time to be judged, and a channel you cannot judge is not a
decision. Spend the money deepening one that already converts.

## Example: six weeks on one event

Take an annual meeting with a forecast total of 1,800 registrations. All figures are
hypothetical. The organization's own history gives a mean weekly deviation near zero with a
standard deviation of 12%, so the noise band runs from about −24% to +24%.
| Weeks out | Expected this week | Actual this week | Cumulative expected | Cumulative actual | Pace index | Weekly deviation | Rule |
| --- | --- | --- | --- | --- | --- | --- | --- |
| 8 | 72 | 75 | 783 | 790 | 1.01 | +4% | Green |
| 7 | 81 | 78 | 864 | 868 | 1.00 | −4% | Green |
| 6 | 90 | 84 | 954 | 952 | 1.00 | −7% | Green |
| 5 | 108 | 71 | 1,062 | 1,023 | 0.96 | −34% | Amber |
| 4 | 126 | 79 | 1,188 | 1,102 | 0.93 | −37% | Red |
| 3 | 162 | 171 | 1,350 | 1,273 | 0.94 | +6% | Red (pace) |
Week 5 breaks the band once: amber, diagnostic within 48 hours. Week 4 breaks it again, the second consecutive week below the band: red, decision meeting.

The diagnostic here finds two things. Delivered email volume to the member stream dropped by
more than half after a sending-domain issue, which is check 2. And the missing registrations
are concentrated in one region, where a competing industry meeting fell in the same fortnight,
which is check 4. Nothing is wrong with the paid channel, which was the team's first instinct.

Do the arithmetic on the deficit before the meeting. At week 4 the event is 86 registrations
behind expected. If the remaining weeks arrive at the same relative rate, a pace index of 0.93
against a forecast of 1,800 implies roughly 1,674 registrations, about 126 short. At a net
contribution of $520 per registration that is around $65,520, and that is the number that
decides how much response is proportionate. Use your own contribution figure, and size the
response against the money at risk, not against the shape of the chart.

The response that follows: fix deliverability and resend to the affected stream from a
corrected domain, and make a one-day rate available to the affected region. Both have lead
times short enough to matter with four weeks left. Adding paid budget would have addressed
neither.

## What to do this quarter

- Compute your weekly arrival shares from the last two or three cycles, and build expected
  weekly registrations for the current cycle.
- Calculate your noise band from your own deviations, and write the green, amber, and red rule
  into the cycle plan before registration opens.
- Put the diagnostic order in the marketing runbook, with tracking as check one and a named
  owner per check.
- Agree the lead time for each response, so nobody proposes a three-week play with two weeks
  left.
- Add a standing weekly item: pace index, weekly deviation, rule status. Three numbers, not a
  chart review.

## Common questions

### How many weeks of decline before we act?

One week outside your noise band triggers a diagnostic. Two consecutive weeks, or a pace index
below 0.90, triggers a decision. Separate them, because diagnosing costs an hour and spending
costs money.

### Can we use an industry pacing curve instead of our own history?

For orientation, yes. For a threshold, no. Published timing figures describe the industry, not
your audience, and a threshold built on someone else's curve fires at the wrong times. Build it
from your own cycles and rebuild it each year.

### What if we have no prior cycles at all?

Run the first cycle with a placeholder band, record every week, and treat year one's output as
the instrument, not the answer. Track leading indicators you can measure from week one: page
sessions, email click-through, and the start-to-complete rate on the form.

### Does a stall mean attendance will drop, or just registrations?

Different questions. Registrations set the ceiling, and the
[attendance rate](https://eventiq.io/md/blog/event-attendance-rate) sets the outcome. A shortfall in a free segment
translates differently from one in a paid segment, because people who paid are more likely to
come.

## Where EventIQ fits

EventIQ replaces nothing. It connects on top of the platforms you already run: event platforms
(Cvent, Zoom, Swapcard), CRM (Salesforce, HubSpot, GoHighLevel), and marketing (Google Ads, Meta
Ads, LinkedIn Ads, Mailchimp, Google Analytics). Platforms with an API outside that list are
connected on request.

This page is close to what the product does. The attendance forecast fits a registration curve
to the event's own sign-up pace, once there are about two weeks of registration data, and it is
shown as a range. A check on registration pace flags a slowdown against that expectation. The
check runs when you ask for it, so it belongs in the weekly review, not in place of it.

Two limits. EventIQ does not recommend a response or a budget shift, so the choice among the
five causes stays with your team. And the paid media figure it holds is the spend your team
entered by channel, not spend read from the ad platforms, so check 2 is done in the ad platform
itself. Records keep the identifier they arrived with, which is what makes check 1 workable: a
suspicious count can be traced to the rows behind it.

[Book a demo](https://eventiq.io/#early-access) to see a registration curve, its forecast range, and a pace
check on a sample event, in a 20-minute demo.

---

HTML version: https://eventiq.io/blog/low-ticket-sales