Oxford Abstracts integrations so presenters register once and the program stays right.
Oxford Abstracts runs the review well. We connect it to the registration system and app you chose and to your membership system, so presenters register once at the right rate, the program stays right everywhere, and the committee report is one file.

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 retyped into the app you chose.
- Membership has no idea who presented this year.

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. Account and event administrators can set up API users, so we work through the API on a sensible schedule and match presenters on more than an email address.
Where Oxford Abstracts’ own integrations stop
Oxford Abstracts brings registration status in from EventsAir and idloom and sends sessions out to Cvent, Swapcard and Conference Compass. 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
Event Data Pro is an independent company. Oxford Abstracts and other product names belong to their owners.
Common Oxford Abstracts integrations
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.
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.
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 map out your event’s data and goals.
We figure out what you’re doing today, where you want to be and a detailed plan to get you there. It has everything you and your IT team need.
That becomes your Event Data Blueprint.
You keep it whether you hire us or not.
If you want to work with us, we’ll build it with a money-back guarantee.

$3,500 to $7,500
Typical first integration
40 to 90 percent less to reuse it for your next event
No subscription. No annual contract.
Money back guarantee. If you’re not satisfied with the integration, we’ll refund you.