Campaigns
Event email, on your approval.
Write it, test it, send it to the people it is for, then see what it sold. Nothing goes out until you say so.
The actual problem
Your email tool does not know who bought a ticket.
A separate email tool sees addresses, not attendees. You export a list, import it, send, and then guess which email moved tickets, because the two systems never meet again.
How it works
Sent from the record that sold the ticket.
Compose, preview and send yourself a test, then send to your ticket holders, or to a segment of your audience on Portfolio. The assistant drafts the campaign in your voice, from a sample you paste. You approve every send.
Afterwards
See what each campaign earned.
Revenue is tied back to the campaign that produced it, in tickets and in dollars, through the checkout itself.
Channels
Email is the channel. Ads get the copy.
Campaigns send by email. For paid social, Janix writes ad copy for Meta, and on Portfolio exports a segment as a Custom Audience. Posting and ad buying stay in Meta, where they already are.
The full list
From draft to what it sold.
What Janix Event Suite does with campaigns, in one list.
Campaigns — 10 capabilities
- Compose, preview, test-send and send
- Drafts in your voice, from a sample you paste
- Approval before every send
- A/B subject lines with the winner promoted
- Server-side CAN-SPAM enforcement
- Revenue attribution per campaign, in tickets and dollars
- Retry failed sends only
- Delivery logs with state and statistics
- Ad copy for Meta
- Custom Audience export to Meta (Portfolio)
Bring last year's campaign.
The emails you sent and what you think they sold. Thirty minutes on what the numbers would have said here.