Skip to main content
events · methodology

How the events record is built

We collect industry conferences from eight sources and keep what the organiser published: the dates, the place, the format, the ticket price. The English pages carry the organiser's own announcement — 373 events have one.

What this section is

NeEvents is a record of affiliate, CPA and iGaming conferences, summits, meetups and webinars. We collect them from eight sources, deduplicate them, and keep the dates, the place, the format and the ticket price where the organiser published them.

An English card carries the name of the event and the organiser's announcement. Where the organiser wrote them in English, they stand as they came. Where they came in Russian, what you read is our translation of that same announcement — the same facts, the same dates and prices, in English. Of 2292 published events, 373 have an English card.

Which events are here

There is no language column in the data, so the test counts alphabets, and it counts them on the text the English card would actually show — the translation where we have one, the original otherwise. An event gets an English card when that name holds at least 3 Latin letters and no Cyrillic at all, and that announcement holds at least 20 Latin letters with Cyrillic under 10% of all letters.

A translation that comes back with Russian left in it is rejected and the card stays Russian-only. That is the point of counting letters instead of checking whether a column is filled: a filled column is not an English page.

The name is held to zero Cyrillic, not to a share. One Russian word in a conference name shows up in every listing row that mentions it, and a share would let it through.

What we do not show here

  • The long body of a Russian card. That text is ours, written in Russian by a generator from the same announcement. Translating our own retelling would put a third copy of one story on the site, so the English card carries the announcement and the facts, and nothing else.
  • Catalogue filters. On the Russian side they run under noindex and they are fed by city names stored in Russian. The country, city and month hubs give the same slices with addresses worth indexing.
  • The Atom feed and the .ics calendar. Both carry the same event text as the card, and neither changes with the language — the existing addresses work as they are.

Which slices exist

A country, city, month, year or vertical gets an English page from 5 events. Below that the address returns 404 rather than a page with three rows — a slice that thin is not a page, and the parent hub already carries the number.

Countries21ISO country codes with enough events. Online events without a country are not here.
Cities18Both spellings of a city fold into one hub: the slug is built from a dictionary, so London and Лондон are the same page.
Months29A month page exists from five events. Past months are published but kept out of the sitemap.
Years6The full calendar of a year, grouped by month.
Verticals4iGaming, CPA and the rest. The slug online is a format, not a vertical — that address came from confa.biz and we keep it.

Place names

Sources write the place in whichever alphabet they feel like, and the record keeps it as it arrived. On an English page the city is resolved in three steps: Latin spelling as it stands, then a dictionary of the industry's cities, then the most frequent Latin spelling of the same city elsewhere in the record. If none of the three works, the page shows the country alone rather than a Russian word.

Countries are stored as ISO codes, so their English names are not a judgement call. A venue is printed only when it is written in Latin letters and does not merely repeat the city.

What goes in the sitemap

  • A card is submitted for indexing while the event is under twelve months old. The archive stays reachable by link and leaves the sitemap — it is the card that keeps catching "how did X go" searches, not the crawl budget.
  • Events of the general vertical that have already passed are a legacy import of IT and business conferences and have nothing to do with this industry. They are out, in both languages.
  • The archive page and past months are published but not submitted: a list without content of its own is index bloat, and the year pages carry the shape of the calendar.

Limits we will state plainly

  • Dates and venues come from organisers and move. We re-read the sources, we do not confirm the schedule ourselves.
  • A ticket price is whatever the organiser published at collection time; early-bird tiers are usually lower. Sums are not converted between currencies.
  • The alphabet test distinguishes scripts, not languages. A Spanish announcement written in Latin letters would pass it; none were found in this record, which comes almost entirely from one source of English press releases.
  • An event whose announcement is Russian has no English page at all, by design. It is not hidden: the Russian card is a click away through the language switch.

← back to events

Project sponsors

Companies that keep this analytics open