Protecting Your Edits

When you fix something on an event by hand, Esora protects that change — the automatic importer will never overwrite it. This is called field pinning, and it happens on its own the moment you make an edit.

The problem it solves

Esora re-checks your social media pages several times a day to keep event data fresh. Without protection, a re-import could undo a title you carefully corrected, revert a description you rewrote, or replace media you uploaded. Pinning makes sure that never happens.

How it works

Editing a field pins it. A pinned field is locked from automatic updates — the importer skips it on every future run. You don’t have to turn anything on; the edit is the pin.

Two things do not create a pin:

• AI translations — when the system generates the Armenian, Russian, or English versions, it doesn’t pin them (so it can keep improving them until you edit one yourself).
• AI categorization and imports — automatic category assignment, and the importer itself, don’t pin anything.

So the system keeps refining auto-generated content right up until you step in with a manual change.

Which fields get pinned

On the event:

• Title and description — these pin together with their translations, so editing one language locks all three
• Media (images and videos)
• Category
• Tags
• External URL

On each date:

• Start and end date & time
• Price
• Venue / address
• Whether the date is disabled

The stronger rule for your own events

Events you created yourself — and any event with native Esora ticketing — are never touched by the importer at all. The one exception is that it may fill a field that’s still empty (like a missing description, media, category, or external URL). Anything you’ve actually set stays exactly as you left it.

Seeing and removing pins

As you manage your events in the Esora Organizer app, fields you’ve edited are marked as pinned, so you can always tell which ones are protected from the importer.

You can unpin a field to hand it back to the importer — after which it can update that field again on the next cycle. Unpinning is useful when you edited something by mistake, or when the original post has been corrected and you’d rather let the importer take over again.

Example

1. Your post about a concert is imported. The AI extracts the title as “LIVE MUSIC: Jazz Night @BlueCafe” — not ideal.
2. You edit it to “Jazz Night at Blue Cafe”. The title is now pinned (along with its Armenian and Russian).
3. Next time the importer runs, it finds the same post but skips the title. If it spots an updated price or a new date on that event, it still updates those — they aren’t pinned.
4. Later, if you want the importer to manage the title again, unpin it — and the importer takes over that field on its next run.