Who needs this
Any shop selling tickets through an event-management plugin who wants reviews for the event itself, not just for “the ticket purchase.”
- Workshops, classes, courses. The customer’s review is about the experience: the instructor, the room, what they learned. Asking on day-of-purchase is meaningless. Asking the day after the event is exactly right.
- Music, sport, club events. Reviews need to land while the event is fresh in the attendee’s memory. A week later they’ve forgotten the details.
- Multi-day or recurring events. A customer who attends 12 sessions doesn’t want 12 review requests. The dedup window stops that.
- Shops that already use Trustie Pro for product reviews and want the same treatment for the event side of the business, without bolting on a separate platform.
What goes wrong without it
Most shops in this position fall back to one of three approaches:
Manual emails. “I’ll send a thank-you email after each event.” Works for the first few; collapses by event five. Reviews then get collected sporadically based on whoever the shop owner remembers to email.
Treating the ticket purchase as a product review trigger. WooCommerce sees a ticket purchase as a normal completed order. Standard review-request automation fires after purchase, which means the email lands days before the event happens. The customer can’t review something they haven’t experienced yet, so they ignore the email, and the review never happens.
Using a generic survey tool. SurveyMonkey or Typeform can collect feedback, but the responses live in that tool’s silo. They don’t show on your shop’s reviews page, don’t feed Google rich snippets, don’t earn star ratings on your event pages. The social proof is invisible to future ticket buyers.
How Trustie Pro handles it
Trustie Pro hooks into your event plugin’s lifecycle, not your shop’s order lifecycle, so the timer starts when the event ends.
Two event plugins supported
| Your event plugin | What Trustie reads | Where the integration lives | |—|—|—| | Eventin (Themewinter) | The etn_attendees table, with WooCommerce orders as automatic fallback | Trustie > Review Requests > Events tab | | The Events Calendar + Event Tickets (StellarWP) | The Event Tickets attendee repository (covers both RSVPs and Tickets Commerce) | Trustie > Review Requests > Events tab |
Both integrations are configured separately. If you run both event plugins, you’ll see two sets of settings. If you only run one, only that one shows. There’s nothing to install — both integrations are part of Trustie Pro.
Timing
The email is scheduled N days after the event’s end date, where N is configurable per event plugin (default: 1 day). So a workshop that ends Saturday gets review requests sent Sunday.
This is not based on when the ticket was purchased. A customer who books six months in advance and one who buys at the door both get asked at the same time, the day after the event.
Check-in awareness
By default, Trustie Pro only asks attendees who actually checked in. No-shows don’t get review requests, because they have nothing to review.
You can flip this behaviour off if your event plugin doesn’t track check-ins, or if you’d rather ask everyone who held a ticket. The setting is one toggle per integration.
Three-step sequence with stop-on-first-review
Each integration runs an independent three-email sequence:
- Initial request — sent 1 day after the event ends (configurable)
- First follow-up — sent 7 days after the initial (off by default)
- Second follow-up — sent 14 days after the initial (off by default)
Each step is independently toggleable. If the attendee leaves a review at any point in the sequence, the remaining steps cancel automatically. Same trustie_review_submitted hook the product review system uses; same shop-wide unsubscribe list.
Dedup window
If the same email address is queued for multiple events in the same week, the dedup window (default: 7 days) prevents the second request from going out. Useful for shops where the same customer attends multiple sessions.
Branded template with event card
Event review emails use your Tracksies Brand Hub: your logo, your primary brand colour, your fonts. The email body shows an event card (featured image, event name, event date, organiser/club name) above the review button. Editable in the Tracksies Designer.
Merge tags
Available in subject, heading, body, and button text:
{customer_name}— attendee first name (or “there” if not captured){event_name}— event title{event_date}— event start date, formatted to your WordPress site date format{club_name}— for The Events Calendar, the organiser name; for Eventin, the Dokan vendor store name (if Dokan is active) or the event author’s display nameTracksies/{site_name}— your WordPress site name
Where reviews land
Reviews collected from event attendees flow into the same Trustie review system as product reviews. They appear on:
- Your auto-generated reviews page
- The floating reviews widget
- Anywhere your
shortcode is placed - Google rich snippets (if you have JSON-LD enabled)
- Owner response, moderation queue, helpful voting, and every other review feature
The event becomes another review source alongside Google, your products, and your shop reviews. One inbox, one moderation flow.
Are you considering Eventbrite reviews, SurveyMonkey, or your event plugin’s built-in feedback?
Eventbrite reviews live on Eventbrite’s platform. If your tickets are sold through Eventbrite, customers can leave reviews there, but those reviews show up on Eventbrite’s listing page, not your shop’s website. Useful if your discoverability runs through Eventbrite; less useful if your sales come from your own site.
SurveyMonkey, Typeform, Google Forms are general survey tools. They handle the data collection well, but the responses don’t become star ratings on your event pages or your shop’s reviews page. They’re feedback, not social proof.
The Events Calendar’s built-in feedback (if available in your tier) is form-based and shows up in TEC’s admin. It doesn’t connect to a public reviews page or feed star ratings into your other shop pages.
Trustie Pro’s event review requests function this way: the reviews are stored in your shop’s reviews system, displayed alongside your other reviews, branded as part of your shop, and treated as social proof for future ticket buyers. The trade-off: they live on your site only, not on a third-party listing.
The fit: if your event sales come from people who land on your shop, this is the path. If they come from third-party event listings, you may want both — Trustie Pro for the on-site social proof, and your event listing’s review system for discoverability there.
Frequently asked
Do I need both event plugins, or just one? Just one. Each integration is independent. If you only run Eventin, only the Eventin tab appears. Same for The Events Calendar + Event Tickets.
What if I run both event plugins on the same site? Both integrations run in parallel with separate settings. An attendee in both systems for the same week is protected by the dedup window — they won’t get two emails for the same event week.
What happens if an attendee already left a review for a different event? The dedup window prevents same-email follow-ups within its configured period. Beyond that window, they can be asked again for a new event. The shop-wide unsubscribe list always wins — once unsubscribed, they’re never asked again.
Does this work for free RSVPs, not just paid tickets? Yes. The Events Calendar integration covers both Tickets Commerce (paid) and RSVPs (free). Eventin covers any attendee in its system regardless of payment status.
Can I preview the email before turning it on? Yes — the same Designer preview tool that handles product review emails handles event review emails. Live preview updates as you edit, sample data filled in.
What about cancelled events or refunded tickets? If an event is removed from the queue before the cron runs, the request is skipped. Refund handling on the ticket itself is the event plugin’s responsibility — Trustie reads from the attendee tables those plugins maintain, so a removed attendee doesn’t get an email.
Does this fire if I don’t have WooCommerce? The Events Calendar + Event Tickets integration works without WooCommerce. The Eventin integration uses the Eventin attendee table directly (no WooCommerce required), with WooCommerce orders as a fallback only if the Eventin table isn’t populated.