Development Log Update: April 30th, 2026
dev log
Remove Sweepstakes 3-Day Validation
Release Date: May 5, 2026
Why Are We Changing This?
Until now, sweepstakes campaigns required the end date to be at least 3 days after the online sales end date. If a user tried to set them closer together, they hit a modal blocking the save. This rule was originally in place to give mail-in entrants enough time to physically mail in their free entries before the drawing.
Two things have shifted. First, the legal/regulatory rationale for enforcing that 3-day buffer is no longer needed. Second, customers running short-turnaround sweepstakes (like same-day live event drawings, flash promos, quick-turn campaigns) have been blocked from setting up the campaign timing they actually want. Removing this constraint opens up a lot more flexibility for how customers can run sweepstakes.
What's Changing | The 3-day rule is gone
Users can now set the sweepstakes end date on the same day as the online sales end date, or any number of days after, without hitting an error or blocking modal. The end date field is still required and all other date validations still work as expected — only the 3-day minimum gap rule has been removed. This applies to both the front-end and back-end, and across all campaign setup versions.
Mail-in entries inside 24 hours are auto-received
When a sweepstakes is running tight on time, there isn't always enough runway for someone to request a free entry, fill out the form, mail it in, and have an organizer manually mark it as received before the drawing. To make short-turnaround sweepstakes work, mail-in entries that move into "FormFilled" status within 24 hours of the drawing end date are now automatically marked as "Received" — meaning they'll show up in the View Mail-in Entries screen and will be assigned entries during the drawing without needing organizer intervention.
A few notes on how this works:
- The auto-received logic only kicks in after the entrant completes the form. Entries still sitting in "Requested" status (just an email submitted, no form completed) will not be auto-received.
- Mail-in entries requested more than 24 hours before the drawing still follow the existing flow — they stay in "Requested" / "FormFilled" until an organizer or admin manually confirms them as received.
Allow Users to Enable Fundraising Components After Publish
Release Date: May 6, 2026
Why Are We Changing This?
Live Event customers may want to publish their campaign and start selling tickets as early as possible — often well before they've nailed down every fundraising activity they plan to run during the event. Until now, once a campaign was published, the fundraising components were essentially locked in: you couldn't add an auction, raffle, or other activity after going live, and you couldn't remove one either, even if nobody had bought anything related to it yet.
That created a real bottleneck for event organizers who wanted to get their ticket sales open while still finalizing the rest of the program. This change gives them the flexibility to keep building out (or scaling back) their campaign after publish, as long as no transactions have happened that would be affected by the change.
What's Changing | Fundraising activities can now be added after publish
Users can enable additional fundraising components on campaigns that are already in Started status. When they save the Fundraising Component Selection screen after enabling a new component, there are no longer errors saying the new components haven't been set up — the user is free to come back and configure them when they're ready. The Campaign page handles components that have been added but not yet configured, so nothing breaks on the public-facing side while setup is still in progress.
Can I remove fundraising components after publish?
If no transactions have been made that include items tied to a specific fundraising activity, users can disable that component from their campaign page after publishing. This gives organizers room to swap or simplify their program post-launch.
If transactions have already happened for a component (donations, ticket purchases, DEBs, etc.), the component is locked. Hovering on the disabled toggle shows a popover explaining why:
"This component can't be disabled because a [donation] has already been made to your [campaign]"
All other fields tied to the activity remain editable as long as no related transactions exist.
Scope of this release
This change applies to the two newer campaign setup versions (2024 and 2025 releases). Customers on the oldest setup won't see this functionality in this release — their setup is structured differently enough that it would need a separate effort to bring across. If you need to enable the new campaign setup version, you can do so by contacting us at partners@rallyup.com.
For more information, please contact us partners@rallyup.com.
