Just the ticket
Event tickets in Apple Wallet and Google Wallet: seat, door, and start time on the phone — updated when plans change.
Why your tickets belongs in Wallet
PDF tickets get lost in the inbox, and screenshots don’t update. When the start time moves, the news only reaches whoever opens the email.
At the door in one tap
The ticket is in Wallet, ready to show without searching the inbox.
One change, every ticket
Move the start time once, and it updates on every ticket issued.
Right on time
Tickets can surface on the lock screen near the venue and close to the start.
How event teams use Wallet
Each one is a model scenario — a typical setup, not a client case study:
Ticket after purchase
The purchase event starts a journey that issues a personal ticket with seat and row from the order.
Time, venue, or door change
Edit the shared field once — it updates on every issued ticket, with Google's update alert close to the start.
Doors-open reminder
The venue location on the pass plus a push before doors open helps people find the right entrance.
General admission pass
One shared pass for a free or open event — allow multiple holders so one link works for everyone.
After-show offer
A segment of attendees, and a journey issues a coupon for the next event or merch.
Your scenario
A different flow in mind? Map it with our team on a demo — the setup is the same account either way.
One scenario, step by step
Here’s “Ticket after purchase” from both sides: what the fan sees and what your team sets up. A free or general admission event skips all of this — one shared ticket from the builder.
-
A fan buys a ticket
An Event Ticket pass campaign: event, date, and venue as shared fields; name, seat, and row as personal fields. The purchase event starts a journey.
Wallet Pass Campaigns ↗ -
They get the confirmation email with an Add to Wallet button
Issue Wallet Pass maps Seat and Row from the order; Send Email adds the personal link.
Issue Wallet Pass ↗ -
They save the ticket
Nothing to set up here: the pass registers for updates on its own, and the holder shows up in the customer profile.
Apple Wallet ↗ · Google Wallet ↗ -
The start time moves — every ticket follows
Edit the shared date field once: Pushwoosh shows how many tickets it affects and pushes the change to all of them.
Update design and push changes ↗
Safe choice
ISO 27001:2022
Pushwoosh meets industry standards for online security and is certified by ISO 27001:2022.
Ensuring GDPR compliance
We maintain the highest standards of compliance with data protection regulations.
Adhering to OWASP principles
Our platform embraces the Security by Design approach to prevent potential threats.
HIPAA
Pushwoosh is HIPAA compliant, ensuring the confidentiality, integrity and availability of PHI(ePHI).
SOC 2 Type 2
Pushwoosh possesses a SOC 2 Type 2 report, reflecting our commitment to ensuring the utmost security of user data.
DPF certified
Pushwoosh is officially certified under the EU-U.S. Data Privacy Framework, including the UK extension, and the Swiss DPF.
Two ways to launch
Start without code today, automate when you’re ready — both routes run on the same account.
1. Start without code
One shared pass for everyone — a general admission ticket. Build it once, then drop the link or QR code into push, email, SMS, your site, or the till; allow multiple holders on Google Wallet so one link works for all.
What you’ll need:
- Apple Wallet — a Developer Program membership and a signing certificate uploaded to Pushwoosh. No iOS app.
- Google Wallet — a Wallet Console issuer account and a service account key.
- Door check — your ticketing system validates the barcode; entry control stays on your side.
2. Automate in Customer Journey
A personal ticket for every buyer: a pass campaign plus an Issue Wallet Pass step in a journey, with seat and row from the order. Shared-field edits handle schedule changes for everyone at once.
Everything from Route 1, plus:
- Order data — purchase events with seat and row, linked to a User ID.
- A trigger event — the purchase that starts the journey issuing the ticket.
Already in your Pushwoosh account
A pass doesn’t deliver itself. The channels that carry it and the customer data behind it are already in your account — so the price of running Wallet looks like this.
What your Wallet setup includes
- Email — puts the ticket in the order confirmation
- Mobile push — sends doors-open reminders and change alerts
- Customer Journey Builder — issues the ticket right after purchase
- Segmentation & CDP — finds attendees for the next event’s offer
Wallet add-on fee: $0 — it’s part of the platform, your price depends on your plan.
Set. Now go.
Start with one general admission pass — after the one-time Apple and Google setup, your team runs it without code. When you're ready, automate personal tickets with seats mapped from your order flow.
Questions organizers ask before they start
Explore related products
Issue Apple Wallet and Google Wallet passes in Pushwoosh and send them to the right segment by push, email, or SMS. One platform, no add-on fees.
Issue boarding passes to Apple Wallet and Google Wallet at check-in and keep gate, seat, and time current up to departure, from the platform you use for push.
Launch a restaurant loyalty program in Apple Wallet and Google Wallet. Digital stamp cards and coupons update after every order, and guests don't need an app.
Put your gym loyalty program and membership cards in Apple Wallet and Google Wallet. Plan, status, and renewal date stay current without code.
Optimize every touchpoint of the customer journey for e-commerce. Map shopping paths, personalize experiences, and maximize lifetime value.
Add labelled action buttons to the push you already send, so users accept, claim, approve or track in one tap. Build the iOS button sets no-code in the Pushwoosh Control Panel and send them from the same campaign and Journey.