Networking process

Networking in ERADIANT connects ticketing, the event, and the public event website — including:

Event sync (ticket data into the event)
Locations and time slots (meeting booking)
Networking page (website, code, login)
Event mailing (code delivery and testing)

This page walks through the typical setup — from data transfer to pre-event testing.

This page complements the detailed documentation of

1. From ticketing to the event — data transfer

For purchased tickets to appear in event networking, you need event sync between ticketing and the event.

What happens during sync?

In ticketing, open Event sync and link the ticketing to the matching event.
Once an order line meets the sync conditions (product, payment status), ERADIANT automatically transfers data into the event.
The person appears under Participants in the event and — if configured — in the public networking participant list.

Sync runs continuously when relevant changes occur (e.g. new order, payment, cancellation, check-in, updated questionnaire answers). Important: This only works if the preset networking question is used.

Which data is transferred?

ERADIANT typically syncs:

Core data: first name, last name, email, title, institution, position
Ticket info: product name, product ID, price, registration and cancellation dates
Check-in: timestamp of the latest real check-in (if available)
Networking code: personal code per ticket/order line — stored in the event as the login code during sync
In networking: whether the person appears in the public networking list (via the ticketing question “Participate in networking?” or the system field Show in networking)
Participant properties / filters: answers to ticketing questions (single/multi select) mapped in event sync to participant properties

Without event sync, ticket buyers do not automatically appear in event networking.

Recommended order

Create participant properties / filters in the event
Configure matching ticketing questions (single/multi select)
Set up event sync and question mappings
Place a test order and verify data under Participants

More details: Event sync component and Participants component.

2. Locations and time slots

Locations and time slots are the foundation for booking meetings. Both are managed in the event under Networking.

Time slots

Under Networking → Time slots you define when networking meetings can take place.

Not too few time slots: With only one or two slots, bottlenecks appear quickly — participants can no longer find a suitable time.
Not too many time slots: Very many short slots make selection confusing and capacity planning harder.
Practical tip: Plan several 15–20 minute slots in your dedicated networking phases (e.g. lunch break, afternoon networking).
Mind the time zone: Start and end times use the event time zone.
Finalize before go-live: Make major time slot changes before live operation whenever possible, especially if appointments already exist.

Locations

Under Networking → Locations you define meeting points (e.g. “Networking table 1”, “Lounge A”).

Important rule: Each location can only be used once per time slot.
If two meetings happen in the same slot, ERADIANT needs two different locations. Assignment is automatic — participants do not pick the location themselves.

Create enough locations: Estimate how many parallel 1:1 meetings you expect in your busiest slot — you need at least that many active locations.
Create the same physical place multiple times: If you have three tables in the same lounge, create “Lounge table 1”, “Lounge table 2”, “Lounge table 3” as separate locations — even if they are close together.
One location across multiple time slots: The same location entry can be reused in different time slots (just not twice in the same slot).
Deactivate instead of delete: Locations already in use are deactivated when needed so existing appointments remain intact.

3. Setting up the networking page

Networking page on the event website

Open the event and go to Website.
Create a page (e.g. “Networking”) or edit an existing one — see Manage event website.
Add the appropriate networking blocks — see Edit page → Networking blocks:
- Networking search bar and Networking filters (usually above the people list)
- Networking people list (shows the participant list)
- Networking contact dialog and Networking chat (contact and scheduling)
- Networking QR code (optional — quick sharing of contact details on site)
Check that the page is visible to participants (publish status, navigation).

You can put all networking blocks on one page (handy for smaller events) or move networking to a dedicated subpage (useful for large events).

Where do I find the networking code?

You can find the personal networking code here:

Event → Participants: column Networking code (after successful event sync)
Ticketing → Reporting → Export: networking_code column in the CSV export of order lines

The code is generated automatically per ticket/order line and transferred to the event during sync.

How do participants log in?

Participants authenticate on the event website via the networking code in the URL, e.g.:

https://your-event-domain.com/networking?networking_code=ABC123

After login, protected areas (networking list, chat) no longer require the code for that session.
Links in system emails (e.g. appointment confirmations, networking reminders) already include the code as a parameter.

4. Sending the networking code by email

Participants need the networking code to log in. The simplest way to send it is via an event mailing:

Create a template under Mailings → Templates.
Add the {{networking_code}} placeholder — e.g. as a link to the networking page:

https://your-event-domain.com/networking?networking_code={{networking_code}}

Under Recipient filters, set Networking participation to Has at least one ticket marked for networking participation — so only people who participate in networking receive the mailing.
Send a test mail before sending to everyone.

More details: Placeholders and Recipient filters.

5. Testing networking

Before go-live, walk through the full flow once:

Verify event sync
Place a test order in ticketing → check Event → Participants for name, In networking, and Networking code.
Verify locations and time slots
Create at least one active time slot and enough active locations (see sections above).
Open the networking page in participant view
From the dashboard → Participant view, open the public website — see Participant view.
Log in with a networking code
Copy a networking code from Participants and open the event URL with ?networking_code=… (or use a test link from an event test mail).
Click through features
Test people list, filters, chat, meeting proposal, and acceptance — verify that a location and time slot are assigned.
Check accepted appointments
In the event under Networking → Accepted appointments, confirm test appointments appear.

For two perspectives, test with two different networking codes (e.g. two test tickets) to simulate contact and scheduling between two people.

Summary

Without event sync, ticket data is not automatically transferred into event networking.
Create participant properties before sync setup so question mappings are available.
Without active time slots or locations, new appointments cannot be booked — see also Troubleshooting → Networking appointments.
The networking code is personal — treat it like a login password and only send it to the authorized person.
Plan locations and time slots together: for your busiest slot you need as many locations as expected parallel meetings.
Use clear location names (number + area) so participants find the meeting point quickly on site.
Send an event mailing with networking link and {{networking_code}} one or two weeks before the event so participants can log in early. A second mailing works well as a reminder.
After major website changes, switch to participant view briefly — especially on mobile.
Review networking activity in the event: Event statistics and Networking component.