In short
An event is created on top of a Linxy Mark you already own. You give it a name, a type, and a start and end date, and it appears as a draft. From there you turn on the parts you want — check-in, group chat, a public listing — because all of them start switched off.
One decision on that first form cannot be revisited: the event type. It looks like a category for filing and it is not. The type determines which tags your attendees are offered when they describe themselves, and it does so by withholding whole groups of them — a social event does not offer the industry or job-title pools at all. Choosing the wrong type produces an event where networking quietly cannot work properly, and the only fix is a new event on a new Mark.
On this page
- An event lives on a Mark
- What you have to decide up front
- Choosing the type — the permanent one
- What you get without configuring anything
- Draft, active, ended
- What scanning the Mark opens
- The three switches that start off
- Listing an event publicly
- Symptoms, causes and fixes
- Things people commonly get wrong
An event lives on a Mark
Events are not created from nothing. You pick one of your existing Linxy Marks — or rather the Dynamic Link behind it — and build the event on that. The Mark becomes the event’s front door: scanning it is how people reach the event. In the Linxy Mark editor, the Mark’s Event & Networking card has Set Up Event, or Manage Event once there is one; your events are also listed under Events in the web app.
Two consequences follow, and both are permanent.
One event per Mark. Trying to create a second event on a Mark that already has one is refused, and the refusal tells you which event is already there. This is helpful rather than obstructive: if you have lost track of an event, pointing the create form at its Mark will find it for you.
The Mark cannot be swapped afterwards. The binding is set at creation and is not among the things an update can change. If you have printed the wrong artwork, the event has to be made again on the right Mark.
What you have to decide up front
| Field | Required | Changeable later |
|---|---|---|
| Name | Yes | Yes |
| The Mark it runs on | Yes | No |
| Event type | Yes | No |
| Start and end date | Yes | Yes |
| Secondary event type | No | Yes |
| Description, venue, address, image | No | Yes |
| Map position | No — Linxy works it out from the venue address | Yes |
| Linked geofence and community | No | Yes |
The Mark must be one you own. Pointing at somebody else’s produces a plain not-found rather than a permission error, so if a Mark you expected is missing from the picker, check whose account it is in.
Hosting events requires a plan that includes them. Without one, creating an event is refused outright — you will not end up with a half-working event.
Choosing the type — the permanent one
Event types come from a fixed catalog, arranged into categories: professional gatherings, social occasions, entertainment, community events, sports, education. You choose one; you do not invent one.
The type does three things. It sets the tone of the attendee onboarding. It carries a safety tier, which travels with the event and is visible to anyone looking at it. And — the part that surprises people — it decides how much of themselves attendees are permitted to advertise.
You may add a secondary type, and this one can be changed later. It widens the palette by adding that type’s tags on top. It is the right tool for a hybrid — a conference with an evening social, a fundraiser with a professional program — and it is the closest thing there is to changing your mind about the type.
If you are unsure between two types, pick the more professional of the two and add the other as the secondary. Breadth can be added afterwards. It cannot be taken back and then re-granted.
What you get without configuring anything
| Setting | Default | Worth reviewing? |
|---|---|---|
| Timezone | America/New_York | Always. It governs every per-day rule |
| Tags per attendee | 12 | Rarely. Twelve is generous |
| Pending connections per attendee | 20 | Only at very large events |
| Tag visibility | Public | If the room is sensitive |
| Interests | On | No |
| Status | Draft | Always. Nothing works until it is active |
| Public listing | Off | If you want strangers to find it in Discover and Near you |
| In Discover, once public | On | Only if you want the event listed without its videos in Discover |
The timezone deserves the same warning it gets everywhere else in this help center: if it is left alone it is New York, not universal time and not wherever you happen to be. Every rule that counts something “per day” measures the day against it.
Draft, active, ended
An event begins as a draft and a draft is genuinely invisible. Asking for its public details returns nothing at all — not a stub, not a coming-soon page. You can build the whole thing, add tags, set the venue, and nobody outside your account can see that it exists.
Setting it active is what brings it to life. This is the step most often missed, and its symptom is comprehensive: nothing scans, nobody can check in, the listing is refused, and none of the error messages point at the status.
Ended retires it — but not completely. In the Linxy App its event page shows Ended and Check-in is closed, while connections made there keep working and attendees reach them from People you met. Ending an event closes the door; it does not clear the room.
What scanning the Mark opens
The Mark’s Event & Networking card has a Scans open the event switch. When it is on, a scan with the Linxy App opens the event page first — cover, dates, venue and Check in — with the Mark’s own content inside it as the featured content. When it is off, scans skip the event and open the content directly. The switch gives the Mark the Event role, and it is saved when you choose Update Linxy Mark.
- Your destination and routing rules still decide the content. The switch never changes them, and NFC tags written inside the Mark keep their own destinations.
- A draft opens the content. While the event is still a draft, scans open the content until you make the event active.
- The Mark can’t point at itself. A destination that is the Mark’s own link is refused when you save — choose content that lives somewhere else, such as a video, a page or a file.
Opened in a web browser instead of the App, the Mark shows a public event page with the featured content and a Check in with the Linxy App panel. See Scanning an event Mark.
The three switches that start off
Three capabilities cannot be turned on when the event is created. They exist only as later changes, which means every new event has all three off whether or not you intended that.
| Switch | Until you turn it on |
|---|---|
| Check-in | Attendees are refused with “check-in is not open yet”. Nobody can select tags, so networking cannot start at all |
| Group chat | The event chat does not appear in anybody’s app |
| Public listing | The event does not appear in Discover or Near you in the Linxy App |
Check-in is the one to watch. Because tag selection requires an attendee record, and an attendee record is only created by checking in, leaving check-in off produces an event where the networking features are all present, all visible, and all inert.
Listing an event publicly
Listing is refused unless three things are true, and each has its own message so you always know which one you are missing.
| Requirement | Why |
|---|---|
| Status is active | A listed draft would be a dead link in a public feed |
| A description exists | The feed entry would be a name and nothing else |
| A venue name exists | People deciding whether to attend need to know where |
Removing a listing has no such conditions. You can unlist at any moment, and unlisting does not end the event or disturb anybody already attending.
Once an event is public and active, your Events list on the web adds two more controls for it: In Discover or Not in Discover, and Request to feature. Near you measures distance from the venue address, which Linxy places on the map when you save, so use a full street address. See Getting your event into Discover.
Separately from listing, people can register intent: going, maybe, or interested — and they can withdraw it. This is independent of checking in, which happens on the day, and the buttons disappear for each person once they have checked in.
Symptoms, causes and fixes
| Symptom | Cause | Fix |
|---|---|---|
| “An event is already associated with this mark” | That Mark is in use | Use the event id in the refusal to find it, or pick another Mark |
| The Mark is not in the picker | It belongs to another account | Check which account owns it |
| Nobody can check in | Check-in has not been switched on, or the event is still a draft | Set the event active, then enable check-in |
| Attendees see no tags worth using | The event type withholds those pools | Add a secondary type. The primary cannot be changed |
| The public page shows nothing | The event is a draft | Set it active |
| “Event needs a description and venue name” | Listing prerequisites are not met | Fill both, then list |
| Re-entry and day counts reset oddly | The timezone is still the default | Set the event timezone |
| The event chat is missing for everyone | Group chat has not been enabled | Turn it on. It is off on every new event |
Things people commonly get wrong
Related reading: Attendee networking, Scanning an event Mark, Getting your event into Discover, Tickets and passes, Operating the gate, and Collecting guest media.