Event readyFirebase scope Event scope 01 Event scope
Event
Associate the service-account configuration with a specific event.
Firebase integration for event apps
Connect Firebase push delivery to the attendee app experience
Store the service-account configuration used by your EventHex environment, register attendee device tokens, respect push preferences, and send supported notification payloads to iOS and Android devices.
Event, organization, or global configActive device tokensiOS and Android payloads
Configure Service accountRegister Device tokenRespect User preferenceTarget One or many tokensSend FCM payloadReview Success or failure
Store Firebase credentials where the deployment model needs them
Event readyFirebase scope Event scope 
Org linkedFirebase scope Portfolio scope 02 Portfolio scope
Organization
Associate a configuration with the franchise or organization.
Global activeFirebase scope Platform scope 03 Platform scope
Global
Maintain a platform-level configuration where the environment uses it.
Use the service-account data required by Firebase Admin
Project identity
Project ID, configuration name, optional bundle ID, and active state.
Service account
Private key ID, private key, client email, and client ID.
Google endpoints
Authentication, token, certificate, and optional database URLs.
Safe responses
Return masked or omitted secret values when the configuration is read back.
Attendee device registration
Keep the current device token attached to the right attendee
Show the mobile-to-API mechanism without losing the device state that makes delivery addressable.
Book a Demo 01
App obtains a token
The attendee app receives the FCM token for the device.
Token received Register token 02
EventHex registers it
Store the token with device type, active state, and last-used time.
Attendee linked Attach attendee 03
Refresh or reuse
Update the existing record when the same token is registered again.
Token refreshed Refresh record 04
Unregister when needed
Remove a token when the app or attendee signs out of the delivery path.
Ready to deliver Deliver safely Respect the attendee setting
Send only when push notifications are enabled for the user
The attendee still controls operating-system permission; the EventHex preference is one gate in the delivery path.
Push enabled
When the attendee has enabled push notifications, the device remains eligible for supported delivery.
ON · EligibleOFF · Skip deliveryPush disabled
When the attendee turns push off, respect that preference before the provider send path runs.
Format the supported push for Android and iOS delivery paths
-
01
Notification
Send a title, body, and an optional absolute image URL.
-
02
Data payload
Attach supported navigation and event data alongside the visible message.
-
03
Android
Use the configured high-priority channel and default sound payload.
-
04
Apple devices
Use the APNs payload with sound and badge values.
Use the delivery layer for supported in-app notification purposes
User notification
Open the notification area with the supported navigation payload.
General announcement
Send a title and body as an app announcement.
New message
Notify a user that a supported in-app message is waiting.
Reminder
Use the applicable event workflow to create the notification content.
One or many attendees
Send to active tokens stored for one user, one registration, or selected attendees.
Fit push infrastructure to the appand event operating model
Keep attendee delivery on track
Support app announcements and attendee messages where the event app is deployed.
SUPPORTED PATH- Active device tokens
- Supported notification payloads
- Per-token delivery results
Active devices readyReach the right registered users
Reach selected registered users through their active app tokens without losing delivery addressability.
SUPPORTED PATH- Target one attendee or many
- Respect push preferences
- Reuse refreshed device tokens
Recipients resolvedMatch delivery to the app model
Use organization or event configuration according to the branded-app environment.
SUPPORTED PATH- Event or organization scope
- iOS and Android payloads
- Safe configuration responses
Delivery job completeValidate every client app before launch
Validate each client app's Firebase project, credentials, bundle, and token lifecycle before launch.
SUPPORTED PATH- Firebase project identity
- Credential and bundle checks
- Invalid-token cleanup
Response reviewedDelivery infrastructure, not campaign strategy
Keep Firebase setup separate from notification orchestration
This integration page
Firebase configuration, device tokens, preference checks, payload transport, and provider send results.
✓ Delivery path readyReview tokens✓ Results recordedView responseEvent Notifications
Message planning, audience rules, timing, templates, channel choice, and operational reporting.
Do not promise scheduling, rich action buttons, frequency capping, or open/click analytics here unless their organizer surfaces are separately verified.
Continue into the feature that owns the experience
→
Event Notifications
Plan and operate attendee messages across the available channels.
Learn more →Event Mobile App
Give attendees the app experience that receives supported mobile notifications.
Learn more →Event Gamification
Connect engagement and reward moments to the attendee experience.
Learn more →WhatsApp Integration
Configure the account and approved templates behind WhatsApp delivery.
Learn morePush Integration Questions, Answered.
Find clear answers about Firebase credentials, device tokens, preferences, delivery scope, and supported notification paths.
Talk to our team1. Does EventHex support iOS and Android push paths?
Yes. The current sender builds Android and APNs payloads through Firebase Cloud Messaging. The attendee still needs the relevant event app and push permission.
2. What Firebase credentials are required?
The configuration accepts Firebase service-account fields such as project ID, private key, client email, and related authentication URLs. Validate the exact deployment requirements with the EventHex team.
3. Can we store configuration for one event?
The API model supports event, organization, and global scopes. Confirm which configuration the target app build and delivery environment will use.
4. What happens when an attendee disables push?
The send path checks the user's notification setting and skips device delivery when push is disabled.
5. Can EventHex guarantee delivery in under one second?
No. Delivery timing depends on Firebase, Apple/Google services, network state, the device, and app conditions. This page makes no latency guarantee.
6. Can we track opens and clicks?
The verified integration reports provider send success/failure and invalid tokens. A customer-facing open/click analytics surface was not verified for this page.
