Marketing Automation · Integration
Splash
Add Splash to your product for your customers, and give your AI agents governed access to it.
Splash runs event marketing: the branded page, the registration form, the invitations and reminders, and the check-in at the door. That last part is what separates it from a campaign tool, because attendance is a fact that only exists after the event and it is the most useful signal the whole programme produces. An embedded Splash integration creates and reads events and their pages, reads registrations, RSVPs and check-ins, adds contacts to an invitation, and reads the engagement around a send. Because a person can register and not turn up, or turn up without registering, your product should read the state rather than treat a registration as attendance. fastn keeps each customer's credentials per tenant and follows the API.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Splash account so events created in your product get a branded page and a registration form.
Read registrations and check-ins so your product knows who said they would come and who actually did.
Trigger an invitation from an event in your product, so the audience follows behaviour rather than a static list.
Read email engagement around an event send so your product reports on the whole programme, not just the page.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which registrants did not attend and which attendees never registered.
An agent summarises an event from its registrations, check-ins and email engagement together.
An agent adds an approved contact to an invitation list within scoped permissions, with the action logged.
Example prompt
How many people who registered for this event actually checked in, and which segments turned up?
Set up Splash in 4 steps
- 01Enable the Splash connector in your fastn dashboard.
- 02Have each customer authorise their own Splash account so events and attendee data stay theirs.
- 03Map the event, registration and check-in fields your product uses, then enable the sends you trigger.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Splash integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Splash integration without building it. Your customers connect their own Splash account inside your product and work their campaigns, segments and subscribers there, with no per-customer code on your side.
- Handle the part that actually costs time: engagement data arrives as a high-volume event stream, so ordering and deduplication matter. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Splash update is not your on-call problem.
- One integration serves your product and your agents. The same governed Splash connection powers in-product features and gives AI agents scoped, audited access, so you trigger and measure campaigns from inside your product without wiring it twice.
Used by these teams
Compare with
Cvent
Hopin
MarketoOften used alongside
Tools the same teams tend to run next to Splash, across other categories.
Salesforce
HubSpot
Pipedrive
Zoho CRMSplash integration FAQ
How do I add a Splash integration to my product?
Enable the Splash connector in your fastn dashboard, then let each customer authenticate their own Splash account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Splash client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Splash account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Splash account and only ever sees their own campaigns, segments and subscribers. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Splash integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reports which registrants did not attend and which attendees never registered.
Who maintains the Splash integration?
fastn does. When Splash changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can I trigger a Splash campaign from an event in my product?
Yes. Product events can start a campaign, add a contact to a segment, or enrol someone in a journey, so lifecycle messaging follows what a user actually did rather than a nightly export.
Can I read engagement results back from Splash?
Yes. Results come back scoped per tenant, so your product can act on them without one customer's data mixing with another's. What you get depends on the channel: opens, clicks, bounces and unsubscribes where there are sends, and impressions, spend and conversions where there are campaigns.
What can I build with the Splash integration?
A common starting point: let each customer connect their own Splash account so events created in your product get a branded page and a registration form. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Splash integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Splash does not change your per-connector cost. You can start free with 3 connected accounts.
Add Splash to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.