Reach and Revenue

The first paid marketing product. Pick one of your events, choose a template, choose which states to reach, and pay — Rameelo emails your event to members in those states. The price is worked out from the real size of the list you are buying, so a small local list costs a small local price, and every figure is calculated on our side rather than quoted by the page. Because the send is recorded as a normal campaign against your event, the opens and clicks land in the campaign report you already use. Two things it deliberately will not do: it never hands over an address list — you are buying reach, not a database — and when the list is small it says "a focused local list" instead of naming a number, so a modest audience is never undersold to you.

The second paid product, and a different kind of thing: Rameelo runs the ads for you. Choose a package and a daily pace, add video or image creative if you need it made, and the flight length is worked out for you — with a warning if the campaign would still be running after your doors open. The purchase screen shows projected impressions and clicks from benchmarks measured on Rameelo’s own ad account, and it is honest about the limit of that: impressions and clicks are what the money buys, while tickets are shown as a band and never as a promise, because garba conversion tracks how close you are to the event far more than how much you spend. Nothing is delivered at checkout — a purchase creates a work order our team picks up, and you can follow it from scheduled to live to complete.

Keep your sponsors in one place and put their logos where you promised they would appear. Each sponsor has a name, a logo, an amount and a tier — bronze, gold, platinum or presenting — and is either attached to your whole organization or to hand-picked events. The tier guide you sell from is the same file the event page, the ticket badge and the home-page sponsor wall read, so what a sponsor is promised cannot drift from what they get. The amount you recorded is private bookkeeping and never reaches an attendee; only branding is ever shown publicly. One switch, Hide, controls whether a sponsor appears anywhere — ending a sponsorship is a deliberate act, never something guessed from your calendar. Events without sponsors look exactly as they did before.

Write a short post and it appears in the feed of everyone holding a ticket to that event, plus members in the event’s state. No email is sent, which is exactly the point: you can post a set-time change, a parking note or a thank-you without spending an email or asking anyone’s permission. Multi-night pass holders are included on every night their pass covers. You can see how many people an announcement reached before you post it.

What’s New moved out of the main navigation into its proper place, and the organizer dashboard now uses the full width of the screen instead of sitting in a narrow column. Small changes, but the dashboard is the page most organizers keep open all night.

Signing in now lands you in a real stream instead of a dashboard: who else is going to events near you, announcements from the organizers you bought from, a countdown as your event gets close, new events published in your state, and your own giveaway entries. Everything in it is real activity — there is no filler. You can react to a post, one reaction per person, and the person who posted it hears about it once and never again for the same post. Privacy is built into how the feed is assembled rather than bolted on: only first names appear, guest checkouts never show up, the city shown is the event’s and not yours, and a single switch on your profile removes you from other people’s feeds entirely.

Rameelo now sells merchandise. A full storefront with product pages, sizes, a cart and its own checkout, plus real inventory so nothing oversells, destination-based tax, and shipping options that are configured rather than guessed. Bulk pricing counts across sizes — two smalls, two mediums and two larges is six shirts and earns the six-plus tier, which is the whole point when a dance group orders together. Completely separate from ticketing: a merch order never touches your tickets, and its receipts and order numbers are their own.

The announcement that the shop exists, built from the live catalog at the moment it is sent — real products, real prices, real sold-out state — so it can never quote a price checkout will not honour. Every product links to its own page rather than the storefront, because the click has to land on the size picker. If the shop is off or nothing is in stock, the send refuses rather than mailing an empty catalog.

College garba and raas teams get their own home on Rameelo: a claim link that turns into a team portal, a public team page with a donor showcase, and the ability to manage their own roster. Built for the campus teams who are a huge part of this community but have never had anywhere to point people.

A proper unsubscribe system. Members can manage what they hear about from their own profile, unsubscribes are recorded in one ledger that every marketing send checks, and the admin team can see and manage the whole suppression list in one place. Transactional email — receipts, refunds, ticket and order mail — deliberately keeps sending, because it is information about something you already bought.

Sending to a large list used to happen inside a single web request, which meant the send could be cut off partway through and the campaign would sit there reporting zero delivered. Delivery is now a queue worked through in the background, so a send survives being interrupted and picks up where it stopped. Every recipient is attempted on their own — one bad address costs that address and never the rest of the list — and the progress figures update while the send is still running instead of only at the end.

A companion to the above, for sends that went out before the queue existed or hiccuped before everyone was even queued. It works out the campaign’s original audience again and mails only the people who have no record of being attempted and no record of already receiving it, so nobody is emailed twice. It refuses rather than guesses in the two cases where it could do harm — a campaign belonging to an organizer, and a campaign with no per-recipient record at all, where retrying would mail the whole list a second time.

The most serious bug in this release, and worth stating plainly. Recipient lists were being silently capped at 1,000 people. An audience of 1,552 became 1,000: the screen said 1,000, the send went to 1,000, and the missing 552 appeared nowhere at all — not even as failures. Nothing looked broken, which is precisely what made it dangerous. Audiences are now counted and queued without ever passing through the layer that was truncating them, and the count you see is the count that gets mailed.