Planned maintenance: Tue Dec 8, 11:30pm–12:30am ET (8:30–9:30pm PT / Wed 5:30–6:30am CET). Brief downtime possible (up to 15 minutes).

Status page
Skip to main content

How can we help?

Need help? Check out our documentation or contact support

Search

Eloqua integration - Connect Bevy to Eloqua

  • Updated

Connect Bevy to Eloqua from Settings → Integrations so community data posts one-way into Eloqua forms you choose. A community admin turns Connect on, enters the Eloqua site name and base URL, selects forms, maps fields in the setup wizard, then verifies sync.

Bevy posts selected community records one-way into Eloqua forms through the Eloqua API. Changes you make in Eloqua do not write back to Bevy. After a create or update in Bevy, Eloqua usually shows the change within about five minutes. That timing is fixed. For what syncs and who should use this integration, see Eloqua integration - Introduction.

Note: Draft events are not synced. Hidden events do sync. Bevy also sends status for canceled or live events, and attendee status updates such as registered to checked in.

Who can connect

Bevy turns on the Eloqua card for your community. If you do not see Eloqua under Settings → Integrations, contact your Customer Success Manager or Bevy Support.

After the card is available, a community admin connects Eloqua from that page.

Before you connect

  • Create (or choose) Eloqua forms that should receive Bevy user, attendee, and event data. Prefer non-production forms for the first test.
  • Have Eloqua access that can authenticate to your site and read those forms’ fields.
  • Know your Eloqua site name and base URL (see below).

Find your Eloqua site name and base URL

Site name is the company name associated with your Eloqua account — the same company name you enter when you log in to Eloqua.

Base URL is the host from your Eloqua browser address after you log in. It looks like secure.p03.eloqua.com (your pod number may differ).

Important: When you enter the base URL in Bevy, do not include https://. Use only the host, such as secure.p03.eloqua.com.

Connect Eloqua

  1. Sign in to the Bevy admin dashboard as a community admin.
  2. Go to Settings → Integrations (/accounts/dashboard/#/admin/settings/integrations/).
  3. Find the Eloqua card and turn Connect on. A setup wizard opens in a popup window.
  4. In the wizard, enter your Eloqua site name and base URL, then continue authentication as prompted.
  5. Still in the wizard, choose the Eloqua forms for user, attendee, and event data, then map fields (see Choose forms and map fields below).
  6. Finish the wizard and close the popup. Bevy enables the connection. The Connect toggle stays on.

As people create accounts, register for events, and publish events on your site, Bevy begins posting those records one-way into your Eloqua forms.

Choose forms and map fields

Form selection and field mapping happen inside the same setup wizard that opens when you turn Connect on. After you are connected, open the wizard again with the edit control on the Eloqua card to change forms, mappings, or credentials.

By default, Bevy can send first name, last name, and email for users and attendees, plus common event and registration fields. Use the wizard to map additional Bevy fields to Eloqua form fields.

Sync object Fields you can map (examples)
Users → user form First name, last name, email, date joined, deleted date. Additional Bevy user fields can be mapped.
Attendees → attendee form First name, last name, email, event title, event ID, event chapter ID, registration status, check-in date, created date, deleted date, ticket title. Additional Bevy attendee fields can be mapped.
Events → event form Title, short description, URL, start and end dates, status, chapter title and ID, event type, venue fields, created and updated timestamps, publisher name, hidden flag, and related event fields. Additional Bevy event fields can be mapped.

When someone signs up for a Bevy account, Bevy can post that person to your user form. When someone RSVPs, Bevy can post or update an attendee form submission — including when registration status moves to checked in. When an event is published or updated, Bevy can post or update an event form submission.

Fix authentication errors

If the wizard shows Error loading Eloqua fields. Please re-authenticate your integration and try again, the Eloqua authentication details are wrong or incomplete.

  1. On the Eloqua card, select edit to reopen the wizard.
  2. Check the site name against the company name you use to log in to Eloqua.
  3. Edit the base URL so it has no https:// prefix — only the host (for example secure.p03.eloqua.com).
  4. Save authentication, then continue to form selection and field mapping.

How data is sent

Bevy sends form submissions through the Eloqua API — specifically the Eloqua 2.0 REST Form Data API. Oracle documents that API in the Eloqua Marketing Cloud REST API reference.

Test the connection

  1. Finish Connect, form selection, and field mapping in the wizard.
  2. In Bevy, create a test user or registration (and a published test event if you need event form data).
  3. In Eloqua, confirm the form submissions. Prefer non-production forms for the first pass.
  4. After testing, use edit on the Eloqua card to point the same Bevy card at your production forms before go-live.

Change mapping or disconnect

  • View or change mapping, forms, or credentials: On the Eloqua card, select edit to reopen the setup wizard.
  • Disconnect: Turn Connect off and confirm. Syncing stops until you connect again.

Not included

  • You cannot change the sync timing from the roughly five-minute cadence.
  • Chapters and chapter members are not Eloqua sync objects.
  • Eloqua does not write data back into Bevy.