# EventAnalytics

> Analytics for trade show and exhibition organisers. Articles on measuring registration, exhibitor performance, rebooking, identity resolution and event data platforms. Every claim is either attributed to named published research or shown as a worked calculation.

## AI for organisers

Where AI helps an organiser and where it does not. Retrieval and grounding, evaluation, human review, natural language querying, model cost, governance and failure modes.

- [When AI generated event reports invent a number nobody measured](https://eventanalytics.ai/blog/ai-generated-event-reports/): AI generated event reports fail when the model summarises a dashboard rather than a query result. How to ground, source and review post-show narrative properly.
- [Natural language querying of event data and what it actually gets right](https://eventanalytics.ai/blog/natural-language-querying-event-data/): What natural language querying of event data gets right on a registration schema, why enterprise warehouses break it, and what a semantic model has to carry.
- [What text to SQL accuracy benchmarks tell an event data team](https://eventanalytics.ai/blog/text-to-sql-accuracy-benchmarks/): How to read text to SQL accuracy benchmarks like BIRD and Spider, what the human baseline means, and how to map the published gap onto your own show week.
- [Verifying an AI generated query before anyone quotes the answer](https://eventanalytics.ai/blog/verifying-an-ai-generated-query/): Verifying an AI generated query means showing the SQL, the row count and the filter set beside it, because a query that runs can return the wrong rows.
- [Grounding AI summaries in aggregates the reader can check themselves](https://eventanalytics.ai/blog/grounding-ai-summaries-in-aggregates/): Grounding AI summaries in aggregates means every sentence traces to a row the reader can open, scored in two stages: did it answer, is each claim supported.
- [Building provenance for AI generated numbers into every report line](https://eventanalytics.ai/blog/provenance-for-ai-generated-numbers/): Provenance for AI generated numbers means a figure carries its query, source tables, filter set and run timestamp, so a disputed number settles in a minute.
- [Writing an AI summary of show metrics that survives a line by line check](https://eventanalytics.ai/blog/ai-summary-of-show-metrics/): How to build an AI summary of show metrics from precomputed aggregates, forbid the model any arithmetic, and match every figure back by string comparison.
- [How hallucinated metrics get into AI reports and who notices last](https://eventanalytics.ai/blog/hallucinated-metrics-in-ai-reports/): Hallucinated metrics in AI reports arrive by four routes, only one of which involves a model, and the person best placed to catch one has the least authority.
- [Hallucination rate measurement for an assistant that answers with numbers](https://eventanalytics.ai/blog/hallucination-rate-measurement/): Hallucination rate measurement needs a stated unit, a frozen sample and a confidence interval, because a rate graded off thirty answers resolves almost nothing.
- [Numeric consistency checks that catch a wrong figure before publication](https://eventanalytics.ai/blog/numeric-consistency-checks/): Numeric consistency checks parse every figure out of generated text, recompute it from the same aggregate, and fail the response when the two disagree.
- [Building an evaluation set for an event assistant from real questions](https://eventanalytics.ai/blog/evaluation-set-for-event-assistant/): An evaluation set for an event assistant is harvested from questions your team already asks, then graded against the SQL that produces the true answer.
- [How far to trust LLM as judge reliability when grading your assistant](https://eventanalytics.ai/blog/llm-as-judge-reliability/): LLM as judge reliability is high enough to be useful and biased enough to mislead, so grade the grader with a human sample large enough to mean something.
- [Regression testing AI features when the model underneath keeps changing](https://eventanalytics.ai/blog/regression-testing-ai-features/): Regression testing AI features means pinning a question set and diffing result sets across versions, because a model upgrade is a code change with no diff.
- [Offline evaluation versus live monitoring for an assistant in daily use](https://eventanalytics.ai/blog/offline-evaluation-versus-live-monitoring/): Offline evaluation versus live monitoring is a coverage argument: an eval set grades the questions you thought of, and the log holds the ones people ask.
- [Retrieval augmented generation for organisers working from their own documents](https://eventanalytics.ai/blog/retrieval-augmented-generation-for-organisers/): Retrieval augmented generation for organisers means indexing post-show reports and board packs nobody rereads, then making each answer name its file and page.
- [Picking a chunking strategy for documents an event team actually keeps](https://eventanalytics.ai/blog/chunking-strategy-for-documents/): A chunking strategy for documents has to suit both a post-show report that splits at headings and a contract whose defined terms sit twelve clauses away.
- [Why hybrid keyword and vector search beats embeddings alone on event documents](https://eventanalytics.ai/blog/hybrid-keyword-and-vector-search/): Hybrid keyword and vector search wins on event documents because stand numbers, hall codes and product references are exactly what an embedding blurs away.
- [Measuring retrieval quality separately from the answer the model writes](https://eventanalytics.ai/blog/measuring-retrieval-quality/): Measuring retrieval quality on its own sets a ceiling on the answer, because if the correct passage never reaches the prompt no amount of prompting recovers it.
- [When rules beat a model for questions an event team asks daily](https://eventanalytics.ai/blog/when-rules-beat-a-model/): When rules beat a model comes down to counting repeats: a few dozen stock questions cover a show week, and a stored query answers each one exactly, for free.
- [Why models get arithmetic wrong and what to compute in SQL instead](https://eventanalytics.ai/blog/why-models-get-arithmetic-wrong/): Why models get arithmetic wrong matters for event reporting, because a percentage the model computed looks identical to one the warehouse computed.
- [Deciding where AI is the wrong tool for an event data problem](https://eventanalytics.ai/blog/where-ai-is-the-wrong-tool/): Where AI is the wrong tool comes down to three questions about rule stability, input structure and what an error costs, scored before anyone writes a prompt.

## Attribution

Where registrations came from, and how confidently you can say so. Source hygiene, unattributed records, multi-touch models, paid media measurement and incrementality testing.

- [The utm tagging conventions that survive five editions of one show](https://eventanalytics.ai/blog/utm-tagging-conventions/): A locked utm tagging convention where source is the platform, medium is the mechanism and campaign carries the edition code, with the lookup that fixes old tags.
- [How registration source tracking breaks between the ad click and the record](https://eventanalytics.ai/blog/registration-source-tracking/): Registration source tracking fails at six identifiable hops between the ad click and the saved row. Test each one with a single tagged link and fix the worst.
- [Capturing click ids on registration forms so paid credit survives the handoff](https://eventanalytics.ai/blog/capturing-click-ids-on-registration-forms/): Capturing click ids on registration forms puts a platform identifier on the registration row, and turns the gap against platform reported conversions into four causes.
- [Cross domain tracking for registration when the form lives on another domain](https://eventanalytics.ai/blog/cross-domain-tracking-for-registration/): Cross domain tracking for registration stops a hosted form counting your own site as a referrer, and collapses the duplicate sessions that flatter your traffic.
- [Build a channel grouping taxonomy before you argue about attribution models](https://eventanalytics.ai/blog/channel-grouping-taxonomy/): A channel grouping taxonomy turns raw source and medium pairs into eight reportable channels, with a first match wins order and a review queue for new values.
- [Print and direct mail attribution without a click to follow](https://eventanalytics.ai/blog/print-and-direct-mail-attribution/): Print and direct mail attribution needs vanity domains, one code per drop and a withheld control cell, plus the arithmetic that says how large that cell must be.
- [What to do with the unattributed registrations sitting in your file](https://eventanalytics.ai/blog/unattributed-registrations/): Unattributed registrations split into four causes with different fixes. Size each one over a single edition, then report the remainder as unknown rather than spreading it.
- [Direct traffic registrations are four different problems wearing one label](https://eventanalytics.ai/blog/direct-traffic-registrations/): Direct traffic registrations hide bookmarked returns, untagged email, referrer stripping apps and redirect loss. Three cross tabs separate them on your own file.
- [Measuring dark social event marketing when the sharing happens in private](https://eventanalytics.ai/blog/dark-social-event-marketing/): Dark social event marketing hides in private forwarding. Instrument it with share links, per person invite codes and a company domain cluster count on your own file.
- [Adding self reported attribution to a registration form without wrecking conversion](https://eventanalytics.ai/blog/self-reported-attribution/): Self reported attribution adds one open question after the commitment step, coded weekly into your channel taxonomy, and read beside tracked shares rather than instead.
- [Attribution coverage rate is the number to fix before you trust a model](https://eventanalytics.ai/blog/attribution-coverage-rate/): Attribution coverage rate is registrations carrying a usable source divided by all registrations. Measure it weekly and publish it beside every channel chart.
- [Running multi touch attribution for events on a single registration file](https://eventanalytics.ai/blog/multi-touch-attribution-for-events/): Multi touch attribution for events needs one touch table keyed to a person, then a weighting rule you can defend. Worked on one registration with six touches.
- [First touch versus last touch on a show that sells for nine months](https://eventanalytics.ai/blog/first-touch-versus-last-touch/): First touch versus last touch answers two different questions on one registration file. Run both, and send each ranking to the meeting it belongs in.
- [Why a time decay attribution model fits a deadline driven show](https://eventanalytics.ai/blog/time-decay-attribution-model/): A time decay attribution model weights touches by how close they sit to the registration. Pick the half life from your own data and the arithmetic is reproducible.
- [Markov chain attribution applied to a trade show registration journey](https://eventanalytics.ai/blog/markov-chain-attribution/): Markov chain attribution derives channel credit from the removal effect rather than a rule. Worked on four states with numbers you can rebuild in a spreadsheet.
- [Choosing an attribution window length for a show with a long buying cycle](https://eventanalytics.ai/blog/attribution-window-length/): Attribution window length decides which touches exist at all. Measure your own first touch distribution, set the window at the 90th percentile, and state what it discards.
- [Measuring paid search for trade shows beyond the platform conversion count](https://eventanalytics.ai/blog/paid-search-for-trade-shows/): Paid search for trade shows should be reported in three spend groups against registrations in the file, because brand, category and competitor terms behave nothing alike.
- [What paid social for event registrations actually delivers once you match the file](https://eventanalytics.ai/blog/paid-social-for-event-registrations/): Paid social for event registrations sells two products at two prices. Split prospecting from retargeting, then match every platform claim to the registration file.
- [Should view through conversions count towards your registration numbers](https://eventanalytics.ai/blog/view-through-conversions/): View through conversions credit a registration to an ad nobody clicked. Set a viewability floor, a short window, and a de duplication rule that puts clicks ahead of views.
- [Closing the platform reported conversions discrepancy against your registration file](https://eventanalytics.ai/blog/platform-reported-conversions-discrepancy/): The platform reported conversions discrepancy is four causes stacked on each other. Walk 1,480 claimed registrations down to 910 rows, one adjustment per line.
- [Retargeting abandoned registrations from the point the form was left](https://eventanalytics.ai/blog/retargeting-abandoned-registrations/): Retargeting abandoned registrations works when the audience is built from the last completed step and recovery is counted as completions inside seven days.

## Audience acquisition

Registration volume before the doors open. Pacing against prior editions, registration curves, deadline behaviour, no-show rates and the qualification questions that decide audience quality.

- [How to read registration pacing in the weeks before a show](https://eventanalytics.ai/blog/registration-pacing/): How to read registration pacing against days to show open rather than calendar date, calculate the index against a prior edition, and judge what it means.
- [The event registration s curve and what its shape tells you](https://eventanalytics.ai/blog/event-registration-s-curve/): An event registration s curve is closer to a flattened S than a line. Plot cumulative share of final registrations against days out to compare editions.
- [What a late registration surge does to your show planning](https://eventanalytics.ai/blog/late-registration-surge/): A late registration surge lands after the catering guarantee and the desk plan are signed. Work the final month week by week and forecast the tail instead.
- [Reading the registration plateau mid campaign before you spend more money](https://eventanalytics.ai/blog/registration-plateau-mid-campaign/): A registration plateau mid campaign is usually the pattern repeating. Check the window's slope against the same weeks in three prior editions before spending.
- [Running a year over year registration comparison that holds up](https://eventanalytics.ai/blog/year-over-year-registration-comparison/): A year over year registration comparison built on one headline delta cannot be acted on. Decompose the gap into returning, new, exhibitor staff and the rest.
- [How to handle a show date change registration comparison](https://eventanalytics.ai/blog/show-date-change-registration-comparison/): A show date change registration comparison run on calendar dates is meaningless. Rebase on days to show open, then check the campaign window's length.
- [Building a multi year registration baseline from five editions of history](https://eventanalytics.ai/blog/multi-year-registration-baseline/): Build a multi year registration baseline from five closed editions: the median cumulative share at each day out, plus the tenth and ninetieth percentiles.
- [Why registration snapshot history is the data you wish you kept](https://eventanalytics.ai/blog/registration-snapshot-history/): Registration snapshot history is what lets you pace against prior editions. Rebuild it approximately from created dates, then start a weekly snapshot job.
- [Building a registration forecast to show open your team will use](https://eventanalytics.ai/blog/registration-forecast-to-show-open/): A registration forecast to show open is one division: current registrations over the historic share held at this day out. Publish it as a range and backtest it.
- [Getting a final attendance forecast from registrations that survives show day](https://eventanalytics.ai/blog/final-attendance-forecast-from-registrations/): A final attendance forecast from registrations needs a turnout rate per registration type, since paid delegates and free expo visitors behave differently.
- [Registration target setting that survives contact with the show director](https://eventanalytics.ai/blog/registration-target-setting/): Registration target setting that survives the budget meeting: build the number from your own baseline band, split returning from new, then price the increment.
- [What the early bird registration deadline actually moves, and what it costs](https://eventanalytics.ai/blog/early-bird-registration-deadline/): How to measure what an early bird registration deadline really produces: separate the registrations it pulled forward from the ones it genuinely added.
- [Designing registration price increase tiers that pull the curve forward](https://eventanalytics.ai/blog/registration-price-increase-tiers/): How to design registration price increase tiers that actually move the curve: how many steps, how far apart, and the yield the ladder gives up to a flat price.
- [Measuring early bird cannibalization on your own registration file](https://eventanalytics.ai/blog/early-bird-cannibalization/): Measure early bird cannibalization on your own file: split the discount takers by what they did last edition, then price what the giveaway actually bought.
- [The real cost of a registration deadline extension nobody planned for](https://eventanalytics.ai/blog/registration-deadline-extension/): A registration deadline extension buys registrations this week and costs deadline response next edition. How to measure the bill and when extending is fair.
- [Paid versus free registration and what each one does to turnout](https://eventanalytics.ai/blog/paid-versus-free-registration/): Paid versus free registration moves turnout, qualification and cancellation in different directions. Compare the two on one edition without fooling yourself.
- [Writing a comp registration policy your finance lead can defend](https://eventanalytics.ai/blog/comp-registration-policy/): A comp registration policy your finance lead can defend: named entitlements with an owner, a cap and an expiry, plus a weekly line on comp share of the file.
- [Sizing exhibitor guest pass allotment so the codes get used](https://eventanalytics.ai/blog/exhibitor-guest-pass-allotment/): Exhibitor guest pass allotment sized against booth area puts the inventory where it is least likely to be used. Size against demonstrated redemption instead.
- [Spotting registration promo code abuse before it dents the paid mix](https://eventanalytics.ai/blog/registration-promo-code-abuse/): Three tests that catch registration promo code abuse before the badges print: redemptions against cap, concentration by email domain, and the shape of the tail.
- [Member versus non member registration pricing and what the gap buys you](https://eventanalytics.ai/blog/member-versus-non-member-registration/): Member versus non member registration pricing is sold two ways that need opposite measurements. Here is how to settle which one your gap is really doing.
- [Measuring trade show no show rate on a denominator you can defend](https://eventanalytics.ai/blog/trade-show-no-show-rate/): How to compute a trade show no show rate on a denominator you can defend, and why one file honestly produces 22, 28 or 34 per cent depending on the base.

## BI and reporting

Dashboard craft for event teams. Metric definition and naming, row-level security, self-service against curated reporting, embedding for exhibitors, and report adoption.

- [Show director dashboard design around three questions](https://eventanalytics.ai/blog/show-director-dashboard-design/): Show director dashboard design works when the front page answers only the three questions a director opens the report to ask, and the rest sits behind a tab.
- [Dashboard requirements gathering begins with a decision](https://eventanalytics.ai/blog/dashboard-requirements-gathering/): Dashboard requirements gathering that starts from the decision the reader has to make, using a one page brief naming audience, cadence and the measures.
- [Dashboard visual hierarchy decides what gets seen first](https://eventanalytics.ai/blog/dashboard-visual-hierarchy/): Dashboard visual hierarchy puts the number that triggers action top left and sizes it largest, using eyetracking evidence about where readers actually look.
- [How many KPI tiles a page can carry](https://eventanalytics.ai/blog/how-many-kpi-tiles/): How many KPI tiles a report page can carry before nobody reads any, worked as an attention budget in seconds and tested against a 22 tile page cut to six.
- [The pre show countdown dashboard for the final week](https://eventanalytics.ai/blog/pre-show-countdown-dashboard/): A pre show countdown dashboard that fits one screen in the final week, with six tiles, one filter, and a refresh cadence the platform can actually deliver.
- [Drill down path design that follows overview first](https://eventanalytics.ai/blog/drill-down-path-design/): Drill down path design for event reporting: one hierarchy per page, overview first then zoom and filter, and a breadcrumb that shows which filter is applied.
- [Drill through to record detail when a number is disputed](https://eventanalytics.ai/blog/drill-through-to-record-detail/): Drill through to record detail gives every headline number a path to the rows behind it, so a disputed count can be opened, filtered by source and checked.
- [Metric naming conventions that end the attendance argument](https://eventanalytics.ai/blog/metric-naming-conventions/): Metric naming conventions that carry the population, filter and window inside the measure name, so three different numbers called attendance stop colliding.
- [KPI tile labels that carry the filter and the window](https://eventanalytics.ai/blog/kpi-tile-labels/): KPI tile labels that state the population, the filter and the window under the number, so a figure quoted out of a report cannot be read two different ways.
- [Metric definitions in tooltips beside the number](https://eventanalytics.ai/blog/metric-definitions-in-tooltips/): Metric definitions in tooltips put population, filter, source and last change date beside the number, so nobody has to open a data dictionary to read a report.
- [Metric change control for the day a definition changes mid year](https://eventanalytics.ai/blog/metric-change-control/): Metric change control for event reporting: version the measure, keep the old definition live for one edition, and mark the changeover date on every chart.
- [Certified versus ad hoc reports and the badge that tells readers which](https://eventanalytics.ai/blog/certified-versus-ad-hoc-reports/): Certified versus ad hoc reports: two tiers, four entry criteria and a badge that tells a reader whether the number in front of them is the number of record.
- [Row level security for event portfolios where a director sees only their show](https://eventanalytics.ai/blog/row-level-security-for-event-portfolios/): Row level security for event portfolios: filter the show dimension once, let the fact tables inherit it, and understand why a contributor still sees every show.
- [Dynamic row level security mapping tables beat one static role per show](https://eventanalytics.ai/blog/dynamic-row-level-security-mapping/): Dynamic row level security mapping replaces one role per show with a user to show table, a single filter expression and access changes made by editing rows.
- [Testing row level security before one exhibitor can see another exhibitor data](https://eventanalytics.ai/blog/testing-row-level-security/): Testing row level security with a matrix of users, expected row counts and expected totals, run through an impersonating query API instead of by eye.
- [Workspace permissions for event teams that stop everybody becoming an admin](https://eventanalytics.ai/blog/workspace-permissions-for-event-teams/): Workspace permissions for event teams: four roles, consumers in an app audience, two admins, and a membership review timed to the close of each edition.
- [Sensitivity labels on event reports so exports carry their classification out](https://eventanalytics.ai/blog/sensitivity-labels-on-reports/): Sensitivity labels on reports travel with exports to Excel, PDF and PowerPoint, never to CSV, and inside the service they classify without restricting access.
- [Object level security when the row is fine but the column is not](https://eventanalytics.ai/blog/object-level-security/): Object level security hides a table or column outright, so the field leaves the field list entirely and any visual or measure that referenced it stops working.
- [Embedded analytics for exhibitors inside the portal they already log into](https://eventanalytics.ai/blog/embedded-analytics-for-exhibitors/): Embedded analytics for exhibitors puts one report definition inside the portal they already use, passing identity from the session so nobody signs in twice.
- [Multi tenant analytics isolation so one exhibitor never sees another set of rows](https://eventanalytics.ai/blog/multi-tenant-analytics-isolation/): Multi tenant analytics isolation: three patterns for exhibitor reporting, why the common one leaks, and where to put a tenant predicate so it cannot be missed.
- [Embedded report authentication tokens that never trust a client supplied id](https://eventanalytics.ai/blog/embedded-report-authentication-tokens/): Mint an embedded report authentication token on the server, carry the tenant claim inside it, and filter at the data layer so a rewritten URL returns nothing.

## Content and media

Editorial operations for event media brands. Repurposing show content, video and clipping, search visibility, visibility inside answer engines, and content performance.

- [How to run editorial operations across event brands without duplicating work](https://eventanalytics.ai/blog/editorial-operations-across-event-brands/): Editorial operations across event brands duplicate work invisibly. A commissioning ledger makes the repeat countable before anyone argues about headcount.
- [A content operations staffing model that survives eight shows a year](https://eventanalytics.ai/blog/content-operations-staffing-model/): A content operations staffing model works only if you staff the constraint. Count touches per published asset, find the queue, and stop hiring writers into it.
- [Syndicating articles between sibling brands without wrecking either one in search](https://eventanalytics.ai/blog/syndicating-articles-between-sibling-brands/): Syndicating articles between sibling brands splits one ranking three ways. Pick a canonical home, syndicate excerpts, and keep a register of what went where.
- [Building a year round content calendar around a show that happens once](https://eventanalytics.ai/blog/year-round-content-calendar/): A year round content calendar for an annual show works best anchored to the registration curve. Four phases, and a concentration figure you can measure this week.
- [Setting a publishing cadence between editions that keeps a show brand alive](https://eventanalytics.ai/blog/publishing-cadence-between-editions/): A publishing cadence between editions holds crawl frequency and reader habit through the quiet months. How to set the floor and read crawl stats to check it.
- [Choosing an evergreen and timely content mix for a seasonal event brand](https://eventanalytics.ai/blog/evergreen-and-timely-content-mix/): An evergreen and timely content mix decides how much of a show brand's traffic has to be re-earned every month. Score commissions on decay half life.
- [Turning session recordings into content assets your editorial team will actually use](https://eventanalytics.ai/blog/session-recordings-into-content-assets/): Turning session recordings into content assets needs a fixed extraction pass and an asset log keyed to the recording id, so reuse becomes a number you can read.
- [A conference transcript editing workflow that turns raw speech into publishable copy](https://eventanalytics.ai/blog/conference-transcript-editing-workflow/): A conference transcript editing workflow in three passes: attribution, filler removal and a check on figures quoted from stage, plus a vendor test.
- [Turning a panel into an article that reads better than the session](https://eventanalytics.ai/blog/turning-a-panel-into-an-article/): Turning a panel into an article works when the piece is built around the disagreement rather than the running order. The arithmetic and the speaker check.
- [Video clipping from session recordings without burning a week of editor time](https://eventanalytics.ai/blog/video-clipping-from-session-recordings/): Video clipping from session recordings costs editor hours in selection, not in editing. Write the selection rule first, then measure cost per published clip.
- [Getting speaker release and recording rights settled before you clip anything](https://eventanalytics.ai/blog/speaker-release-and-recording-rights/): A speaker release and recording rights form should name every downstream use. General permission to record settles almost nothing once clips and paid promotion start.
- [Producing vertical clips from conference footage shot for a wide stage](https://eventanalytics.ai/blog/vertical-clips-from-conference-footage/): Vertical clips from conference footage fail when the master was framed wide. Work the crop arithmetic, then price a tight second camera per delivered clip.
- [Content repurposing rules that stop a portfolio filling up with thin duplicates](https://eventanalytics.ai/blog/content-repurposing-rules/): Content repurposing rules should force a decision before publication: a reused asset earns a page only if it clears a written test, otherwise it gets a link.

## Data platform

Warehouses built for events. Star schemas, medallion layering, incremental loads, semantic layers, slowly changing dimensions, pipeline testing, orchestration and cost.

- [How to declare the event data warehouse grain before you build tables](https://eventanalytics.ai/blog/event-data-warehouse-grain/): Declaring the event data warehouse grain means saying what one fact row represents. One edition with three business processes needs three separate grain statements.
- [Atomic grain versus aggregates when storing badge scans and registrations](https://eventanalytics.ai/blog/atomic-grain-versus-aggregates/): Atomic grain versus aggregates decides which questions you can still answer in year three. Collapsing 38,900 scans to 1,096 summary rows loses repeat visits.
- [A fact table grain mismatch is why your two reports disagree](https://eventanalytics.ai/blog/fact-table-grain-mismatch/): A fact table grain mismatch inflates every sum. Joining 900 registrations to 3,400 scans returns 3,400 rows and reports registration revenue at 3.8 times its true value.
- [Designing the event and edition dimension for a show that repeats yearly](https://eventanalytics.ai/blog/event-and-edition-dimension-design/): Event and edition dimension design needs two keys: a durable event key for the show brand and a surrogate key per edition. Eight brands over five years is 40 rows.
- [Adding days to show open to your date dimension](https://eventanalytics.ai/blog/days-to-show-open/): Days to show open cannot be a column on a shared date dimension, because one calendar date holds a different offset for every edition running that season.
- [Modelling the venue and hall dimension when a show changes buildings](https://eventanalytics.ai/blog/venue-and-hall-dimension/): A venue and hall dimension has to hold two speeds: a building that changes every few years and a hall configuration that changes every edition.
- [Conformed dimensions across shows are what make a portfolio roll up work](https://eventanalytics.ai/blog/conformed-dimensions-across-shows/): Conformed dimensions across shows are the condition for a portfolio roll up. Two local code lists of 41 and 62 categories report 103 sectors where 74 exist.
- [Drawing an event bus matrix before you model a single fact table](https://eventanalytics.ai/blog/event-bus-matrix/): An event bus matrix puts business processes down the side and dimensions across the top. A 6 by 9 grid shows which dimensions to build before anything else.
- [An industry taxonomy mapping table beats forcing every show to renumber](https://eventanalytics.ai/blog/industry-taxonomy-mapping-table/): An industry taxonomy mapping table keeps each show's local code list and links it to a conformed master. 132 local values map to 28 master sectors with 9 unmapped.
- [A slowly changing company dimension for exhibitors that merge and rebrand](https://eventanalytics.ai/blog/slowly-changing-company-dimension/): A slowly changing company dimension keeps type 2 rows so a 2023 contract still reports under the exhibitor's 2023 name after the firm rebrands in 2024.
- [Choosing type 2 versus type 1 attributes on your contact dimension](https://eventanalytics.ai/blog/type-2-versus-type-1-attributes/): Type 2 versus type 1 attributes decides which contact columns keep history. Job title and employer need a new row. A corrected email should overwrite.
- [Using a mini dimension for contact attributes that change every edition](https://eventanalytics.ai/blog/mini-dimension-for-contact-attributes/): A mini dimension for contact attributes pulls volatile bands like seniority and buying role out of the contact dimension into one small profile table.
- [Badge scan fact table design that survives five editions of questions](https://eventanalytics.ai/blog/badge-scan-fact-table-design/): Badge scan fact table design is mostly a key list. Eight foreign keys, one degenerate scan identifier and no measure will answer questions nobody has asked yet.
- [A session attendance fact table needs both a scan and a capacity](https://eventanalytics.ai/blog/session-attendance-fact-table/): A session attendance fact table holds one row per entry and no measure. Room capacity belongs on the session dimension, so fill rate is computed at query time.
- [When a factless fact table gives you the coverage denominator](https://eventanalytics.ai/blog/factless-fact-table-coverage/): A factless fact table coverage row exists for every eligible pairing, so exhibitors nobody scanned and sessions nobody entered get a denominator.
- [Medallion architecture for event data and where the layers earn their keep](https://eventanalytics.ai/blog/medallion-architecture-for-event-data/): Medallion architecture for event data pays off unevenly: bronze earns its keep at the first edition, silver at the second show, gold at the roll-up.
- [Deciding bronze layer retention when a show runs once a year](https://eventanalytics.ai/blog/bronze-layer-retention/): Bronze layer retention for an annual show runs on two clocks: how many editions a comparison needs, and how long the personal data may lawfully be kept.
- [Designing burst shaped ingestion pipelines for a show that peaks in four days](https://eventanalytics.ai/blog/burst-shaped-ingestion-pipelines/): Burst shaped ingestion pipelines for an exhibition get sized from the busiest hour. 38,900 scans across 96 hours peaks near 2,400 an hour, a very small load.
- [Running an annual cadence data pipeline that sits idle for eleven months](https://eventanalytics.ai/blog/annual-cadence-data-pipeline/): An annual cadence data pipeline is broken by the time you need it. Credentials, runtimes and schemas expire on their own clocks. A rehearsal run finds it.
- [Idempotent warehouse loads mean you can rerun show day without fear](https://eventanalytics.ai/blog/idempotent-warehouse-loads/): Idempotent warehouse loads let you rerun a half finished show day job without thinking. Append semantics turn one interrupted run into 62,900 rows from 38,900.
- [Merge versus insert overwrite for loading a completed show edition](https://eventanalytics.ai/blog/merge-versus-insert-overwrite/): Merge versus insert overwrite decided on batch size: a 400 row correction and a 12,000 row re-extract into the same show edition want opposite loaders.

## Data quality

Quality as an operating discipline. Freshness and volume checks, schema drift, duplicate rates, stewardship queues, data contracts, ownership and quality SLAs.

- [The event data quality dimensions worth measuring on a registration file](https://eventanalytics.ai/blog/event-data-quality-dimensions/): The six event data quality dimensions only work on a registration file once each one is bound to a named field. Six numbers from one show, with the arithmetic.
- [Fitness for use data quality beats a generic accuracy target](https://eventanalytics.ai/blog/fitness-for-use-data-quality/): Fitness for use data quality rates one registration file separately for each thing you do with it, so the exhibitor report and the pacing model get different verdicts.
- [How to build a registration data quality score your team trusts](https://eventanalytics.ai/blog/registration-data-quality-score/): A registration data quality score is only trustworthy when the weights are published. A worked weighted average over four dimension pass rates, with the arithmetic.
- [Data profiling a registration file before you trust a single number](https://eventanalytics.ai/blog/data-profiling-a-registration-file/): Data profiling a registration file means five statistics per column before any dashboard is built. The top twenty values on job title is the one that changes plans.
- [Registration record completeness measured against what the post show report needs](https://eventanalytics.ai/blog/registration-record-completeness/): Registration record completeness measured against every form field gives a number nobody acts on. Measure against the fields your published outputs read instead.
- [Which registration fields actually matter to the reports you publish](https://eventanalytics.ai/blog/which-registration-fields-actually-matter/): To find which registration fields actually matter, count how many published outputs break without each one, then set targets only where that count reaches two.
- [Completeness rate by field turns a vague data problem into a queue](https://eventanalytics.ai/blog/completeness-rate-by-field/): The completeness rate by field is the share of records holding a non null and non placeholder value. Placeholder detection is what separates a real rate from a flattering one.
- [A weighted completeness score that reflects what each field is worth](https://eventanalytics.ai/blog/weighted-completeness-score/): A weighted completeness score rates each registration record by the value of the fields it holds, so a missing phone number stops costing as much as a missing company.
- [Job title normalisation when every attendee types their own title](https://eventanalytics.ai/blog/job-title-normalisation/): Job title normalisation in three passes: strip case and punctuation, apply a synonym map, then join to a taxonomy. Most of the collapse happens before any semantic work.
- [Deriving seniority level from job title text on a registration form](https://eventanalytics.ai/blog/seniority-level-from-job-title/): Deriving seniority level from job title text needs an ordered keyword ladder run highest first, an exclusion pass before it, and the unknown share published alongside.
- [Company name standardisation across registration and exhibitor systems](https://eventanalytics.ai/blog/company-name-standardisation/): Company name standardisation is the step before any cross system comparison: case, whitespace, legal suffixes from a published list, and the raw string kept.
- [Country field normalisation and the two letter codes that end the argument](https://eventanalytics.ai/blog/country-field-normalisation/): Country field normalisation maps UK, U.K., England and GB to one ISO 3166-1 alpha-2 code on ingest, keeps the original, and counts unmapped values as a metric.
- [State and province codes are the quiet failure in geographic reporting](https://eventanalytics.ai/blog/state-and-province-codes/): State and province codes collide across countries unless they carry a country prefix. Store ISO 3166-2 subdivision codes and validate the prefix against the country.
- [Postal code validation catches errors that country level checks never see](https://eventanalytics.ai/blog/postal-code-validation/): Postal code validation tests each postcode against a pattern chosen by country code, reports a pass rate per country, and turns a vague data problem into one form fix.
- [Data freshness monitoring for a business whose data arrives in bursts](https://eventanalytics.ai/blog/data-freshness-monitoring/): Data freshness monitoring on an events business needs a threshold that moves with the show calendar, because one fixed window pages you all summer for nothing.
- [Freshness checks for annual feeds when a source lands once a year](https://eventanalytics.ai/blog/freshness-checks-for-annual-feeds/): Freshness checks for annual feeds fail when built on hours. Replace the clock with the event calendar so the check asserts a file landed within days of show close.
- [Stale event data detection and the age at which a record misleads](https://eventanalytics.ai/blog/stale-event-data-detection/): Stale event data detection sets a maximum age per downstream use, not per table, then reports the share of records past it so a call list stops being built on 2019.
- [Data volume anomaly detection on a business with one peak a year](https://eventanalytics.ai/blog/data-volume-anomaly-detection/): Data volume anomaly detection on an events business builds its expected range from prior editions at the same number of days before show open, then alerts outside it.
- [Row count checks on seasonal data built from the prior year curve](https://eventanalytics.ai/blog/row-count-checks-on-seasonal-data/): Row count checks on seasonal data work once you decompose the series first: run STL on daily counts, keep the remainder, and put the control limit on that.
- [Zero row load detection when an empty file is sometimes correct](https://eventanalytics.ai/blog/zero-row-load-detection/): Zero row load detection needs a gate on the show calendar, because zero registrations 200 days out is fine and zero on the Tuesday of show week is an incident.
- [Schema drift detection for the exports you did not write and cannot control](https://eventanalytics.ai/blog/schema-drift-detection/): Schema drift detection on a registration export you do not control: hash the ordered column list and types on every load, and decide in advance what stops it.

## Event finance

Event P and L structure, revenue recognition, deferred revenue and cash timing, contribution analysis, organic growth definitions, budgeting and reforecasting a show.

- [How an event profit and loss structure is built line by line](https://eventanalytics.ai/blog/event-profit-and-loss-structure/): An event profit and loss structure has four blocks: revenue by line, direct show cost, sales and marketing, and allocated overhead. What each one does to the margin.
- [Splitting fixed versus variable event costs before the first budget review](https://eventanalytics.ai/blog/fixed-versus-variable-event-costs/): How to split fixed versus variable event costs by decision window, what a 10 per cent space shortfall really releases, and why step costs break the two-bucket model.
- [Allocating central overhead to shows without starting a war between show directors](https://eventanalytics.ai/blog/allocating-central-overhead-to-shows/): Allocating central overhead to shows changes who looks profitable. Three bases on one 8.4 million show, the ranking they invert, and the disclosure that ends the argument.
- [What belongs in space revenue versus service revenue when the accounts close](https://eventanalytics.ai/blog/space-revenue-versus-service-revenue/): Space revenue versus service revenue: what belongs in each line, why folding services into space overstates yield per square foot, and the test IFRS 15 actually applies.
- [Sponsorship revenue accounting when the package spans a year and one show week](https://eventanalytics.ai/blog/sponsorship-revenue-accounting/): Sponsorship revenue accounting for a package covering show week and a year of digital presence: splitting the price by standalone selling price and phasing each piece.
- [Delegate fee revenue recognition for a conference running alongside the exhibition](https://eventanalytics.ai/blog/delegate-fee-revenue-recognition/): Delegate fee revenue recognition for a conference alongside a trade show: when the fee is earned, how no-shows are treated, and what a conference straddling a year end does.
- [Gross versus net revenue presentation when the organiser resells stand build and housing](https://eventanalytics.ai/blog/gross-versus-net-revenue-presentation/): Gross versus net revenue presentation turns on control, not on who sends the invoice. A housing block worth 4 million shows as 600,000 or 4 million of revenue.
- [Venue cost in event budgets and the clauses that move it after signature](https://eventanalytics.ai/blog/venue-cost-in-event-budgets/): Venue cost in event budgets is a contracted hall hire plus a variable tail that bills on actuals. How to rate it per square foot and budget the part nobody signed for.
- [Capitalising sales commissions for events under the costs to obtain a contract rules](https://eventanalytics.ai/blog/capitalising-sales-commissions-for-events/): Capitalising sales commissions for events: what counts as an incremental cost of obtaining a contract, when the one year expedient applies, and what a December year end does.
- [Event staff cost allocation when one team runs six shows a year](https://eventanalytics.ai/blog/event-staff-cost-allocation/): Event staff cost allocation across six editions: four bases on one 650,000 payroll, the five point margin swing, and why timesheet percentages total 100.
- [The largest direct cost lines on a trade show and how they move](https://eventanalytics.ai/blog/largest-direct-cost-lines/): The largest direct cost lines on a trade show are floor build, venue, contracted operations and audiovisual. How to size each one and predict how it moves.
- [Contribution margin per square foot tells you which halls are worth opening](https://eventanalytics.ai/blog/contribution-margin-per-square-foot/): Contribution margin per square foot is space revenue less the direct cost that follows the floor, divided by net square feet sold. How to compute it by hall.
- [The event gross margin calculation that survives a first look from group finance](https://eventanalytics.ai/blog/event-gross-margin-calculation/): An event gross margin calculation needs a stated direct cost line. Worked on filed accounts and on a single show, with the two numbers a board confuses.
- [Finding the break even point for a show before the sales team commits](https://eventanalytics.ai/blog/break-even-point-for-a-show/): The break even point for a show is fixed cost divided by contribution per square foot. Worked with sensitivities, plus the commit date that matters more.
- [Point in time revenue recognition puts a whole show into one reporting period](https://eventanalytics.ai/blog/point-in-time-revenue-recognition/): Point in time revenue recognition puts a whole show into one period. What the standard requires, and what a single date change does to a half year.
- [Event phasing across reporting periods and why half year numbers mislead by design](https://eventanalytics.ai/blog/event-phasing-across-reporting-periods/): Event phasing across reporting periods makes flat years look like growth at the half. How listed groups reconcile it and what an organiser should publish.
- [Revenue cutoff for a show that opens on the last day of the quarter](https://eventanalytics.ai/blog/revenue-cutoff-for-a-show/): The revenue cutoff for a show straddling a quarter end turns on the IFRS 15 tests. A worked split on 9.3 million, and why a per day split misleads.
- [Deferred revenue for trade shows is the balance sheet line nobody reads carefully](https://eventanalytics.ai/blog/deferred-revenue-for-trade-shows/): Deferred revenue for trade shows holds every booth, badge and sponsorship invoiced before doors open. What moves the balance, and what it cannot tell you.
- [The cash profile of an annual show peaks months before the revenue does](https://eventanalytics.ai/blog/cash-profile-of-an-annual-show/): The cash profile of an annual show peaks before doors open and settles after breakdown. A month by month curve on one edition, and where the peak misleads.
- [Why a growing event business runs on negative working capital and what breaks it](https://eventanalytics.ai/blog/negative-working-capital-event-business/): A growing event business runs on negative working capital because deferred revenue funds it. What two filed balance sheets show, and what a flat year costs.
- [Forward bookings as a metric only works if the comparison date is fixed](https://eventanalytics.ai/blog/forward-bookings-as-a-metric/): Forward bookings as a metric only compares if both figures are struck the same number of days before doors open and the basis is written down first.

## Exhibitor performance

Lead capture through to pipeline. Scan data models, lead grading, per exhibitor scorecards, benchmarking inside a show, and reporting an exhibitor will actually open.

- [What a lead retrieval data model must hold before reporting works](https://eventanalytics.ai/blog/lead-retrieval-data-model/): A lead retrieval data model that never declares its grain gives one stand three different lead counts. Model every scan as an event row and they reconcile.
- [Badge scan timestamps tell you more about a stand than the lead count](https://eventanalytics.ai/blog/badge-scan-timestamps/): Badge scan timestamps expose how a stand was really staffed. Bucket captures into fifteen minute bins, divide active bins by open bins, and read the coverage.
- [Lead capture coverage rate shows how many exhibitors captured nothing at all](https://eventanalytics.ai/blog/lead-capture-coverage-rate/): Lead capture coverage rate counts the exhibitors who captured nothing. With 640 exhibitors and 470 scanning, coverage is 73.4 per cent and 170 stands are blank.
- [The exhibitor lead export fields that decide whether follow up ever happens](https://eventanalytics.ai/blog/exhibitor-lead-export-fields/): Exhibitor lead export fields decide whether follow up happens: capture time, scanning user, a real consent flag and the qualifier answers behind them.
- [Lead retrieval scanner activation is the gap between ordering and actually scanning](https://eventanalytics.ai/blog/lead-retrieval-scanner-activation/): Lead retrieval scanner activation counts the licences that produced a real scan. If 380 go out and 291 get used, activation is 76.6 per cent and 89 sit dark.
- [Lead quality grading only works when the organiser defines the grades first](https://eventanalytics.ai/blog/lead-quality-grading/): Lead quality grading collapses when every stand invents its own scale. Publish four axes scored zero to three and let each exhibitor set their own cut point.
- [Where to set lead grade thresholds so an A actually means something](https://eventanalytics.ai/blog/lead-grade-thresholds/): Lead grade thresholds set by feel produce shows where most leads come back grade A. Plot the score distribution first, then set the cut with a named panel.
- [Agreeing one qualified lead definition for exhibitors across an entire show](https://eventanalytics.ai/blog/qualified-lead-definition-for-exhibitors/): A qualified lead definition for exhibitors has to come from the show: a capture, one qualifier answer and a recorded next step, with both counts reported.
- [Building a trade show lead scoring model an organiser can defend to exhibitors](https://eventanalytics.ai/blog/trade-show-lead-scoring-model/): A trade show lead scoring model an organiser publishes has to be arguable. Use four stated inputs and render the sub-scores beside the total, then band it.
- [Unique visitors versus total scans and why the two numbers keep diverging](https://eventanalytics.ai/blog/unique-visitors-versus-total-scans/): Unique visitors versus total scans: one counts people, the other counts events. A stand with 1,410 scans and 980 distinct badges runs at a ratio of 1.44.
- [How to handle duplicate badge scans without deleting real second conversations](https://eventanalytics.ai/blog/duplicate-badge-scans/): Duplicate badge scans are not all errors. A windowed rule on exhibitor, badge, device and show day drops retries and keeps the genuine second conversations.
- [The scan to unique lead ratio and what a healthy number looks like](https://eventanalytics.ai/blog/scan-to-unique-lead-ratio/): The scan to unique lead ratio is one division per exhibitor. Around 1.0 means single pass capture, above 1.6 usually means a kiosk or a re-scanning stand.
- [Repeat visitor scans across a show floor and what they say about intent](https://eventanalytics.ai/blog/repeat-visitor-scans/): Repeat visitor scans are only evidence of intent when counted by distinct scan day and divided by the visitors who were actually on site to return.
- [Scan to pipeline attribution for exhibitors without pretending the show closed the deal](https://eventanalytics.ai/blog/scan-to-pipeline-attribution/): Scan to pipeline attribution is a two hop join with a loss at each hop. Report the CRM match rate on the same line as the influenced pipeline figure.
- [Choosing an exhibitor attribution window that matches the real sales cycle](https://eventanalytics.ai/blog/exhibitor-attribution-window/): Set the exhibitor attribution window at 1.5 to 2 times the median sales cycle, so a 120 day cycle reports at 180 to 240 days instead of the usual 30.
- [Matching booth scans to CRM records when email is the only usable key](https://eventanalytics.ai/blog/matching-booth-scans-to-crm/): Matching booth scans to CRM records on email alone tops out near 62 per cent. Add a domain plus surname tier and a phone tier, and report each one separately.
- [Reporting closed won revenue from scans without overclaiming what the show did](https://eventanalytics.ai/blog/closed-won-revenue-from-scans/): Reporting closed won revenue from scans needs a written rule and a published range, because the attribution model alone can move the figure three to one.
- [Exhibitor pipeline reporting lag and how to report before the deals close](https://eventanalytics.ai/blog/exhibitor-pipeline-reporting-lag/): Exhibitor pipeline reporting lag puts your rebooking deadline months ahead of the evidence. Publish a staged report at day 7, day 30 and day 180 instead.
- [The exhibitor scorecard metrics worth putting in front of a stand manager](https://eventanalytics.ai/blog/exhibitor-scorecard-metrics/): Exhibitor scorecard metrics an organiser can actually measure: unique leads, total scans, grade mix, active scanners, category percentile and prior edition.
- [Calculating cost per lead for exhibitors when you only know part of the cost](https://eventanalytics.ai/blog/cost-per-lead-for-exhibitors/): An organiser can compute cost per lead for exhibitors only on space and services it billed. Label it that way, publish the rule, and say what it misses.

## Forecasting methods

Forecasting registration, attendance, revenue and space. Curve fitting, sparse series, cold start for a new event, hierarchical forecasts, prediction intervals and backtesting.

- [How the additive pickup model forecasts your final registration number](https://eventanalytics.ai/blog/additive-pickup-model/): The additive pickup model adds an average historical increment to the registrations in hand. The arithmetic, the spread around it, and the two ways it breaks.
- [The multiplicative pickup model scales your count by a historical ratio](https://eventanalytics.ai/blog/multiplicative-pickup-model/): The multiplicative pickup model divides the registrations in hand by a historical share of final. Worked on a growing show, with the horizon where it inflates.
- [Pickup model diagnostics that tell you which form to trust this year](https://eventanalytics.ai/blog/pickup-model-diagnostics/): Pickup model diagnostics settle the additive versus multiplicative argument with residuals from your own closed editions instead of an opinion in the meeting.
- [Fitting a booking curve to five editions with a three parameter logistic](https://eventanalytics.ai/blog/fitting-a-booking-curve/): Fitting a booking curve with a three parameter logistic: borrow the midpoint and steepness from closed editions, then solve the asymptote from the live one.
- [Monotone regression splines keep a cumulative registration curve from going backwards](https://eventanalytics.ai/blog/monotone-regression-splines/): Cumulative registrations never fall, so a smoother that dips is wrong. Monotone regression splines and the PAVA pass impose the constraint before you forecast.
- [Penalised spline forecasting for pacing curves that only have five editions behind them](https://eventanalytics.ai/blog/penalised-spline-forecasting/): Penalised spline forecasting puts many knots along the days-to-open axis and lets one penalty do the work. How to pick that penalty when you have five editions.
- [Booking curve principal components compress a decade of editions into two numbers](https://eventanalytics.ai/blog/booking-curve-principal-components/): Booking curve principal components turn each edition into two scores. What the components mean, how to fit them, and where the level has to come from.
- [The Gompertz growth curve fits a registration campaign the logistic cannot](https://eventanalytics.ai/blog/gompertz-growth-curve/): The Gompertz growth curve puts its inflection at 37 per cent of the asymptote instead of 50, which is why it fits an asymmetric registration campaign.
- [Days to open as the axis when a show moves in the calendar](https://eventanalytics.ai/blog/days-to-open-axis/): A days to open axis re-indexes every edition so day zero is show open, which lets a show that moved from March to June be compared with its own history.
- [Aligning booking windows when one edition opened registration eleven weeks late](https://eventanalytics.ai/blog/aligning-booking-windows/): Aligning booking windows when editions had different runways: rescale to fraction of window elapsed, or truncate, and the halfway test that decides which.
- [Forecasting with five observations and the parameter budget that leaves you](https://eventanalytics.ai/blog/forecasting-with-five-observations/): Forecasting with five observations is a budgeting problem. Count what each method wants to estimate, then pick the one your five editions can actually pay for.
- [Overfitting short time series is easy when every model fits five points](https://eventanalytics.ai/blog/overfitting-short-time-series/): Overfitting short time series is the default with five editions. A quadratic explains 98 per cent of the variation and invents 4,600 registrations of growth.
- [A shrinkage estimator pulls one noisy show forecast toward the portfolio mean](https://eventanalytics.ai/blog/shrinkage-estimator/): A shrinkage estimator moves one show's 22 per cent growth toward the portfolio's 6 per cent. The weight is between-show variance over total variance, here 0.40.
- [Borrowing strength across shows when no single show has enough history](https://eventanalytics.ai/blog/borrowing-strength-across-shows/): Borrowing strength across shows gives each show its own pooling weight. A three edition show keeps 43 per cent of its own curve, a twelve edition show 75.
- [A global forecasting model trained on every show in the portfolio at once](https://eventanalytics.ai/blog/global-forecasting-model/): A global forecasting model fits one function across every show. The budget that buys three weeks of memory locally buys twenty four globally.
- [Pooled panel regression turns eight shows and five years into forty rows](https://eventanalytics.ai/blog/pooled-panel-regression/): Pooled panel regression stacks eight shows and five years into forty rows. Show and year effects cost twelve of them before a single covariate is estimated.
- [Hierarchical forecast reconciliation makes show and portfolio numbers add up](https://eventanalytics.ai/blog/hierarchical-forecast-reconciliation/): Hierarchical forecast reconciliation projects base forecasts onto the coherent space, so a 500 registration gap between show sum and portfolio total disappears.
- [Bottom up versus top down forecasting for a portfolio of eight shows](https://eventanalytics.ai/blog/bottom-up-versus-top-down/): Bottom up versus top down decides which level you trust. On a show whose share drifted from 3.1 to 7.1 per cent, static proportions come out 36 per cent low.
- [Temporal hierarchy forecasting reconciles the weekly pace with the annual number](https://eventanalytics.ai/blog/temporal-hierarchy-forecasting/): Temporal hierarchy forecasting aggregates one series to several frequencies, forecasts each, then reconciles. A 710 registration disagreement settles at 14,370.
- [Prediction interval coverage is worse than the label claims with five editions](https://eventanalytics.ai/blog/prediction-interval-coverage/): Prediction interval coverage on five editions is nothing like 95 per cent. The correct interval on this worked example is 2.35 times as wide as published.

## Identity resolution

One record per person across editions. Blocking, similarity measures, deterministic and probabilistic matching, survivorship, golden records, merges and unmerges.

- [Cross event attendee matching, and why one buyer becomes four records](https://eventanalytics.ai/blog/cross-event-attendee-matching/): Cross event attendee matching explained: why exact email matching undercounts repeat buyers, and how the Fellegi-Sunter model weighs evidence instead.
- [Duplicate attendee records across shows and the six stage fix for them](https://eventanalytics.ai/blog/duplicate-attendee-records-across-shows/): Duplicate attendee records across shows survive every dedupe you have run. Trace one buyer through ingest, blocking, scoring, decision, survivorship and golden record.
- [One person many email addresses and why exact match joins lose her](https://eventanalytics.ai/blog/one-person-many-email-addresses/): When one person has many email addresses, an exact match join links none of them. Here is what agreement counting across surname, mobile and employer recovers instead.
- [Deterministic matching rules and the exact point where they stop working](https://eventanalytics.ai/blog/deterministic-matching-rules/): Deterministic matching rules fire on equality after normalisation. Measure a three tier cascade on 100 labelled pairs and you can see the tier where precision breaks.
- [Probabilistic record linkage when your registration files share no common key](https://eventanalytics.ai/blog/probabilistic-record-linkage/): Probabilistic record linkage scores partial agreement across several weak fields when no shared key exists, then ranks every candidate pair by its total weight in bits.
- [Fellegi Sunter model, applied to a five year registration archive](https://eventanalytics.ai/blog/fellegi-sunter-model/): The Fellegi Sunter model splits candidate pairs into link, non link and a middle region for review. Worked on two registration records across four fields, with both cut offs.
- [Match weight calculation from m and u probabilities on badge scan data](https://eventanalytics.ai/blog/match-weight-calculation/): Match weight calculation turns m and u probabilities into bits of evidence per field. Worked on badge scan data, where an email agreement is worth 9.8 bits and a surname less.
- [The conditional independence assumption and where event data quietly violates it](https://eventanalytics.ai/blog/conditional-independence-assumption/): The conditional independence assumption lets match weights be added across fields. Employer name and work email domain break it, and the double counting is worth four bits.
- [Blocking for entity resolution before the pair count runs to billions](https://eventanalytics.ai/blog/blocking-for-entity-resolution/): Blocking for entity resolution cuts 88 billion candidate pairs to 50 million, and ten oversized blocks produce most of what is left. Here is the arithmetic and the cost.
- [Blocking key design that protects recall without exploding the comparison count](https://eventanalytics.ai/blog/blocking-key-design/): Blocking key design is a trade between pair completeness and reduction ratio. Measure both on 500 labelled pairs, then price each extra pass by the comparisons it costs.
- [The sorted neighbourhood method for matching exhibitor contact lists year to year](https://eventanalytics.ai/blog/sorted-neighbourhood-method/): The sorted neighbourhood method sorts records on a composite key and compares inside a sliding window, cutting 1.25 billion exhibitor pairs to 450,000 in one pass.
- [Candidate pair generation and the recall you give away before scoring starts](https://eventanalytics.ai/blog/candidate-pair-generation/): Candidate pair generation sets a hard ceiling on match recall, because any true pair it discards can never be scored. How to measure that ceiling and raise it.
- [Jaro Winkler similarity and why it favours the first four characters](https://eventanalytics.ai/blog/jaro-winkler-similarity/): Jaro Winkler similarity explained by hand on two badge names, including the prefix bonus, the transposition rule, and the fields where the bonus misleads you.
- [Jaccard token overlap for company names on an exhibitor directory](https://eventanalytics.ai/blog/jaccard-token-overlap/): Jaccard token overlap scores company names by shared words instead of shared characters, which is why it handles a missing word on an exhibitor directory better.
- [Levenshtein distance for names and where it misleads on short surnames](https://eventanalytics.ai/blog/levenshtein-distance-for-names/): Levenshtein distance for names counts insertions, deletions and substitutions, and a fixed threshold of 2 merges half the four letter surnames in your file.
- [Phonetic name matching with Soundex and Metaphone on international attendee lists](https://eventanalytics.ai/blog/phonetic-name-matching/): Phonetic name matching with Soundex and Metaphone recovers variant spellings on an international attendee list, and the false pairs it creates are countable.
- [Choosing a string similarity measure for each field on a registration record](https://eventanalytics.ai/blog/choosing-a-string-similarity-measure/): Choosing a string similarity measure works field by field: the failure mode of a forename differs from a company name, so one function everywhere loses on both.
- [Company name normalisation before you compare a single exhibitor record](https://eventanalytics.ai/blog/company-name-normalisation/): Company name normalisation is its own pipeline stage: case, punctuation, accents and ampersands are resolved before any similarity measure gets to see the name.
- [Legal entity suffixes and the exhibitor records they split in two](https://eventanalytics.ai/blog/legal-entity-suffixes/): Legal entity suffixes split one exhibitor into two accounts. Strip them before comparison, then keep the stripped form as a jurisdiction signal a reviewer can use.
- [Parent and subsidiary matching when one exhibitor books under four legal names](https://eventanalytics.ai/blog/parent-and-subsidiary-matching/): Parent and subsidiary matching keeps four contracting entities separate while rolling booth spend up to one group, using an edge instead of a merge.

## Integrations

Named systems and how their data behaves. Registration platforms, lead retrieval, floorplan tools, CRM, ERP, exhibitor portals, and the export you will want on the way out.

- [How to plan a Cvent data export you can actually reuse](https://eventanalytics.ai/blog/cvent-data-export/): A Cvent data export is only reusable if registration type, source code and cancellation status survive the crossing. How to plan one before you pull it.
- [Reading the Swapcard API rate limits before you build the nightly pull](https://eventanalytics.ai/blog/swapcard-api-rate-limits/): The Swapcard API rate limits are priced in points, not requests, so a nightly attendee pull has to be costed field by field before you write the loop.
- [Loading MYS exhibitor data without losing the booth link](https://eventanalytics.ai/blog/map-your-show-exhibitor-data/): Map Your Show exhibitor data loads cleanly and the booth link does not. Model the exhibitor key and the booth key separately before the join is written.
- [Planning an a2z Events data export across several shows and years](https://eventanalytics.ai/blog/a2z-events-data-export/): An a2z Events data export across several editions is mostly a booth numbering problem. Separate a renumbered hall from an exhibitor who genuinely moved.
- [What the ExpoFP floorplan API gives you and what it does not](https://eventanalytics.ai/blog/expofp-floorplan-api/): The ExpoFP floorplan API sends exhibitors, booths and extras into a plan. Treat it as a geometry source and keep the exhibitor master somewhere else.
- [Sizing an event data sync against Salesforce API limits](https://eventanalytics.ai/blog/salesforce-api-limits/): Salesforce API limits are a 24 hour allowance plus a licence multiplier. Size a registration sync against both before you write one call per record.
- [Working inside HubSpot API rate limits when a registration file lands](https://eventanalytics.ai/blog/hubspot-api-rate-limits/): HubSpot API rate limits set a burst ceiling per ten seconds and a daily cap per account. Size a 30,000 contact registration upload against both of them.
- [Handling Dynamics 365 API throttling during a show week data load](https://eventanalytics.ai/blog/dynamics-365-api-throttling/): Dynamics 365 API throttling is enforced per user over a five minute window, so one integration account becomes the ceiling on your busiest scanning minute.
- [Questions to settle before a Marketo event integration goes live](https://eventanalytics.ai/blog/marketo-event-integration/): A Marketo event integration lives inside a daily call quota, a twenty second rate limit and a concurrency ceiling. Time one 5,000 lead push before scheduling.
- [Pulling Stova registration data into a portfolio level report](https://eventanalytics.ai/blog/stova-registration-data/): Stova registration data rolls up across a portfolio only if registration type means the same thing in every show. Count the near duplicates before you build.
- [What a Grip matchmaking export tells you about meeting demand](https://eventanalytics.ai/blog/grip-matchmaking-export/): A Grip matchmaking export mixes requests, acceptances and held meetings in one table, and the permission settings decide who could be recommended at all.
- [Using the Brella REST API to pull meeting and lead data](https://eventanalytics.ai/blog/brella-rest-api/): A Brella REST API pull can carry meeting ratings as well as bookings, which is the one field that says something about quality rather than volume.
- [Mapping an ExpoPlatform data export onto your own event schema](https://eventanalytics.ai/blog/expoplatform-data-export/): An ExpoPlatform data export arrives with one identifier space across modules, which helps until you ask which of those identifiers survives the next edition.
- [Joining onPeak housing data to the registration file](https://eventanalytics.ai/blog/onpeak-housing-data/): Joining onPeak housing data to the registration file usually falls back to email, and email drops the guests whose rooms were booked by somebody else.
- [Cvent Passkey reservation data and what to settle before you model room blocks](https://eventanalytics.ai/blog/cvent-passkey-reservation-data/): Cvent Passkey reservation data supports several different pickup numbers, and the one your report shows is rarely the one the hotel invoice was computed from.
- [Getting GES exhibitor ordering data out and lined up with your booth list](https://eventanalytics.ai/blog/ges-exhibitor-ordering-data/): GES exhibitor ordering data is keyed on the contractor's own account number, so matching it to your booth list by company name leaves a fifth unattributed.
- [What a Zuant lead capture export looks like when it reaches the CRM](https://eventanalytics.ai/blog/zuant-lead-capture-export/): A Zuant lead capture export passes a filter and release step before the CRM sees it, and that is where organiser and exhibitor lead counts diverge.
- [Syncing an association management system with the show registration platform](https://eventanalytics.ai/blog/association-management-system-sync/): An association management system sync copies a membership status that is effective dated, into a registration platform that stores it as a flag with no date.
- [Choosing webhooks versus polling for an event registration feed](https://eventanalytics.ai/blog/webhooks-versus-polling/): Webhooks versus polling is a latency decision rather than a completeness one, and an event registration feed usually needs both running side by side.
- [Making an SFTP file drop integration survive a badly timed upload](https://eventanalytics.ai/blog/sftp-file-drop-integration/): An SFTP file drop integration fails silently when the loader reads a file mid write, and the fix is atomic delivery plus a manifest carrying row counts.

## Matchmaking

Buyer and seller matching. Fit scoring, hosted buyer programmes, scheduling under constraints, no-shows and cancellations, connection density, and meeting quality afterwards.

- [What a buyer seller fit score should actually contain](https://eventanalytics.ai/blog/buyer-seller-fit-score/): A buyer seller fit score needs five bounded sub-scores covering product, industry, intent, authority and behaviour, scored in both directions before weighting.
- [How to decide on weighting a match score you can defend](https://eventanalytics.ai/blog/weighting-a-match-score/): Weighting a match score is a policy choice, so test candidate weights against held out accepted meetings, report precision at five, and publish the numbers.
- [Match score calibration and why raw scores mislead your concierge team](https://eventanalytics.ai/blog/match-score-calibration/): Match score calibration checks whether a 0.72 proposal really gets accepted 72 per cent of the time, using decile buckets and an isotonic correction.
- [Explaining a match recommendation so the buyer trusts the meeting proposal](https://eventanalytics.ai/blog/explaining-a-match-recommendation/): Explaining a match recommendation works when the sentence comes from the same weighted contributions that produced the ranking, so it cannot drift from it.
- [Match reason codes give your team something to argue with](https://eventanalytics.ai/blog/match-reason-codes/): Match reason codes replace free text with a short controlled list you can count, so acceptance by lead reason becomes a number your team can argue with.
- [Showing sub scores to exhibitors without handing them a cheat sheet](https://eventanalytics.ai/blog/showing-sub-scores-to-exhibitors/): Showing sub scores to exhibitors invites gaming, so publish coarse bands on a fixed refresh cadence and hold the behaviour term back from the exhibitor view.
- [Building an exhibitor product taxonomy that a matching engine can use](https://eventanalytics.ai/blog/exhibitor-product-taxonomy/): An exhibitor product taxonomy decides what a matching engine can see, so size the tree from your own floor and count the exhibitors landing in a catch all node.
- [Product category mapping from free text exhibitor profiles](https://eventanalytics.ai/blog/product-category-mapping/): Product category mapping turns free text exhibitor profiles into taxonomy leaves using tf-idf cosine similarity, an auto assign threshold and a review queue.
- [Taxonomy granularity for matching and the cost of going too deep](https://eventanalytics.ai/blog/taxonomy-granularity-for-matching/): Taxonomy granularity for matching trades precision against pool size, so score the same buyer at three depths and count how many candidates each one leaves.
- [Buyer interest capture at registration without adding twelve more questions](https://eventanalytics.ai/blog/buyer-interest-capture/): Buyer interest capture costs registration completions, so test a short picker against a long one and count the completions lost and the categories gained.
- [Intent signals for matchmaking and which ones are worth scoring](https://eventanalytics.ai/blog/intent-signals-for-matchmaking/): Rank candidate intent signals for matchmaking by acceptance lift against the base rate, then check coverage and the error band before either one earns a weight.
- [First party intent at events and where the signal comes from](https://eventanalytics.ai/blog/first-party-intent-at-events/): First party intent at events already sits in registration, agenda and prior edition data. Here is which table each signal comes from and how to turn it into a score.
- [Treating meeting requests as intent and what that does to scores](https://eventanalytics.ai/blog/meeting-requests-as-intent/): Meeting requests as intent are the loudest signal in the building and the easiest to double count. Cap the contribution, then measure the feedback loop they create.
- [Buyer authority scoring when nobody fills in the budget field](https://eventanalytics.ai/blog/buyer-authority-scoring/): Buyer authority scoring has to run on purchasing role, company size band and hosted buyer status, because the budget question on your registration form is mostly empty.
- [Job title seniority parsing for a global exhibitor and visitor file](https://eventanalytics.ai/blog/job-title-seniority-parsing/): Job title seniority parsing is a data job before it is a modelling job. Build a rules first mapper onto five levels, then measure it against 500 hand labelled titles.
- [The buying committee at trade shows rarely arrives on one badge](https://eventanalytics.ai/blog/buying-committee-at-trade-shows/): The buying committee at trade shows sends one person and keeps four at the office. Score the account beside the badge, and count each account once however many badges it has.
- [Cold start matchmaking at a first edition with no behavioural history](https://eventanalytics.ai/blog/cold-start-matchmaking-first-edition/): Cold start matchmaking at a first edition has no accepted meetings to learn from. Hold intent and behaviour neutral, renormalise the weights, and instrument the show.
- [Onboarding questions for matchmaking that people will actually answer](https://eventanalytics.ai/blog/onboarding-questions-for-matchmaking/): Onboarding questions for matchmaking trade signal against drop off. Run the trade as an experiment and judge it on matched buyers per arrival.
- [Borrowing priors from a sister event to seed a new one](https://eventanalytics.ai/blog/priors-from-a-sister-event/): Priors from a sister event let a new show start with category level acceptance rates, blended by a shrinkage factor so local data takes over as it arrives.
- [Meeting scheduling as an assignment problem your team can inspect](https://eventanalytics.ai/blog/meeting-scheduling-assignment-problem/): Meeting scheduling is an assignment problem with side constraints. Write the objective and the constraints down, then pick a solver and make every rejection explainable.

## On-site analytics

What the floor tells you while it is open. Badge scans and access control, session fill, dwell, aisle traffic, the limits of each sensing method, and show-day anomalies.

- [The types of badge scans at a show and what each one proves](https://eventanalytics.ai/blog/types-of-badge-scans/): The types of badge scans at a show are entry, session, lead and deny. Each proves a different fact, so fix the taxonomy before anybody adds them up.
- [How exhibition access control data should feed show day operations](https://eventanalytics.ai/blog/exhibition-access-control-data/): Exhibition access control data records grants, denies and door-held events. Reading the deny reasons on show morning is what turns the feed into operations.
- [An entry scan deduplication rule that survives a busy hall door](https://eventanalytics.ai/blog/entry-scan-deduplication/): An entry scan deduplication rule needs two windows: a short debounce per badge per reader, then a session window per person per day. Here is how to size both.
- [What RFID badge tracking at exhibitions actually measures and what it misses](https://eventanalytics.ai/blog/rfid-badge-tracking-exhibitions/): RFID badge tracking at exhibitions records portal crossings, never a continuous path. Read rate compounds across a journey, and here is the arithmetic that shows it.
- [How NFC badge scanning throughput changes a door under load](https://eventanalytics.ai/blog/nfc-badge-scanning-throughput/): NFC badge scanning throughput depends on full service time at the lane, from badge presentation to gate release. Measure that, then divide lanes by the mean.
- [Gate coverage for attendance counting and the doors everyone forgets](https://eventanalytics.ai/blog/gate-coverage-for-attendance-counting/): Gate coverage for attendance counting starts with a door inventory. Classify every door as counted, sampled or uncounted, then publish the band that follows.
- [Building the show day arrival curve that tells you when to staff the doors](https://eventanalytics.ai/blog/show-day-arrival-curve/): A show day arrival curve is built from 15 minute bins per door. Peak to mean drives door staffing far harder than the daily attendance total does.
- [Testing entrance counting accuracy against a manual clicker count](https://eventanalytics.ai/blog/entrance-counting-accuracy/): Entrance counting accuracy is measured by running a manual clicker count beside the sensor, then plotting the difference against the mean for each bin.
- [Attendee reentry tracking without inflating the daily attendance number](https://eventanalytics.ai/blog/attendee-reentry-tracking/): Attendee reentry tracking separates a return from a fresh arrival. Without exit reads you need a minimum gap rule, and the gap you pick moves the headline.
- [Dwell time measurement on a show floor and what each method assumes](https://eventanalytics.ai/blog/dwell-time-measurement/): Dwell time measurement gives different answers by method. Portal dwell counts time inside a boundary and proximity dwell counts time inside a moving radius.
- [Turning aisle traffic density into a number your operations team can act on](https://eventanalytics.ai/blog/aisle-traffic-density/): Aisle traffic density turns a headcount into persons per square metre over walkable area, which is the form an operations lead can grade and act on in minutes.
- [Reading show floor traffic patterns from door scans and zone counts](https://eventanalytics.ai/blog/show-floor-traffic-patterns/): Show floor traffic patterns become useful once you split hourly zone counts into a daily profile, a day effect and a residual, then read each part separately.
- [Analysing attendee movement paths as ordered sequences of zones](https://eventanalytics.ai/blog/attendee-movement-paths/): Attendee movement paths become analysable when each route is reduced to an ordered list of zones and counted in a transition matrix, which survives sensor noise.
- [Calculating peak show floor occupancy from entry and exit scans](https://eventanalytics.ai/blog/peak-show-floor-occupancy/): Peak show floor occupancy is a cumulative sum of entries minus exits that drifts upward when exit reads are missed, so it needs a reconciliation before anyone quotes it.
- [Show floor heat mapping that an operations lead can defend in a debrief](https://eventanalytics.ai/blog/show-floor-heat-mapping/): Show floor heat mapping is a spatial histogram, so bin size, grid origin, colour scale and time window decide what the picture shows before any attendee does.
- [Finding dead zones on a show floor before the exhibitors in them complain](https://eventanalytics.ai/blog/dead-zones-on-show-floor/): Dead zones on a show floor show up when you rank aisle segments by traffic per linear metre of frontage against the hall median, then test what caused it.
- [Why heat map normalization changes which part of the hall looks busy](https://eventanalytics.ai/blog/heat-map-normalization/): Heat map normalization divides zone counts by area and by open minutes, and doing it usually reverses which part of an exhibition hall looks busiest.
- [What BLE beacon tracking accuracy means on a crowded exhibition floor](https://eventanalytics.ai/blog/ble-beacon-tracking-accuracy/): BLE beacon tracking accuracy is set by a noisy signal strength to distance conversion, so a few decibels of error moves an attendee across a stand boundary.
- [Where lidar people counting accuracy holds up and where crowds break it](https://eventanalytics.ai/blog/lidar-people-counting-accuracy/): Lidar people counting accuracy is quoted per crossing at a doorway, and that figure hides where the misses land, which is the busiest ninety minutes of the day.
- [Computer vision people counting on a show floor and its failure modes](https://eventanalytics.ai/blog/computer-vision-people-counting/): Computer vision people counting reports a number without naming anyone, and the benchmark error that comes with it is quoted on crowds unlike any exhibition hall.

## Onboarding operations

The exhibitor back office. Contracting, certificates of insurance, tax forms, service orders, manuals and deadlines, document extraction, and the touch count per exhibitor.

- [Where the exhibitor onboarding process stalls between signed contract and move in](https://eventanalytics.ai/blog/exhibitor-onboarding-process/): Model the exhibitor onboarding process as dated states, measure median days resident in each one, and the stall becomes visible months before move-in.
- [Defining exhibitor onboarding funnel stages so drop off is visible per stage](https://eventanalytics.ai/blog/exhibitor-onboarding-funnel-stages/): Give every one of your exhibitor onboarding funnel stages a defined entry and exit event, and the per stage conversion rate stops being an opinion.
- [Measuring exhibitor onboarding cycle time from countersignature to show ready status](https://eventanalytics.ai/blog/exhibitor-onboarding-cycle-time/): Exhibitor onboarding cycle time is elapsed days from countersignature to show ready. Report P50 and P90 together, because the median hides the tail.
- [Calculating an exhibitor compliance rate that survives an audit before move in](https://eventanalytics.ai/blog/exhibitor-compliance-rate/): An exhibitor compliance rate is compliant exhibitors over contracted exhibitors at a stated cutoff, and the cutoff you pick moves the answer 39 points.
- [Reading an exhibitor certificate of insurance for the six fields that decide access](https://eventanalytics.ai/blog/exhibitor-certificate-of-insurance/): An exhibitor certificate of insurance is checked field by field: insured name, carrier, policy number, limits, additional insured wording and expiry date.
- [Additional insured verification for shows where three parties must be named](https://eventanalytics.ai/blog/additional-insured-verification/): Additional insured verification is party by party string matching against a required list, and the near miss is the failure mode that survives a human check.
- [Certificate holder versus additional insured and why ops teams confuse the two](https://eventanalytics.ai/blog/certificate-holder-versus-additional-insured/): Certificate holder versus additional insured decides whether your show has coverage or an address label, and the two names sit in different boxes on the form.
- [Insurance certificate expiration tracking against move in and move out dates](https://eventanalytics.ai/blog/insurance-certificate-expiration-tracking/): Insurance certificate expiration tracking compares the policy expiry to your last move-out day, because a certificate can cover show open and expire before teardown.
- [General liability limit checking when the show accepts two different limit structures](https://eventanalytics.ai/blog/general-liability-limit-checking/): General liability limit checking has to evaluate every branch a show accepts, because a rule reading one box rejects certificates that satisfy the other one.
- [Exhibitor W9 collection and the five fields that decide whether it is usable](https://eventanalytics.ai/blog/exhibitor-w9-collection/): Exhibitor W9 collection is only useful if five fields are right, and the one that fails most often is line 1, where the trading name gets typed instead.
- [TIN matching validation before an exhibitor payment file reaches accounts payable](https://eventanalytics.ai/blog/tin-matching-validation/): TIN matching validation checks each exhibitor name and taxpayer number pair against IRS records before the payment file runs, turning next year's notice into this month's fix.
- [Backup withholding on exhibitor payments and the paperwork gap that triggers it](https://eventanalytics.ai/blog/backup-withholding-on-exhibitor-payments/): Backup withholding on exhibitor payments starts at 24 per cent when a taxpayer number is missing, so the fix is a payment block at source rather than a correction later.
- [Foreign exhibitor tax forms and why the W9 workflow breaks at the border](https://eventanalytics.ai/blog/foreign-exhibitor-tax-forms/): Foreign exhibitor tax forms sit outside the W-9 workflow entirely, so route by country from the contract and request a W-8 before anybody emails the wrong form.
- [Building an exhibitor deadline calendar from a service kit nobody reads](https://eventanalytics.ai/blog/exhibitor-deadline-calendar/): An exhibitor deadline calendar extracts every date from the service kit into one table with an owner, a penalty and a dependency, then publishes only the dates that apply.
- [The advance warehouse cutoff date is the deadline that costs exhibitors most](https://eventanalytics.ai/blog/advance-warehouse-cutoff-date/): The advance warehouse cutoff date decides which drayage rate an exhibitor pays, and on a real 2026 rate sheet the late fee makes the warehouse the worse option.
- [Discount deadline compliance and what the late rate really costs your exhibitors](https://eventanalytics.ai/blog/discount-deadline-compliance/): Discount deadline compliance is measurable per service line, and on a published 2026 electrical order form the late rate runs about 50 per cent above the advance rate.
- [Booth services order extraction turns a stack of pdf forms into a schedule](https://eventanalytics.ai/blog/booth-services-order-extraction/): Booth services order extraction pulls line item, quantity, service date and booth number from every contractor form, then reconciles the booth number against the contract.
- [Exhibitor appointed contractor approval is a second insurance workflow hiding inside the first](https://eventanalytics.ai/blog/exhibitor-appointed-contractor-approval/): Exhibitor appointed contractor approval adds a compliance record per contractor, so model the EAC as a child of the exhibitor and size the queue from contractor counts.
- [Exhibitor manual design that treats the manual as a product with users](https://eventanalytics.ai/blog/exhibitor-manual-design/): Exhibitor manual design works better as software: one required action per screen, sections filtered by booth type, and instrumentation on what actually gets opened.
- [Measuring exhibitor service kit adoption with four counts you already have](https://eventanalytics.ai/blog/exhibitor-service-kit-adoption/): Exhibitor service kit adoption needs four counts rather than one: kits opened, sections viewed, forms started and forms submitted, each plotted by week from release.

## Portfolio and M&A

Buying and selling events. Diligence, portfolio construction and pruning, launches and geo-clones, post-merger integration, vendor rationalisation and synergy tracking.

- [Trade show business value drivers a buyer actually pays for](https://eventanalytics.ai/blog/trade-show-business-value-drivers/): The four trade show business value drivers a buyer can recompute from the seller's own files: tenure mix, waitlist depth, price realisation and buyer scarcity.
- [How to test whether an exhibition brand moat is real](https://eventanalytics.ai/blog/exhibition-brand-moat/): An exhibition brand moat is a claim you can falsify. Run a substitution audit on your top 40 exhibitors and see how much of their category spend you hold.
- [Attendance data due diligence before you sign a trade show deal](https://eventanalytics.ai/blog/attendance-data-due-diligence/): Attendance data due diligence means rebuilding the headline figure from badge records yourself, then explaining every row you removed before you price the show.
- [Exhibitor retention diligence and the three ways a seller flatters it](https://eventanalytics.ai/blog/exhibitor-retention-diligence/): Exhibitor retention diligence recomputes three figures on one fixed cohort of companies: logo retention, revenue retention and square metre retention.
- [Revenue concentration analysis on a show you are about to buy](https://eventanalytics.ai/blog/revenue-concentration-analysis/): A revenue concentration analysis on a trade show reprices the deal: top ten exhibitor share, a Herfindahl index, and both figures three editions back.

## Post-show reporting

The report itself. KPI definitions that reconcile, verified attendance, year over year variance decomposition, event level ROI, and closing the pack while anyone still cares.

- [What belongs in a post show report and what gets cut](https://eventanalytics.ai/blog/post-show-report/): A post show report answers four questions in order: who came, who exhibited, what sold, what people said. What belongs in each section, and what gets cut.
- [Standardizing show reports so five editions can be compared at all](https://eventanalytics.ai/blog/standardizing-show-reports/): Standardizing show reports takes a versioned section list, one fixed name per metric, and a changelog row carrying a restated figure when a definition moves.
- [Writing the post event report executive summary a chief executive will actually read](https://eventanalytics.ai/blog/post-event-report-executive-summary/): A post event report executive summary is five numbers, each with a prior year figure and one graded cause, ranked by how unusual the move is for that metric.
- [Post show reporting stakeholders and why one report cannot serve all of them](https://eventanalytics.ai/blog/post-show-reporting-stakeholders/): Post show reporting stakeholders want different grains and deadlines. The answer is one warehouse, four published cuts and a shared definitions appendix.
- [Event KPI definitions that stop the same number meaning two things](https://eventanalytics.ai/blog/event-kpi-definitions/): Event KPI definitions need four slots: population, filters, time window and source system. Leave one out and two people read the same metric name two ways.
- [The unique attendee definition decides whether your show grew or shrank](https://eventanalytics.ai/blog/unique-attendee-definition/): Your unique attendee definition decides the growth number. Badge, email, resolved person and organisation give four counts, with a spread past 15 per cent.
- [Settling an attendance metric disagreement between teams before the report ships](https://eventanalytics.ai/blog/attendance-metric-disagreement-between-teams/): An attendance metric disagreement between teams is almost never arithmetic. Run a definition diff, reconcile the gap to the last person, then price it.
- [Counting exhibiting companies when co exhibitors and pavilions blur the line](https://eventanalytics.ai/blog/counting-exhibiting-companies/): Counting exhibiting companies gives three legitimate answers: contracted accounts, exhibiting brands and directory listings. Publish one, disclose two.
- [Running registration to attendance reconciliation as a numbered ledger every year](https://eventanalytics.ai/blog/registration-to-attendance-reconciliation/): Run registration to attendance reconciliation as a numbered ledger: open with registrations, subtract and add named populations, close on the reported figure.
- [Verified attendance reporting and the evidence trail behind every headline number](https://eventanalytics.ai/blog/verified-attendance-reporting/): Verified attendance reporting needs one column: an evidence type on every counted row. Publish the mix of scanned, printed and manual beside the headline.
- [Reconciling badge scan counts when three systems each claim a different total](https://eventanalytics.ai/blog/reconciling-badge-scan-counts/): Reconciling badge scan counts across entry, session and lead retrieval systems by collapsing every feed to distinct badge and date, then naming the residual.
- [Excluding staff badges from attendance and disclosing what you took out](https://eventanalytics.ai/blog/excluding-staff-badges-from-attendance/): Excluding staff badges from attendance without an argument: classify every badge type at registration, report by class, and publish the ladder underneath.
- [Decomposing year over year attendance variance into causes you can act on](https://eventanalytics.ai/blog/year-over-year-attendance-variance/): Year over year attendance variance says nothing as one percentage. Split it into retained, lapsed and new attendees, then by channel and by geography.
- [Building a show revenue bridge analysis that survives a finance review](https://eventanalytics.ai/blog/show-revenue-bridge-analysis/): A show revenue bridge analysis splits growth into volume, rate and mix on the space line, so finance can see how much of the increase was really price.
- [Reading the new versus returning attendee mix in your post show numbers](https://eventanalytics.ai/blog/new-versus-returning-attendee-mix/): The new versus returning attendee mix hides behind a flat total. Cohort every badge against three prior editions and read retention by year of first visit.
- [Isolating the calendar shift effect on attendance before you blame marketing](https://eventanalytics.ai/blog/calendar-shift-effect-on-attendance/): Isolating the calendar shift effect on attendance: compare editions by day position, size the closing-day move, and hand marketing only the residual.
- [The event ROI calculation an organiser can defend line by line](https://eventanalytics.ai/blog/event-roi-calculation/): An event ROI calculation an organiser can defend: contribution over direct show cost, with every allocated line reported separately and the boundary stated.
- [Return on objectives for events when the goal was never a revenue number](https://eventanalytics.ai/blog/return-on-objectives-for-events/): Return on objectives for events scores an edition whose purpose was never revenue, using levels set in writing before doors open and a data source per level.
- [Cost to attract an attendee and the three ways teams get it wrong](https://eventanalytics.ai/blog/cost-to-attract-an-attendee/): Cost to attract an attendee moves threefold depending on where you draw the numerator and denominator. Here is the honest version and the three usual errors.
- [Measuring the ROI of a show feature area without double counting revenue](https://eventanalytics.ai/blog/roi-of-a-show-feature-area/): The ROI of a show feature area collapses once you count only exhibitors new to the show. Here is the incremental version and the range around it.

## Publishing operations

Running many event brands at once. The brief as an artefact, intake, review and approval, brand systems, launching an edition, and naming and rebrands.

- [What an event brief template must decide before anyone designs anything](https://eventanalytics.ai/blog/event-brief-template/): An event brief template only works if five sections carry an actual decision. Here is how to score a live brief, section by section, and what to cut.
- [Which creative brief sections are decisions and which are just description](https://eventanalytics.ai/blog/creative-brief-sections/): Creative brief sections split into two kinds: decisions that must be made fresh each edition, and descriptions that can safely be copied forward.
- [A brief quality score you can apply before work starts](https://eventanalytics.ai/blog/brief-quality-score/): A brief quality score built from five items, each scored zero to two, gives a portfolio a number it can compare across shows before work starts.
- [Treating the brief as source of truth when decks keep contradicting it](https://eventanalytics.ai/blog/brief-as-source-of-truth/): Making the brief the source of truth means every decision has one home, and any deck that disagrees with it gets deleted the same day it is found.

## Renewals

Rebooking and what predicts it. Renewal rate definitions, at-risk scoring, account health, win-back, sales call lists and revenue forecasting for exhibition sales.

- [What an onsite rebooking rate actually measures and what it hides](https://eventanalytics.ai/blog/onsite-rebooking-rate/): An onsite rebooking rate is decided by a denominator nobody wrote down: four honest bases put the same 402 signings anywhere between 56.5 and 69.1 per cent.
- [Building a rebooking conversion funnel from appointment held to deposit received](https://eventanalytics.ai/blog/rebooking-conversion-funnel/): A rebooking conversion funnel splits one rate into five, and on 640 targets it shows the appointment diary losing 210 of the 238 accounts that never signed.
- [The post show rebooking window and how fast intent decays](https://eventanalytics.ai/blog/post-show-rebooking-window/): The post show rebooking window front loads hard: across 238 unrenewed accounts, week one converted 18.1 per cent of them and week eight only 3.0 per cent.
- [Rebooking cancellation rate is the number your gross figure leaves out](https://eventanalytics.ai/blog/rebooking-cancellation-rate/): A rebooking cancellation rate is the give-back between signature and first payment: 31 of 402 onsite signings left, and five times more in the deadline cohort.
- [Writing an exhibitor retention rate definition two analysts can both reproduce](https://eventanalytics.ai/blog/exhibitor-retention-rate-definition/): An exhibitor retention rate definition has to fix three things, and moving only the measurement date swung one show's rate 5.6 points across the same cohort.
- [Logo retention versus revenue retention and why you report both](https://eventanalytics.ai/blog/logo-retention-versus-revenue-retention/): Logo retention versus revenue retention on one cohort: 448 of 640 companies back is 70.0 per cent, but the money that survived with them is 88.1 per cent.
- [Net revenue retention for exhibitions when booth sizes move both ways](https://eventanalytics.ai/blog/net-revenue-retention-for-exhibitions/): Net revenue retention for exhibitions is capped by the hall: on a sold out floor at fixed prices, the returning cohort cannot get past 100 per cent at all.
- [First time exhibitor retention is where most of your churn lives](https://eventanalytics.ai/blog/first-time-exhibitor-retention/): First time exhibitor retention ran 44.1 per cent on one show against 77.4 for everybody else, so 18.3 per cent of the base produced 35.7 per cent of the churn.
- [Space retention rate measures the show floor your renewals actually hold](https://eventanalytics.ai/blog/space-retention-rate/): A space retention rate says how much floor your renewals hold: on one hall the same cohort read 73.6 per cent in companies and 85.0 per cent in square metres.
- [Building an exhibitor churn prediction model that beats a simple baseline](https://eventanalytics.ai/blog/exhibitor-churn-prediction-model/): An exhibitor churn prediction model earns its place only against a baseline: 0.71 against a 0.627 persistence rule bought four extra churners in the top decile.
- [Which exhibitor churn model features carry real signal in exhibitions](https://eventanalytics.ai/blog/exhibitor-churn-model-features/): The exhibitor churn model features that carry real signal come from five families of billing and behaviour data, ranked honestly by permutation importance.
- [Survival analysis for exhibitor churn puts a date on the risk](https://eventanalytics.ai/blog/survival-analysis-exhibitor-churn/): Survival analysis for exhibitor churn turns a renewed or lapsed flag into a hazard per edition, so a risk score finally carries a date a sales team can work to.
- [Churn model label leakage and the fields that encode the answer](https://eventanalytics.ai/blog/churn-model-label-leakage/): Churn model label leakage in exhibitions comes from fields written after the renewal conversation starts. Here is how to find them and what a rebuild costs.
- [Leading indicators of exhibitor churn ranked by how early they appear](https://eventanalytics.ai/blog/leading-indicators-of-exhibitor-churn/): Rank the leading indicators of exhibitor churn by how many days of warning each one buys, because a signal arriving ten days out is a receipt and not a warning.
- [Show week renewal signals you can only collect before teardown](https://eventanalytics.ai/blog/show-week-renewal-signals/): The show week renewal signals worth having are booth staff hours, decision maker attendance and stand scans, and all of them vanish within days of teardown.
- [Counting service tickets as renewal risk without punishing your largest exhibitors](https://eventanalytics.ai/blog/service-tickets-as-renewal-risk/): Counting service tickets as renewal risk ranks your biggest exhibitors first. Normalise by stand size, shrink small accounts to the median, then read reopens.
- [Finding silent exhibitor accounts before the renewal call goes badly](https://eventanalytics.ai/blog/silent-exhibitor-accounts/): Silent exhibitor accounts are measurable: count days since the last exhibitor-initiated contact, then rank each account against its own normal gap.
- [Designing an exhibitor account health score a sales director will trust](https://eventanalytics.ai/blog/exhibitor-account-health-score/): An exhibitor account health score gets used only if a rep can take it apart. Five weighted components, published weights, every input checkable in a minute.
- [Setting account health score bands so green actually means something](https://eventanalytics.ai/blog/account-health-score-bands/): Set account health score bands from observed renewal. Find where renewal crosses 60 per cent, then judge every candidate red line on size, capture and lift.

## Space and pricing

Rate cards, zone and dynamic pricing, floorplan design, net square foot yield, premium location premiums, sell-through, waitlists and priority points systems.

- [How to design a booth rate card that survives a full sales cycle](https://eventanalytics.ai/blog/booth-rate-card-design/): Booth rate card design is three stacked decisions: base rate per net square foot, a size ladder, and location adjustments. How to set and defend each one.
- [What booth price per square foot actually tells you about a show](https://eventanalytics.ai/blog/booth-price-per-square-foot/): Booth price per square foot is two ratios. Compute it over net square feet sold and again over gross hall area, then split the rate effect from the mix effect.
- [Setting an annual booth price increase without losing the middle of the floor](https://eventanalytics.ai/blog/annual-booth-price-increase/): An annual booth price increase does not have to be flat. Hold the entry rate, raise premium locations, and price what that split costs before the meeting.
- [Booth size tier pricing and why the linear ladder breaks above 400 square feet](https://eventanalytics.ai/blog/booth-size-tier-pricing/): Booth size tier pricing breaks when the ladder stays linear. Price the tiers marginally, put the breakpoints above your median booth, and cost the taper first.
- [How much is a corner booth premium worth and how to price it](https://eventanalytics.ai/blog/corner-booth-premium/): A corner booth premium should be priced per linear foot of new aisle frontage rather than as a percentage. What a corner buys, and what it cannot promise.
- [The island booth price premium and what four open sides are really worth](https://eventanalytics.ai/blog/island-booth-price-premium/): The island booth price premium is measurable on your own floor. Match islands against inline blocks of the same size and zone, then read the gap in paid rate.
- [Building a hedonic pricing model for booth location on your own floorplan](https://eventanalytics.ai/blog/hedonic-pricing-model-booth-location/): A hedonic pricing model for booth location turns three editions of contracts into dollar values for open sides, aisle frontage and distance from the entrance.
- [Zone based booth pricing and how to draw the zone lines defensibly](https://eventanalytics.ai/blog/zone-based-booth-pricing/): Zone based booth pricing works when the lines come from ranked data rather than a highlighter. How to cut the zones, cap the premium and solve the base rate.
- [Where dynamic booth pricing in exhibitions helps and where it breaks](https://eventanalytics.ai/blog/dynamic-booth-pricing-exhibitions/): Dynamic booth pricing in exhibitions breaks on buyers who compare notes. Where repricing works, where it costs renewals, and why the rule has to be published.
- [Making early bird booth pricing pay for the certainty it buys](https://eventanalytics.ai/blog/early-bird-booth-pricing/): Early bird booth pricing buys cash timing and forecast certainty, and pays for both. How to measure what the discount hands to accounts that were never leaving.
- [Estimating booth price elasticity when you only have five editions of data](https://eventanalytics.ai/blog/booth-price-elasticity/): Booth price elasticity will not come out of five editions of history. Two survey methods, from 1966 and 1976, give a number you can defend to finance.
- [What revenue management for exhibitions borrows from airlines and what it cannot](https://eventanalytics.ai/blog/revenue-management-for-exhibitions/): Revenue management for exhibitions borrows every airline condition but one: booth 412 is not booth 1130. Pool within a zone, then set protection levels.
- [How a priority points system in exhibitions shapes who gets the good space](https://eventanalytics.ai/blog/priority-points-system-exhibitions/): The priority points system exhibitions use to allocate space is a queue with a published sorting key, and the formula decides who picks first for a decade.
- [Running a booth space draw process that does not eat three weeks](https://eventanalytics.ai/blog/booth-space-draw-process/): A booth space draw process is a queue with a service rate. Time it before you schedule it, and find out what 400 exhibitors really cost you in hours.
- [Designing a priority points formula that rewards the behaviour you actually want](https://eventanalytics.ai/blog/priority-points-formula-design/): Priority points formula design decides who picks first for a decade. Add decay and an early booking point, then simulate the standings before you publish.
- [Space selection appointment scheduling and the queue that decides your floorplan](https://eventanalytics.ai/blog/space-selection-appointment-scheduling/): Space selection appointment scheduling is queue design. Band your slots by booth size, stage the map release, and find out who really owns the first day.
- [Exhibition floorplan design decisions that set your revenue before sales opens](https://eventanalytics.ai/blog/exhibition-floorplan-design/): Exhibition floorplan design sets the revenue ceiling before sales opens. Count corners, perimeter runs and islands off the drawing, then price what it made.
- [Trade show aisle width is a pricing decision as much as a safety one](https://eventanalytics.ai/blog/trade-show-aisle-width/): Trade show aisle width is priced in square feet you cannot sell. Work the pitch arithmetic before widening, because the back of envelope number is wrong.
- [What to do about back of hall pricing when the aisles run cold](https://eventanalytics.ai/blog/back-of-hall-pricing/): Back of hall pricing by discount is permanent and the cold aisle is not. Move a demand anchor instead, then measure realised rate inside a 60 foot radius.

## Sponsorship

Non-booth inventory. Package construction, CPM and value pricing, activation measurement, digital and app inventory, signage, press value and sponsor renewal.

- [Run a sponsorship inventory audit before you print another rate card](https://eventanalytics.ai/blog/sponsorship-inventory-audit/): A sponsorship inventory audit records every sellable asset with its unit count, exposure window and price, including the ones missing from the rate card.
- [Sponsorship inventory sizing decides whether your assets sell or sit](https://eventanalytics.ai/blog/sponsorship-inventory-sizing/): Sponsorship inventory sizing sets how many units of an asset you offer. Add units and you cut scarcity, drag price and often finish the edition with less.
- [Sponsorship sell through rate is the number your rate card is hiding](https://eventanalytics.ai/blog/sponsorship-sell-through-rate/): Sponsorship sell through rate needs two ratios per asset: units sold over units offered, and revenue captured over card value. One number hides the other.
- [Three sponsorship valuation methods and when each one gives a defensible number](https://eventanalytics.ai/blog/sponsorship-valuation-methods/): The three sponsorship valuation methods in use, cost-plus, market comparable and impression-based, price one lanyard six times apart. When each one holds up.
- [Pricing sponsorship without comparables when the asset has never been sold](https://eventanalytics.ai/blog/pricing-sponsorship-without-comparables/): Pricing sponsorship without comparables means building a floor from cost, a ceiling from the nearest priced asset, and a measurement plan that sets edition two.
- [The intangible sponsorship value multiplier is where most valuations go wrong](https://eventanalytics.ai/blog/intangible-sponsorship-value-multiplier/): An intangible sponsorship value multiplier of 1.6 on 40,000 of assets invents 24,000 nobody measured. Unbundle it into four line items you can price separately.
- [Category exclusivity pricing means charging for the competitors you turn away](https://eventanalytics.ai/blog/category-exclusivity-pricing/): Category exclusivity pricing starts from the revenue you turn away. Weight each forgone deal by its chance of returning, then make the fee clear that total.
- [Comparing sponsorship assets on CPM makes a lanyard and an email argue fairly](https://eventanalytics.ai/blog/comparing-sponsorship-assets-on-cpm/): Comparing sponsorship assets on CPM puts a lanyard, an aisle sign and a sponsored email on one axis, so a rate card can be ranked and then defended.
- [Sponsorship impression error bars belong on the report you send the sponsor](https://eventanalytics.ai/blog/sponsorship-impression-error-bars/): Sponsorship impression error bars turn a fake-precise 12,600 into a 5,000 to 20,200 band, and the variance split tells you which input to go and measure.
- [Double counting sponsorship impressions is how a package reaches unbelievable reach](https://eventanalytics.ai/blog/double-counting-sponsorship-impressions/): Double counting sponsorship impressions turns nine assets into a headline number no attendance base can support. Split gross from net reach and report the ratio.
- [The attendance denominator for sponsorship metrics decides every number above it](https://eventanalytics.ai/blog/attendance-denominator-for-sponsorship-metrics/): The attendance denominator for sponsorship metrics moves a CPM from 156 to 333 on the same asset at the same price. Pick one base, write it down, use it everywhere.
- [Sponsored email pricing follows deliverability before it follows list size](https://eventanalytics.ai/blog/sponsored-email-pricing/): Sponsored email pricing set against total list size overstates reach. Price on delivered and opened, and one 4,000 dollar send costs five times more.
- [Enhanced directory listing pricing works when you can show the click difference](https://eventanalytics.ai/blog/enhanced-directory-listing-pricing/): Enhanced directory listing pricing rests on the view difference the upgrade causes. The raw gap between upgraded and standard listings is mostly self-selection.
- [A sponsor renewal rate definition that survives a board meeting](https://eventanalytics.ai/blog/sponsor-renewal-rate-definition/): A sponsor renewal rate definition has to pick a denominator. The same edition can honestly report 67, 55, 62 or 72 per cent depending on what you count.
- [Which sponsor renewal predictors actually appear in your own data](https://eventanalytics.ai/blog/sponsor-renewal-predictors/): Sponsor renewal predictors are testable against three editions of your own data. With 49 non-renewals in the file, four candidate signals is the honest ceiling.
- [Advertising value equivalency for events is the number sponsors stopped believing](https://eventanalytics.ai/blog/advertising-value-equivalency-for-events/): Why advertising value equivalency for events converts exposure into a price nobody paid, what the arithmetic actually does, and what a sponsor can check instead.
- [The PR multiplier for sponsorship has no evidence behind the number three](https://eventanalytics.ai/blog/pr-multiplier-for-sponsorship/): Where the PR multiplier for sponsorship came from, why no published research fixes its value, and what a sensitivity test on 2.5 to 8 does to a recap total.
- [What to report instead of AVE when the sponsor wants a dollar figure](https://eventanalytics.ai/blog/what-to-report-instead-of-ave/): What to report instead of AVE: cost per outcome built from an invoice and a counted denominator, worked down three levels of a real sponsorship funnel.
- [Sponsorship tier design fails when the middle tier has nothing distinctive](https://eventanalytics.ai/blog/sponsorship-tier-design/): Sponsorship tier design breaks when a buyer can assemble the middle tier from cheaper parts. How to test your ladder for that gap and price the exclusive asset.

## Standards and research

Audited attendance, third-party verification, industry definitions, published research and how to read it, survey methodology, and comparability across shows and countries.

- [What an exhibition attendance audit actually checks before the certificate is signed](https://eventanalytics.ai/blog/exhibition-attendance-audit/): What an exhibition attendance audit checks stage by stage, which three figures the auditor certifies, and what happens to badges that trace back to no record.
- [Event audit scope limits and the questions an auditor will not answer](https://eventanalytics.ai/blog/event-audit-scope-limits/): The scope limits of an event audit, what the auditor's declaration actually covers, and why a certified visitor figure says nothing about audience quality.
- [Choosing an event auditor from the UFI accredited list without surprises](https://eventanalytics.ai/blog/choosing-an-event-auditor/): Choosing an event auditor from UFI's accredited list: who may sign a certificate, what to ask before scoping, and the two costs that never appear in the quote.
- [The audit evidence your registration file has to produce on request](https://eventanalytics.ai/blog/audit-evidence-registration-file/): The audit evidence a registration file has to produce: which extracts an exhibition auditor asks for, how they must reconcile, and why you build the pack once.
- [Audit frequency across exhibition editions and what keeps a UFI label alive](https://eventanalytics.ai/blog/audit-frequency-exhibition-editions/): Audit frequency across exhibition editions under UFI rules: the every other edition cadence, the new entrant exception, and the six month certificate deadline.
- [Verified versus registered attendance and the gap between those two numbers](https://eventanalytics.ai/blog/verified-versus-registered-attendance/): Verified versus registered attendance: what each base contains, why the gap has two separate halves, and which of the two numbers belongs in a media kit.
- [Counting unique attendees versus visits without inflating your headline number](https://eventanalytics.ai/blog/unique-attendees-versus-visits/): Unique attendees versus visits: the ladder from reader events to a certified figure, and why a 1.5 visit factor does not mean a bigger unique audience.
- [Whether exhibitor staff count in attendance figures your show publishes](https://eventanalytics.ai/blog/exhibitor-staff-in-attendance/): Whether exhibitor staff count in attendance: the standard keeps them out of visitors, puts them inside total attendance, and gives the certificate no box.
- [How no shows in audited attendance change the number an auditor signs](https://eventanalytics.ai/blog/no-shows-in-audited-attendance/): How no shows in audited attendance work: the standard counts arrivals only, the certificate hides the gap, and absence can cost the international label.
- [How comp and guest badges appear on an audited attendance certificate](https://eventanalytics.ai/blog/comp-and-guest-badges/): How comp and guest badges appear on an audited attendance certificate: they count when the holder attends, and no badge type appears on the form itself.
- [Exhibition terminology standards and the words organisers keep using differently](https://eventanalytics.ai/blog/exhibition-terminology-standards/): Exhibition terminology standards fix what a visitor, a visit and total attendance mean, and a portfolio benchmark is only as good as the words underneath it.
- [Why two shows in one sector report attendance so differently](https://eventanalytics.ai/blog/why-two-shows-report-differently/): Two shows in one sector can both report honestly and still publish incomparable attendance, because the base underneath each number is chosen and rarely stated.
- [Participants versus visitors terminology and why the broader word creeps in](https://eventanalytics.ai/blog/participants-versus-visitors-terminology/): Participants versus visitors terminology matters because participant has no published definition, so the bucket widens each year nobody records its contents.
- [Trade versus consumer show counting rules and where the evidence diverges](https://eventanalytics.ai/blog/trade-versus-consumer-show-counting/): Trade versus consumer show counting rules diverge because a ticket proves an admission and a badge proves a person, and each is weak where the other is strong.
- [Net square metres of exhibition space and what an auditor counts](https://eventanalytics.ai/blog/net-square-metres-exhibition-space/): Net square metres of exhibition space is contracted floor occupied by exhibitors, paid or unpaid, indoors and outdoors, with the last two reported apart.
- [Converting net square metres to square feet without breaking your benchmark](https://eventanalytics.ai/blog/net-square-metres-to-square-feet/): Converting net square metres to square feet with a rounded factor turns a flat year into growth, because the error is bigger than most shows' annual change.
- [Gross versus net exhibition space and the ratio worth tracking yourself](https://eventanalytics.ai/blog/gross-versus-net-exhibition-space/): Gross versus net exhibition space are reported by two different parties for different purposes, and the ratio between them moves when the denominator changes.
- [Booth size unit conversion errors that quietly corrupt a portfolio roll up](https://eventanalytics.ai/blog/booth-size-unit-conversion-errors/): Booth size unit conversion errors survive every total anyone checks, because they corrupt size bands and averages long before they show up in a portfolio sum.
- [Reading a benchmark study sample definition before you quote the number](https://eventanalytics.ai/blog/benchmark-study-sample-definition/): A benchmark study sample definition decides what the average means, and the published detail is usually enough to work out whether your show is in it at all.