Accepted presenters registered once
Accepted presenters created in your registration system at the presenter rate, with registration status back in Oxford Abstracts so you can see who has not paid.
Oxford Abstracts integrations
Oxford Abstracts integrations so presenters register once and the program stays right.
Oxford Abstracts runs the review well. Then the decisions go out, presenters ask why they had to register twice, a volunteer retypes session titles into the app, and someone stitches three exports together for one report. We connect the abstract system to registration, the app and your membership system so that stops.
Sound familiar?
Decisions went out Tuesday. The spreadsheets started Wednesday.
Decisions went out from Oxford Abstracts on Tuesday. By Thursday the registration team is matching two spreadsheets by email to find presenters who have not paid, a volunteer is retyping session titles into the app, and a presenter emails to ask why she had to register twice.
- Presenters register in Oxford Abstracts and then again for the conference, and they ask you why.
- You export submissions, then decisions, then affiliations, and stitch them together.
- The program is right in the builder and wrong in the app.
- Membership has no idea who presented this year.
We live in your world
We know how Oxford Abstracts holds a submission.
Submissions have child rows for authors and affiliations, decisions carry acceptance types and program codes, the program builder turns them into sessions with chairs and locations, and registration status can come in from outside. There is an API for account administrators, no webhooks, so we poll on a sensible schedule and match presenters on more than an email address.
Where Oxford Abstracts’ own integrations stop
Oxford Abstracts can pull registration status in from Cvent, EventsAir and idloom and push sessions out to Swapcard. That covers a common pairing. We handle everything else: presenters created in your registration system at the presenter rate, the program kept current in any app or website, presenter history and member status exchanged with your membership system, and one report that joins submissions, decisions and registration. The same approach works for ScholarOne, ProposalSpace and Fourwaves exports.
We speak Oxford Abstracts
Submissions and child rowsReviewing and decision stagesAcceptance types and program codesProgram builder and sessionsSession chairs and locationsDelegate registrationRegistered externallyAPI users
Event Data Pro is an independent company. Oxford Abstracts and other product names belong to their owners.
How we do it
Common Oxford Abstracts integrations
The program in your app and on your website
Sessions, presenters and rooms from the program builder kept current in any app or site, not only the ones with a connector.
Presenters on the member record
Who presented, and what was accepted, recorded in your membership system, and member status available for pricing.
One report across submissions, decisions and registration
Abstracts, affiliations, decisions and who actually registered joined into one dataset for your program committee.
Attendance to the credit system
Attendance and evaluations for accepted sessions delivered to the platform that issues credits.
What done looks like
Every accepted presenter is registered at the right rate without asking, the program matches the app, and the committee report is one file instead of three.
How every project starts
We start with a free consultation - about two hours of discovery kicking off with a 30-minute call. We map out where your data lives, the business rules your event follows, and what your IT team will need to see. You keep that document whether you hire us or not.
If you do hire us, a first integration is typically $3,500 to $7,500, and reusing it for your next event costs 40 to 90 percent less. No subscription. No annual contract.
Money back guarantee. If you’re not satisfied with the integration, we’ll refund you.