<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel><title>EventAnalytics blog</title><link>https://eventanalytics.ai/blog/</link><description>Analytics for trade show and exhibition organisers</description><language>en-gb</language><item><title>Capitalising sales commissions for events under the costs to obtain a contract rules</title><link>https://eventanalytics.ai/blog/capitalising-sales-commissions-for-events/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/capitalising-sales-commissions-for-events/</guid><category>Event finance</category><description>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.</description></item><item><title>Venue cost in event budgets and the clauses that move it after signature</title><link>https://eventanalytics.ai/blog/venue-cost-in-event-budgets/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/venue-cost-in-event-budgets/</guid><category>Event finance</category><description>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.</description></item><item><title>Gross versus net revenue presentation when the organiser resells stand build and housing</title><link>https://eventanalytics.ai/blog/gross-versus-net-revenue-presentation/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/gross-versus-net-revenue-presentation/</guid><category>Event finance</category><description>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.</description></item><item><title>Delegate fee revenue recognition for a conference running alongside the exhibition</title><link>https://eventanalytics.ai/blog/delegate-fee-revenue-recognition/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/delegate-fee-revenue-recognition/</guid><category>Event finance</category><description>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.</description></item><item><title>Sponsorship revenue accounting when the package spans a year and one show week</title><link>https://eventanalytics.ai/blog/sponsorship-revenue-accounting/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/sponsorship-revenue-accounting/</guid><category>Event finance</category><description>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.</description></item><item><title>What belongs in space revenue versus service revenue when the accounts close</title><link>https://eventanalytics.ai/blog/space-revenue-versus-service-revenue/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/space-revenue-versus-service-revenue/</guid><category>Event finance</category><description>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.</description></item><item><title>Allocating central overhead to shows without starting a war between show directors</title><link>https://eventanalytics.ai/blog/allocating-central-overhead-to-shows/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/allocating-central-overhead-to-shows/</guid><category>Event finance</category><description>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.</description></item><item><title>Forward bookings as a metric only works if the comparison date is fixed</title><link>https://eventanalytics.ai/blog/forward-bookings-as-a-metric/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/forward-bookings-as-a-metric/</guid><category>Event finance</category><description>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.</description></item><item><title>Why a growing event business runs on negative working capital and what breaks it</title><link>https://eventanalytics.ai/blog/negative-working-capital-event-business/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/negative-working-capital-event-business/</guid><category>Event finance</category><description>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.</description></item><item><title>Splitting fixed versus variable event costs before the first budget review</title><link>https://eventanalytics.ai/blog/fixed-versus-variable-event-costs/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/fixed-versus-variable-event-costs/</guid><category>Event finance</category><description>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.</description></item><item><title>The cash profile of an annual show peaks months before the revenue does</title><link>https://eventanalytics.ai/blog/cash-profile-of-an-annual-show/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/cash-profile-of-an-annual-show/</guid><category>Event finance</category><description>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.</description></item><item><title>Deferred revenue for trade shows is the balance sheet line nobody reads carefully</title><link>https://eventanalytics.ai/blog/deferred-revenue-for-trade-shows/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/deferred-revenue-for-trade-shows/</guid><category>Event finance</category><description>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.</description></item><item><title>Revenue cutoff for a show that opens on the last day of the quarter</title><link>https://eventanalytics.ai/blog/revenue-cutoff-for-a-show/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/revenue-cutoff-for-a-show/</guid><category>Event finance</category><description>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.</description></item><item><title>Event phasing across reporting periods and why half year numbers mislead by design</title><link>https://eventanalytics.ai/blog/event-phasing-across-reporting-periods/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/event-phasing-across-reporting-periods/</guid><category>Event finance</category><description>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.</description></item><item><title>Point in time revenue recognition puts a whole show into one reporting period</title><link>https://eventanalytics.ai/blog/point-in-time-revenue-recognition/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/point-in-time-revenue-recognition/</guid><category>Event finance</category><description>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.</description></item><item><title>Finding the break even point for a show before the sales team commits</title><link>https://eventanalytics.ai/blog/break-even-point-for-a-show/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/break-even-point-for-a-show/</guid><category>Event finance</category><description>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.</description></item><item><title>The event gross margin calculation that survives a first look from group finance</title><link>https://eventanalytics.ai/blog/event-gross-margin-calculation/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/event-gross-margin-calculation/</guid><category>Event finance</category><description>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.</description></item><item><title>Contribution margin per square foot tells you which halls are worth opening</title><link>https://eventanalytics.ai/blog/contribution-margin-per-square-foot/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/contribution-margin-per-square-foot/</guid><category>Event finance</category><description>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.</description></item><item><title>The largest direct cost lines on a trade show and how they move</title><link>https://eventanalytics.ai/blog/largest-direct-cost-lines/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/largest-direct-cost-lines/</guid><category>Event finance</category><description>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.</description></item><item><title>Event staff cost allocation when one team runs six shows a year</title><link>https://eventanalytics.ai/blog/event-staff-cost-allocation/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/event-staff-cost-allocation/</guid><category>Event finance</category><description>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.</description></item><item><title>How an event profit and loss structure is built line by line</title><link>https://eventanalytics.ai/blog/event-profit-and-loss-structure/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/event-profit-and-loss-structure/</guid><category>Event finance</category><description>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.</description></item><item><title>KPI tile labels that carry the filter and the window</title><link>https://eventanalytics.ai/blog/kpi-tile-labels/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/kpi-tile-labels/</guid><category>BI and reporting</category><description>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.</description></item><item><title>Metric naming conventions that end the attendance argument</title><link>https://eventanalytics.ai/blog/metric-naming-conventions/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/metric-naming-conventions/</guid><category>BI and reporting</category><description>Metric naming conventions that carry the population, filter and window inside the measure name, so three different numbers called attendance stop colliding.</description></item><item><title>Drill through to record detail when a number is disputed</title><link>https://eventanalytics.ai/blog/drill-through-to-record-detail/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/drill-through-to-record-detail/</guid><category>BI and reporting</category><description>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.</description></item><item><title>Drill down path design that follows overview first</title><link>https://eventanalytics.ai/blog/drill-down-path-design/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/drill-down-path-design/</guid><category>BI and reporting</category><description>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.</description></item><item><title>The pre show countdown dashboard for the final week</title><link>https://eventanalytics.ai/blog/pre-show-countdown-dashboard/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/pre-show-countdown-dashboard/</guid><category>BI and reporting</category><description>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.</description></item><item><title>How many KPI tiles a page can carry</title><link>https://eventanalytics.ai/blog/how-many-kpi-tiles/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/how-many-kpi-tiles/</guid><category>BI and reporting</category><description>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.</description></item><item><title>Dashboard visual hierarchy decides what gets seen first</title><link>https://eventanalytics.ai/blog/dashboard-visual-hierarchy/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/dashboard-visual-hierarchy/</guid><category>BI and reporting</category><description>Dashboard visual hierarchy puts the number that triggers action top left and sizes it largest, using eyetracking evidence about where readers actually look.</description></item><item><title>Embedded report authentication tokens that never trust a client supplied id</title><link>https://eventanalytics.ai/blog/embedded-report-authentication-tokens/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/embedded-report-authentication-tokens/</guid><category>BI and reporting</category><description>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.</description></item><item><title>Multi tenant analytics isolation so one exhibitor never sees another set of rows</title><link>https://eventanalytics.ai/blog/multi-tenant-analytics-isolation/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/multi-tenant-analytics-isolation/</guid><category>BI and reporting</category><description>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.</description></item><item><title>Dashboard requirements gathering begins with a decision</title><link>https://eventanalytics.ai/blog/dashboard-requirements-gathering/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/dashboard-requirements-gathering/</guid><category>BI and reporting</category><description>Dashboard requirements gathering that starts from the decision the reader has to make, using a one page brief naming audience, cadence and the measures.</description></item><item><title>Embedded analytics for exhibitors inside the portal they already log into</title><link>https://eventanalytics.ai/blog/embedded-analytics-for-exhibitors/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/embedded-analytics-for-exhibitors/</guid><category>BI and reporting</category><description>Embedded analytics for exhibitors puts one report definition inside the portal they already use, passing identity from the session so nobody signs in twice.</description></item><item><title>Object level security when the row is fine but the column is not</title><link>https://eventanalytics.ai/blog/object-level-security/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/object-level-security/</guid><category>BI and reporting</category><description>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.</description></item><item><title>Sensitivity labels on event reports so exports carry their classification out</title><link>https://eventanalytics.ai/blog/sensitivity-labels-on-reports/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/sensitivity-labels-on-reports/</guid><category>BI and reporting</category><description>Sensitivity labels on reports travel with exports to Excel, PDF and PowerPoint, never to CSV, and inside the service they classify without restricting access.</description></item><item><title>Workspace permissions for event teams that stop everybody becoming an admin</title><link>https://eventanalytics.ai/blog/workspace-permissions-for-event-teams/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/workspace-permissions-for-event-teams/</guid><category>BI and reporting</category><description>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.</description></item><item><title>Testing row level security before one exhibitor can see another exhibitor data</title><link>https://eventanalytics.ai/blog/testing-row-level-security/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/testing-row-level-security/</guid><category>BI and reporting</category><description>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.</description></item><item><title>Dynamic row level security mapping tables beat one static role per show</title><link>https://eventanalytics.ai/blog/dynamic-row-level-security-mapping/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/dynamic-row-level-security-mapping/</guid><category>BI and reporting</category><description>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.</description></item><item><title>Row level security for event portfolios where a director sees only their show</title><link>https://eventanalytics.ai/blog/row-level-security-for-event-portfolios/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/row-level-security-for-event-portfolios/</guid><category>BI and reporting</category><description>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.</description></item><item><title>Certified versus ad hoc reports and the badge that tells readers which</title><link>https://eventanalytics.ai/blog/certified-versus-ad-hoc-reports/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/certified-versus-ad-hoc-reports/</guid><category>BI and reporting</category><description>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.</description></item><item><title>Metric change control for the day a definition changes mid year</title><link>https://eventanalytics.ai/blog/metric-change-control/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/metric-change-control/</guid><category>BI and reporting</category><description>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.</description></item><item><title>Metric definitions in tooltips beside the number</title><link>https://eventanalytics.ai/blog/metric-definitions-in-tooltips/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/metric-definitions-in-tooltips/</guid><category>BI and reporting</category><description>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.</description></item><item><title>Show director dashboard design around three questions</title><link>https://eventanalytics.ai/blog/show-director-dashboard-design/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/show-director-dashboard-design/</guid><category>BI and reporting</category><description>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.</description></item><item><title>Revenue concentration analysis on a show you are about to buy</title><link>https://eventanalytics.ai/blog/revenue-concentration-analysis/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/revenue-concentration-analysis/</guid><category>Portfolio and M&amp;A</category><description>A revenue concentration analysis on a trade show reprices the deal: top ten exhibitor share, a Herfindahl index, and both figures three editions back.</description></item><item><title>Exhibitor retention diligence and the three ways a seller flatters it</title><link>https://eventanalytics.ai/blog/exhibitor-retention-diligence/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/exhibitor-retention-diligence/</guid><category>Portfolio and M&amp;A</category><description>Exhibitor retention diligence recomputes three figures on one fixed cohort of companies: logo retention, revenue retention and square metre retention.</description></item><item><title>Attendance data due diligence before you sign a trade show deal</title><link>https://eventanalytics.ai/blog/attendance-data-due-diligence/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/attendance-data-due-diligence/</guid><category>Portfolio and M&amp;A</category><description>Attendance data due diligence means rebuilding the headline figure from badge records yourself, then explaining every row you removed before you price the show.</description></item><item><title>How to test whether an exhibition brand moat is real</title><link>https://eventanalytics.ai/blog/exhibition-brand-moat/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/exhibition-brand-moat/</guid><category>Portfolio and M&amp;A</category><description>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.</description></item><item><title>Trade show business value drivers a buyer actually pays for</title><link>https://eventanalytics.ai/blog/trade-show-business-value-drivers/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/trade-show-business-value-drivers/</guid><category>Portfolio and M&amp;A</category><description>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.</description></item><item><title>Treating the brief as source of truth when decks keep contradicting it</title><link>https://eventanalytics.ai/blog/brief-as-source-of-truth/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/brief-as-source-of-truth/</guid><category>Publishing operations</category><description>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.</description></item><item><title>A brief quality score you can apply before work starts</title><link>https://eventanalytics.ai/blog/brief-quality-score/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/brief-quality-score/</guid><category>Publishing operations</category><description>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.</description></item><item><title>Which creative brief sections are decisions and which are just description</title><link>https://eventanalytics.ai/blog/creative-brief-sections/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/creative-brief-sections/</guid><category>Publishing operations</category><description>Creative brief sections split into two kinds: decisions that must be made fresh each edition, and descriptions that can safely be copied forward.</description></item><item><title>What an event brief template must decide before anyone designs anything</title><link>https://eventanalytics.ai/blog/event-brief-template/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/event-brief-template/</guid><category>Publishing operations</category><description>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.</description></item><item><title>Turning a panel into an article that reads better than the session</title><link>https://eventanalytics.ai/blog/turning-a-panel-into-an-article/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/turning-a-panel-into-an-article/</guid><category>Content and media</category><description>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.</description></item><item><title>A conference transcript editing workflow that turns raw speech into publishable copy</title><link>https://eventanalytics.ai/blog/conference-transcript-editing-workflow/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/conference-transcript-editing-workflow/</guid><category>Content and media</category><description>A conference transcript editing workflow in three passes: attribution, filler removal and a check on figures quoted from stage, plus a vendor test.</description></item><item><title>Turning session recordings into content assets your editorial team will actually use</title><link>https://eventanalytics.ai/blog/session-recordings-into-content-assets/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/session-recordings-into-content-assets/</guid><category>Content and media</category><description>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.</description></item><item><title>Choosing an evergreen and timely content mix for a seasonal event brand</title><link>https://eventanalytics.ai/blog/evergreen-and-timely-content-mix/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/evergreen-and-timely-content-mix/</guid><category>Content and media</category><description>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.</description></item><item><title>Setting a publishing cadence between editions that keeps a show brand alive</title><link>https://eventanalytics.ai/blog/publishing-cadence-between-editions/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/publishing-cadence-between-editions/</guid><category>Content and media</category><description>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.</description></item><item><title>Building a year round content calendar around a show that happens once</title><link>https://eventanalytics.ai/blog/year-round-content-calendar/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/year-round-content-calendar/</guid><category>Content and media</category><description>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.</description></item><item><title>Syndicating articles between sibling brands without wrecking either one in search</title><link>https://eventanalytics.ai/blog/syndicating-articles-between-sibling-brands/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/syndicating-articles-between-sibling-brands/</guid><category>Content and media</category><description>Syndicating articles between sibling brands splits one ranking three ways. Pick a canonical home, syndicate excerpts, and keep a register of what went where.</description></item><item><title>A content operations staffing model that survives eight shows a year</title><link>https://eventanalytics.ai/blog/content-operations-staffing-model/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/content-operations-staffing-model/</guid><category>Content and media</category><description>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.</description></item><item><title>Content repurposing rules that stop a portfolio filling up with thin duplicates</title><link>https://eventanalytics.ai/blog/content-repurposing-rules/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/content-repurposing-rules/</guid><category>Content and media</category><description>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.</description></item><item><title>Producing vertical clips from conference footage shot for a wide stage</title><link>https://eventanalytics.ai/blog/vertical-clips-from-conference-footage/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/vertical-clips-from-conference-footage/</guid><category>Content and media</category><description>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.</description></item><item><title>Getting speaker release and recording rights settled before you clip anything</title><link>https://eventanalytics.ai/blog/speaker-release-and-recording-rights/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/speaker-release-and-recording-rights/</guid><category>Content and media</category><description>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.</description></item><item><title>Video clipping from session recordings without burning a week of editor time</title><link>https://eventanalytics.ai/blog/video-clipping-from-session-recordings/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/video-clipping-from-session-recordings/</guid><category>Content and media</category><description>Video clipping from session recordings costs editor hours in selection, not in editing. Write the selection rule first, then measure cost per published clip.</description></item><item><title>How to run editorial operations across event brands without duplicating work</title><link>https://eventanalytics.ai/blog/editorial-operations-across-event-brands/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/editorial-operations-across-event-brands/</guid><category>Content and media</category><description>Editorial operations across event brands duplicate work invisibly. A commissioning ledger makes the repeat countable before anyone argues about headcount.</description></item><item><title>Numeric consistency checks that catch a wrong figure before publication</title><link>https://eventanalytics.ai/blog/numeric-consistency-checks/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/numeric-consistency-checks/</guid><category>AI for organisers</category><description>Numeric consistency checks parse every figure out of generated text, recompute it from the same aggregate, and fail the response when the two disagree.</description></item><item><title>Hallucination rate measurement for an assistant that answers with numbers</title><link>https://eventanalytics.ai/blog/hallucination-rate-measurement/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/hallucination-rate-measurement/</guid><category>AI for organisers</category><description>Hallucination rate measurement needs a stated unit, a frozen sample and a confidence interval, because a rate graded off thirty answers resolves almost nothing.</description></item><item><title>How hallucinated metrics get into AI reports and who notices last</title><link>https://eventanalytics.ai/blog/hallucinated-metrics-in-ai-reports/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/hallucinated-metrics-in-ai-reports/</guid><category>AI for organisers</category><description>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.</description></item><item><title>Writing an AI summary of show metrics that survives a line by line check</title><link>https://eventanalytics.ai/blog/ai-summary-of-show-metrics/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/ai-summary-of-show-metrics/</guid><category>AI for organisers</category><description>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.</description></item><item><title>Building provenance for AI generated numbers into every report line</title><link>https://eventanalytics.ai/blog/provenance-for-ai-generated-numbers/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/provenance-for-ai-generated-numbers/</guid><category>AI for organisers</category><description>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.</description></item><item><title>Grounding AI summaries in aggregates the reader can check themselves</title><link>https://eventanalytics.ai/blog/grounding-ai-summaries-in-aggregates/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/grounding-ai-summaries-in-aggregates/</guid><category>AI for organisers</category><description>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.</description></item><item><title>Verifying an AI generated query before anyone quotes the answer</title><link>https://eventanalytics.ai/blog/verifying-an-ai-generated-query/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/verifying-an-ai-generated-query/</guid><category>AI for organisers</category><description>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.</description></item><item><title>Deciding where AI is the wrong tool for an event data problem</title><link>https://eventanalytics.ai/blog/where-ai-is-the-wrong-tool/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/where-ai-is-the-wrong-tool/</guid><category>AI for organisers</category><description>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.</description></item><item><title>What text to SQL accuracy benchmarks tell an event data team</title><link>https://eventanalytics.ai/blog/text-to-sql-accuracy-benchmarks/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/text-to-sql-accuracy-benchmarks/</guid><category>AI for organisers</category><description>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.</description></item><item><title>Why models get arithmetic wrong and what to compute in SQL instead</title><link>https://eventanalytics.ai/blog/why-models-get-arithmetic-wrong/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/why-models-get-arithmetic-wrong/</guid><category>AI for organisers</category><description>Why models get arithmetic wrong matters for event reporting, because a percentage the model computed looks identical to one the warehouse computed.</description></item><item><title>When rules beat a model for questions an event team asks daily</title><link>https://eventanalytics.ai/blog/when-rules-beat-a-model/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/when-rules-beat-a-model/</guid><category>AI for organisers</category><description>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.</description></item><item><title>Measuring retrieval quality separately from the answer the model writes</title><link>https://eventanalytics.ai/blog/measuring-retrieval-quality/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/measuring-retrieval-quality/</guid><category>AI for organisers</category><description>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.</description></item><item><title>Why hybrid keyword and vector search beats embeddings alone on event documents</title><link>https://eventanalytics.ai/blog/hybrid-keyword-and-vector-search/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/hybrid-keyword-and-vector-search/</guid><category>AI for organisers</category><description>Hybrid keyword and vector search wins on event documents because stand numbers, hall codes and product references are exactly what an embedding blurs away.</description></item><item><title>Picking a chunking strategy for documents an event team actually keeps</title><link>https://eventanalytics.ai/blog/chunking-strategy-for-documents/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/chunking-strategy-for-documents/</guid><category>AI for organisers</category><description>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.</description></item><item><title>Retrieval augmented generation for organisers working from their own documents</title><link>https://eventanalytics.ai/blog/retrieval-augmented-generation-for-organisers/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/retrieval-augmented-generation-for-organisers/</guid><category>AI for organisers</category><description>Retrieval augmented generation for organisers means indexing post-show reports and board packs nobody rereads, then making each answer name its file and page.</description></item><item><title>Offline evaluation versus live monitoring for an assistant in daily use</title><link>https://eventanalytics.ai/blog/offline-evaluation-versus-live-monitoring/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/offline-evaluation-versus-live-monitoring/</guid><category>AI for organisers</category><description>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.</description></item><item><title>Regression testing AI features when the model underneath keeps changing</title><link>https://eventanalytics.ai/blog/regression-testing-ai-features/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/regression-testing-ai-features/</guid><category>AI for organisers</category><description>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.</description></item><item><title>How far to trust LLM as judge reliability when grading your assistant</title><link>https://eventanalytics.ai/blog/llm-as-judge-reliability/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/llm-as-judge-reliability/</guid><category>AI for organisers</category><description>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.</description></item><item><title>Building an evaluation set for an event assistant from real questions</title><link>https://eventanalytics.ai/blog/evaluation-set-for-event-assistant/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/evaluation-set-for-event-assistant/</guid><category>AI for organisers</category><description>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.</description></item><item><title>Natural language querying of event data and what it actually gets right</title><link>https://eventanalytics.ai/blog/natural-language-querying-event-data/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/natural-language-querying-event-data/</guid><category>AI for organisers</category><description>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.</description></item><item><title>How no shows in audited attendance change the number an auditor signs</title><link>https://eventanalytics.ai/blog/no-shows-in-audited-attendance/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/no-shows-in-audited-attendance/</guid><category>Standards and research</category><description>How no shows in audited attendance work: the standard counts arrivals only, the certificate hides the gap, and absence can cost the international label.</description></item><item><title>Whether exhibitor staff count in attendance figures your show publishes</title><link>https://eventanalytics.ai/blog/exhibitor-staff-in-attendance/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/exhibitor-staff-in-attendance/</guid><category>Standards and research</category><description>Whether exhibitor staff count in attendance: the standard keeps them out of visitors, puts them inside total attendance, and gives the certificate no box.</description></item><item><title>Counting unique attendees versus visits without inflating your headline number</title><link>https://eventanalytics.ai/blog/unique-attendees-versus-visits/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/unique-attendees-versus-visits/</guid><category>Standards and research</category><description>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.</description></item><item><title>Verified versus registered attendance and the gap between those two numbers</title><link>https://eventanalytics.ai/blog/verified-versus-registered-attendance/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/verified-versus-registered-attendance/</guid><category>Standards and research</category><description>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.</description></item><item><title>Audit frequency across exhibition editions and what keeps a UFI label alive</title><link>https://eventanalytics.ai/blog/audit-frequency-exhibition-editions/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/audit-frequency-exhibition-editions/</guid><category>Standards and research</category><description>Audit frequency across exhibition editions under UFI rules: the every other edition cadence, the new entrant exception, and the six month certificate deadline.</description></item><item><title>The audit evidence your registration file has to produce on request</title><link>https://eventanalytics.ai/blog/audit-evidence-registration-file/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/audit-evidence-registration-file/</guid><category>Standards and research</category><description>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.</description></item><item><title>Choosing an event auditor from the UFI accredited list without surprises</title><link>https://eventanalytics.ai/blog/choosing-an-event-auditor/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/choosing-an-event-auditor/</guid><category>Standards and research</category><description>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.</description></item><item><title>Event audit scope limits and the questions an auditor will not answer</title><link>https://eventanalytics.ai/blog/event-audit-scope-limits/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/event-audit-scope-limits/</guid><category>Standards and research</category><description>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.</description></item><item><title>Reading a benchmark study sample definition before you quote the number</title><link>https://eventanalytics.ai/blog/benchmark-study-sample-definition/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/benchmark-study-sample-definition/</guid><category>Standards and research</category><description>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.</description></item><item><title>Booth size unit conversion errors that quietly corrupt a portfolio roll up</title><link>https://eventanalytics.ai/blog/booth-size-unit-conversion-errors/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/booth-size-unit-conversion-errors/</guid><category>Standards and research</category><description>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.</description></item><item><title>Gross versus net exhibition space and the ratio worth tracking yourself</title><link>https://eventanalytics.ai/blog/gross-versus-net-exhibition-space/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/gross-versus-net-exhibition-space/</guid><category>Standards and research</category><description>Gross versus net exhibition space are reported by two different parties for different purposes, and the ratio between them moves when the denominator changes.</description></item><item><title>Converting net square metres to square feet without breaking your benchmark</title><link>https://eventanalytics.ai/blog/net-square-metres-to-square-feet/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/net-square-metres-to-square-feet/</guid><category>Standards and research</category><description>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.</description></item><item><title>Net square metres of exhibition space and what an auditor counts</title><link>https://eventanalytics.ai/blog/net-square-metres-exhibition-space/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/net-square-metres-exhibition-space/</guid><category>Standards and research</category><description>Net square metres of exhibition space is contracted floor occupied by exhibitors, paid or unpaid, indoors and outdoors, with the last two reported apart.</description></item><item><title>Trade versus consumer show counting rules and where the evidence diverges</title><link>https://eventanalytics.ai/blog/trade-versus-consumer-show-counting/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/trade-versus-consumer-show-counting/</guid><category>Standards and research</category><description>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.</description></item><item><title>Participants versus visitors terminology and why the broader word creeps in</title><link>https://eventanalytics.ai/blog/participants-versus-visitors-terminology/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/participants-versus-visitors-terminology/</guid><category>Standards and research</category><description>Participants versus visitors terminology matters because participant has no published definition, so the bucket widens each year nobody records its contents.</description></item><item><title>Why two shows in one sector report attendance so differently</title><link>https://eventanalytics.ai/blog/why-two-shows-report-differently/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/why-two-shows-report-differently/</guid><category>Standards and research</category><description>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.</description></item><item><title>Exhibition terminology standards and the words organisers keep using differently</title><link>https://eventanalytics.ai/blog/exhibition-terminology-standards/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/exhibition-terminology-standards/</guid><category>Standards and research</category><description>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.</description></item><item><title>How comp and guest badges appear on an audited attendance certificate</title><link>https://eventanalytics.ai/blog/comp-and-guest-badges/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/comp-and-guest-badges/</guid><category>Standards and research</category><description>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.</description></item><item><title>What an exhibition attendance audit actually checks before the certificate is signed</title><link>https://eventanalytics.ai/blog/exhibition-attendance-audit/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/exhibition-attendance-audit/</guid><category>Standards and research</category><description>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.</description></item><item><title>Days to open as the axis when a show moves in the calendar</title><link>https://eventanalytics.ai/blog/days-to-open-axis/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/days-to-open-axis/</guid><category>Forecasting methods</category><description>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.</description></item><item><title>The Gompertz growth curve fits a registration campaign the logistic cannot</title><link>https://eventanalytics.ai/blog/gompertz-growth-curve/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/gompertz-growth-curve/</guid><category>Forecasting methods</category><description>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.</description></item><item><title>Booking curve principal components compress a decade of editions into two numbers</title><link>https://eventanalytics.ai/blog/booking-curve-principal-components/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/booking-curve-principal-components/</guid><category>Forecasting methods</category><description>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.</description></item><item><title>Penalised spline forecasting for pacing curves that only have five editions behind them</title><link>https://eventanalytics.ai/blog/penalised-spline-forecasting/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/penalised-spline-forecasting/</guid><category>Forecasting methods</category><description>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.</description></item><item><title>Monotone regression splines keep a cumulative registration curve from going backwards</title><link>https://eventanalytics.ai/blog/monotone-regression-splines/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/monotone-regression-splines/</guid><category>Forecasting methods</category><description>Cumulative registrations never fall, so a smoother that dips is wrong. Monotone regression splines and the PAVA pass impose the constraint before you forecast.</description></item><item><title>Fitting a booking curve to five editions with a three parameter logistic</title><link>https://eventanalytics.ai/blog/fitting-a-booking-curve/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/fitting-a-booking-curve/</guid><category>Forecasting methods</category><description>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.</description></item><item><title>Pickup model diagnostics that tell you which form to trust this year</title><link>https://eventanalytics.ai/blog/pickup-model-diagnostics/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/pickup-model-diagnostics/</guid><category>Forecasting methods</category><description>Pickup model diagnostics settle the additive versus multiplicative argument with residuals from your own closed editions instead of an opinion in the meeting.</description></item><item><title>Prediction interval coverage is worse than the label claims with five editions</title><link>https://eventanalytics.ai/blog/prediction-interval-coverage/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/prediction-interval-coverage/</guid><category>Forecasting methods</category><description>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.</description></item><item><title>The multiplicative pickup model scales your count by a historical ratio</title><link>https://eventanalytics.ai/blog/multiplicative-pickup-model/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/multiplicative-pickup-model/</guid><category>Forecasting methods</category><description>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.</description></item><item><title>Temporal hierarchy forecasting reconciles the weekly pace with the annual number</title><link>https://eventanalytics.ai/blog/temporal-hierarchy-forecasting/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/temporal-hierarchy-forecasting/</guid><category>Forecasting methods</category><description>Temporal hierarchy forecasting aggregates one series to several frequencies, forecasts each, then reconciles. A 710 registration disagreement settles at 14,370.</description></item><item><title>Bottom up versus top down forecasting for a portfolio of eight shows</title><link>https://eventanalytics.ai/blog/bottom-up-versus-top-down/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/bottom-up-versus-top-down/</guid><category>Forecasting methods</category><description>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.</description></item><item><title>Hierarchical forecast reconciliation makes show and portfolio numbers add up</title><link>https://eventanalytics.ai/blog/hierarchical-forecast-reconciliation/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/hierarchical-forecast-reconciliation/</guid><category>Forecasting methods</category><description>Hierarchical forecast reconciliation projects base forecasts onto the coherent space, so a 500 registration gap between show sum and portfolio total disappears.</description></item><item><title>Pooled panel regression turns eight shows and five years into forty rows</title><link>https://eventanalytics.ai/blog/pooled-panel-regression/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/pooled-panel-regression/</guid><category>Forecasting methods</category><description>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.</description></item><item><title>A global forecasting model trained on every show in the portfolio at once</title><link>https://eventanalytics.ai/blog/global-forecasting-model/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/global-forecasting-model/</guid><category>Forecasting methods</category><description>A global forecasting model fits one function across every show. The budget that buys three weeks of memory locally buys twenty four globally.</description></item><item><title>Borrowing strength across shows when no single show has enough history</title><link>https://eventanalytics.ai/blog/borrowing-strength-across-shows/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/borrowing-strength-across-shows/</guid><category>Forecasting methods</category><description>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.</description></item><item><title>A shrinkage estimator pulls one noisy show forecast toward the portfolio mean</title><link>https://eventanalytics.ai/blog/shrinkage-estimator/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/shrinkage-estimator/</guid><category>Forecasting methods</category><description>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.</description></item><item><title>Overfitting short time series is easy when every model fits five points</title><link>https://eventanalytics.ai/blog/overfitting-short-time-series/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/overfitting-short-time-series/</guid><category>Forecasting methods</category><description>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.</description></item><item><title>Forecasting with five observations and the parameter budget that leaves you</title><link>https://eventanalytics.ai/blog/forecasting-with-five-observations/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/forecasting-with-five-observations/</guid><category>Forecasting methods</category><description>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.</description></item><item><title>Aligning booking windows when one edition opened registration eleven weeks late</title><link>https://eventanalytics.ai/blog/aligning-booking-windows/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/aligning-booking-windows/</guid><category>Forecasting methods</category><description>Aligning booking windows when editions had different runways: rescale to fraction of window elapsed, or truncate, and the halfway test that decides which.</description></item><item><title>How the additive pickup model forecasts your final registration number</title><link>https://eventanalytics.ai/blog/additive-pickup-model/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/additive-pickup-model/</guid><category>Forecasting methods</category><description>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.</description></item><item><title>Questions to settle before a Marketo event integration goes live</title><link>https://eventanalytics.ai/blog/marketo-event-integration/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/marketo-event-integration/</guid><category>Integrations</category><description>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.</description></item><item><title>Handling Dynamics 365 API throttling during a show week data load</title><link>https://eventanalytics.ai/blog/dynamics-365-api-throttling/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/dynamics-365-api-throttling/</guid><category>Integrations</category><description>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.</description></item><item><title>Working inside HubSpot API rate limits when a registration file lands</title><link>https://eventanalytics.ai/blog/hubspot-api-rate-limits/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/hubspot-api-rate-limits/</guid><category>Integrations</category><description>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.</description></item><item><title>Sizing an event data sync against Salesforce API limits</title><link>https://eventanalytics.ai/blog/salesforce-api-limits/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/salesforce-api-limits/</guid><category>Integrations</category><description>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.</description></item><item><title>What the ExpoFP floorplan API gives you and what it does not</title><link>https://eventanalytics.ai/blog/expofp-floorplan-api/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/expofp-floorplan-api/</guid><category>Integrations</category><description>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.</description></item><item><title>Planning an a2z Events data export across several shows and years</title><link>https://eventanalytics.ai/blog/a2z-events-data-export/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/a2z-events-data-export/</guid><category>Integrations</category><description>An a2z Events data export across several editions is mostly a booth numbering problem. Separate a renumbered hall from an exhibitor who genuinely moved.</description></item><item><title>Loading MYS exhibitor data without losing the booth link</title><link>https://eventanalytics.ai/blog/map-your-show-exhibitor-data/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/map-your-show-exhibitor-data/</guid><category>Integrations</category><description>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.</description></item><item><title>Making an SFTP file drop integration survive a badly timed upload</title><link>https://eventanalytics.ai/blog/sftp-file-drop-integration/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/sftp-file-drop-integration/</guid><category>Integrations</category><description>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.</description></item><item><title>Reading the Swapcard API rate limits before you build the nightly pull</title><link>https://eventanalytics.ai/blog/swapcard-api-rate-limits/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/swapcard-api-rate-limits/</guid><category>Integrations</category><description>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.</description></item><item><title>Choosing webhooks versus polling for an event registration feed</title><link>https://eventanalytics.ai/blog/webhooks-versus-polling/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/webhooks-versus-polling/</guid><category>Integrations</category><description>Webhooks versus polling is a latency decision rather than a completeness one, and an event registration feed usually needs both running side by side.</description></item><item><title>Syncing an association management system with the show registration platform</title><link>https://eventanalytics.ai/blog/association-management-system-sync/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/association-management-system-sync/</guid><category>Integrations</category><description>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.</description></item><item><title>What a Zuant lead capture export looks like when it reaches the CRM</title><link>https://eventanalytics.ai/blog/zuant-lead-capture-export/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/zuant-lead-capture-export/</guid><category>Integrations</category><description>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.</description></item><item><title>Getting GES exhibitor ordering data out and lined up with your booth list</title><link>https://eventanalytics.ai/blog/ges-exhibitor-ordering-data/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/ges-exhibitor-ordering-data/</guid><category>Integrations</category><description>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.</description></item><item><title>Cvent Passkey reservation data and what to settle before you model room blocks</title><link>https://eventanalytics.ai/blog/cvent-passkey-reservation-data/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/cvent-passkey-reservation-data/</guid><category>Integrations</category><description>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.</description></item><item><title>Joining onPeak housing data to the registration file</title><link>https://eventanalytics.ai/blog/onpeak-housing-data/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/onpeak-housing-data/</guid><category>Integrations</category><description>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.</description></item><item><title>Mapping an ExpoPlatform data export onto your own event schema</title><link>https://eventanalytics.ai/blog/expoplatform-data-export/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/expoplatform-data-export/</guid><category>Integrations</category><description>An ExpoPlatform data export arrives with one identifier space across modules, which helps until you ask which of those identifiers survives the next edition.</description></item><item><title>Using the Brella REST API to pull meeting and lead data</title><link>https://eventanalytics.ai/blog/brella-rest-api/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/brella-rest-api/</guid><category>Integrations</category><description>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.</description></item><item><title>What a Grip matchmaking export tells you about meeting demand</title><link>https://eventanalytics.ai/blog/grip-matchmaking-export/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/grip-matchmaking-export/</guid><category>Integrations</category><description>A Grip matchmaking export mixes requests, acceptances and held meetings in one table, and the permission settings decide who could be recommended at all.</description></item><item><title>Pulling Stova registration data into a portfolio level report</title><link>https://eventanalytics.ai/blog/stova-registration-data/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/stova-registration-data/</guid><category>Integrations</category><description>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.</description></item><item><title>How to plan a Cvent data export you can actually reuse</title><link>https://eventanalytics.ai/blog/cvent-data-export/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/cvent-data-export/</guid><category>Integrations</category><description>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.</description></item><item><title>Merge versus insert overwrite for loading a completed show edition</title><link>https://eventanalytics.ai/blog/merge-versus-insert-overwrite/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/merge-versus-insert-overwrite/</guid><category>Data platform</category><description>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.</description></item><item><title>Idempotent warehouse loads mean you can rerun show day without fear</title><link>https://eventanalytics.ai/blog/idempotent-warehouse-loads/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/idempotent-warehouse-loads/</guid><category>Data platform</category><description>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.</description></item><item><title>Running an annual cadence data pipeline that sits idle for eleven months</title><link>https://eventanalytics.ai/blog/annual-cadence-data-pipeline/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/annual-cadence-data-pipeline/</guid><category>Data platform</category><description>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.</description></item><item><title>Designing burst shaped ingestion pipelines for a show that peaks in four days</title><link>https://eventanalytics.ai/blog/burst-shaped-ingestion-pipelines/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/burst-shaped-ingestion-pipelines/</guid><category>Data platform</category><description>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.</description></item><item><title>Deciding bronze layer retention when a show runs once a year</title><link>https://eventanalytics.ai/blog/bronze-layer-retention/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/bronze-layer-retention/</guid><category>Data platform</category><description>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.</description></item><item><title>Medallion architecture for event data and where the layers earn their keep</title><link>https://eventanalytics.ai/blog/medallion-architecture-for-event-data/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/medallion-architecture-for-event-data/</guid><category>Data platform</category><description>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.</description></item><item><title>When a factless fact table gives you the coverage denominator</title><link>https://eventanalytics.ai/blog/factless-fact-table-coverage/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/factless-fact-table-coverage/</guid><category>Data platform</category><description>A factless fact table coverage row exists for every eligible pairing, so exhibitors nobody scanned and sessions nobody entered get a denominator.</description></item><item><title>A session attendance fact table needs both a scan and a capacity</title><link>https://eventanalytics.ai/blog/session-attendance-fact-table/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/session-attendance-fact-table/</guid><category>Data platform</category><description>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.</description></item><item><title>Category exclusivity pricing means charging for the competitors you turn away</title><link>https://eventanalytics.ai/blog/category-exclusivity-pricing/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/category-exclusivity-pricing/</guid><category>Sponsorship</category><description>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.</description></item><item><title>The intangible sponsorship value multiplier is where most valuations go wrong</title><link>https://eventanalytics.ai/blog/intangible-sponsorship-value-multiplier/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/intangible-sponsorship-value-multiplier/</guid><category>Sponsorship</category><description>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.</description></item><item><title>Pricing sponsorship without comparables when the asset has never been sold</title><link>https://eventanalytics.ai/blog/pricing-sponsorship-without-comparables/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/pricing-sponsorship-without-comparables/</guid><category>Sponsorship</category><description>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.</description></item><item><title>Three sponsorship valuation methods and when each one gives a defensible number</title><link>https://eventanalytics.ai/blog/sponsorship-valuation-methods/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/sponsorship-valuation-methods/</guid><category>Sponsorship</category><description>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.</description></item><item><title>Sponsorship tier design fails when the middle tier has nothing distinctive</title><link>https://eventanalytics.ai/blog/sponsorship-tier-design/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/sponsorship-tier-design/</guid><category>Sponsorship</category><description>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.</description></item><item><title>What to report instead of AVE when the sponsor wants a dollar figure</title><link>https://eventanalytics.ai/blog/what-to-report-instead-of-ave/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/what-to-report-instead-of-ave/</guid><category>Sponsorship</category><description>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.</description></item><item><title>The PR multiplier for sponsorship has no evidence behind the number three</title><link>https://eventanalytics.ai/blog/pr-multiplier-for-sponsorship/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/pr-multiplier-for-sponsorship/</guid><category>Sponsorship</category><description>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.</description></item><item><title>Advertising value equivalency for events is the number sponsors stopped believing</title><link>https://eventanalytics.ai/blog/advertising-value-equivalency-for-events/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/advertising-value-equivalency-for-events/</guid><category>Sponsorship</category><description>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.</description></item><item><title>Sponsorship sell through rate is the number your rate card is hiding</title><link>https://eventanalytics.ai/blog/sponsorship-sell-through-rate/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/sponsorship-sell-through-rate/</guid><category>Sponsorship</category><description>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.</description></item><item><title>Which sponsor renewal predictors actually appear in your own data</title><link>https://eventanalytics.ai/blog/sponsor-renewal-predictors/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/sponsor-renewal-predictors/</guid><category>Sponsorship</category><description>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.</description></item><item><title>A sponsor renewal rate definition that survives a board meeting</title><link>https://eventanalytics.ai/blog/sponsor-renewal-rate-definition/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/sponsor-renewal-rate-definition/</guid><category>Sponsorship</category><description>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.</description></item><item><title>Enhanced directory listing pricing works when you can show the click difference</title><link>https://eventanalytics.ai/blog/enhanced-directory-listing-pricing/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/enhanced-directory-listing-pricing/</guid><category>Sponsorship</category><description>Enhanced directory listing pricing rests on the view difference the upgrade causes. The raw gap between upgraded and standard listings is mostly self-selection.</description></item><item><title>Sponsored email pricing follows deliverability before it follows list size</title><link>https://eventanalytics.ai/blog/sponsored-email-pricing/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/sponsored-email-pricing/</guid><category>Sponsorship</category><description>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.</description></item><item><title>Sponsorship inventory sizing decides whether your assets sell or sit</title><link>https://eventanalytics.ai/blog/sponsorship-inventory-sizing/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/sponsorship-inventory-sizing/</guid><category>Sponsorship</category><description>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.</description></item><item><title>The attendance denominator for sponsorship metrics decides every number above it</title><link>https://eventanalytics.ai/blog/attendance-denominator-for-sponsorship-metrics/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/attendance-denominator-for-sponsorship-metrics/</guid><category>Sponsorship</category><description>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.</description></item><item><title>Double counting sponsorship impressions is how a package reaches unbelievable reach</title><link>https://eventanalytics.ai/blog/double-counting-sponsorship-impressions/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/double-counting-sponsorship-impressions/</guid><category>Sponsorship</category><description>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.</description></item><item><title>Sponsorship impression error bars belong on the report you send the sponsor</title><link>https://eventanalytics.ai/blog/sponsorship-impression-error-bars/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/sponsorship-impression-error-bars/</guid><category>Sponsorship</category><description>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.</description></item><item><title>Comparing sponsorship assets on CPM makes a lanyard and an email argue fairly</title><link>https://eventanalytics.ai/blog/comparing-sponsorship-assets-on-cpm/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/comparing-sponsorship-assets-on-cpm/</guid><category>Sponsorship</category><description>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.</description></item><item><title>Run a sponsorship inventory audit before you print another rate card</title><link>https://eventanalytics.ai/blog/sponsorship-inventory-audit/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/sponsorship-inventory-audit/</guid><category>Sponsorship</category><description>A sponsorship inventory audit records every sellable asset with its unit count, exposure window and price, including the ones missing from the rate card.</description></item><item><title>Computer vision people counting on a show floor and its failure modes</title><link>https://eventanalytics.ai/blog/computer-vision-people-counting/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/computer-vision-people-counting/</guid><category>On-site analytics</category><description>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.</description></item><item><title>Where lidar people counting accuracy holds up and where crowds break it</title><link>https://eventanalytics.ai/blog/lidar-people-counting-accuracy/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/lidar-people-counting-accuracy/</guid><category>On-site analytics</category><description>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.</description></item><item><title>What BLE beacon tracking accuracy means on a crowded exhibition floor</title><link>https://eventanalytics.ai/blog/ble-beacon-tracking-accuracy/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/ble-beacon-tracking-accuracy/</guid><category>On-site analytics</category><description>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.</description></item><item><title>Why heat map normalization changes which part of the hall looks busy</title><link>https://eventanalytics.ai/blog/heat-map-normalization/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/heat-map-normalization/</guid><category>On-site analytics</category><description>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.</description></item><item><title>Finding dead zones on a show floor before the exhibitors in them complain</title><link>https://eventanalytics.ai/blog/dead-zones-on-show-floor/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/dead-zones-on-show-floor/</guid><category>On-site analytics</category><description>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.</description></item><item><title>General liability limit checking when the show accepts two different limit structures</title><link>https://eventanalytics.ai/blog/general-liability-limit-checking/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/general-liability-limit-checking/</guid><category>Onboarding operations</category><description>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.</description></item><item><title>Insurance certificate expiration tracking against move in and move out dates</title><link>https://eventanalytics.ai/blog/insurance-certificate-expiration-tracking/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/insurance-certificate-expiration-tracking/</guid><category>Onboarding operations</category><description>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.</description></item><item><title>Certificate holder versus additional insured and why ops teams confuse the two</title><link>https://eventanalytics.ai/blog/certificate-holder-versus-additional-insured/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/certificate-holder-versus-additional-insured/</guid><category>Onboarding operations</category><description>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.</description></item><item><title>Additional insured verification for shows where three parties must be named</title><link>https://eventanalytics.ai/blog/additional-insured-verification/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/additional-insured-verification/</guid><category>Onboarding operations</category><description>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.</description></item><item><title>Reading an exhibitor certificate of insurance for the six fields that decide access</title><link>https://eventanalytics.ai/blog/exhibitor-certificate-of-insurance/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/exhibitor-certificate-of-insurance/</guid><category>Onboarding operations</category><description>An exhibitor certificate of insurance is checked field by field: insured name, carrier, policy number, limits, additional insured wording and expiry date.</description></item><item><title>Calculating an exhibitor compliance rate that survives an audit before move in</title><link>https://eventanalytics.ai/blog/exhibitor-compliance-rate/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/exhibitor-compliance-rate/</guid><category>Onboarding operations</category><description>An exhibitor compliance rate is compliant exhibitors over contracted exhibitors at a stated cutoff, and the cutoff you pick moves the answer 39 points.</description></item><item><title>Measuring exhibitor onboarding cycle time from countersignature to show ready status</title><link>https://eventanalytics.ai/blog/exhibitor-onboarding-cycle-time/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/exhibitor-onboarding-cycle-time/</guid><category>Onboarding operations</category><description>Exhibitor onboarding cycle time is elapsed days from countersignature to show ready. Report P50 and P90 together, because the median hides the tail.</description></item><item><title>Measuring exhibitor service kit adoption with four counts you already have</title><link>https://eventanalytics.ai/blog/exhibitor-service-kit-adoption/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/exhibitor-service-kit-adoption/</guid><category>Onboarding operations</category><description>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.</description></item><item><title>Defining exhibitor onboarding funnel stages so drop off is visible per stage</title><link>https://eventanalytics.ai/blog/exhibitor-onboarding-funnel-stages/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/exhibitor-onboarding-funnel-stages/</guid><category>Onboarding operations</category><description>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.</description></item><item><title>Exhibitor manual design that treats the manual as a product with users</title><link>https://eventanalytics.ai/blog/exhibitor-manual-design/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/exhibitor-manual-design/</guid><category>Onboarding operations</category><description>Exhibitor manual design works better as software: one required action per screen, sections filtered by booth type, and instrumentation on what actually gets opened.</description></item><item><title>Exhibitor appointed contractor approval is a second insurance workflow hiding inside the first</title><link>https://eventanalytics.ai/blog/exhibitor-appointed-contractor-approval/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/exhibitor-appointed-contractor-approval/</guid><category>Onboarding operations</category><description>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.</description></item><item><title>Booth services order extraction turns a stack of pdf forms into a schedule</title><link>https://eventanalytics.ai/blog/booth-services-order-extraction/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/booth-services-order-extraction/</guid><category>Onboarding operations</category><description>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.</description></item><item><title>Discount deadline compliance and what the late rate really costs your exhibitors</title><link>https://eventanalytics.ai/blog/discount-deadline-compliance/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/discount-deadline-compliance/</guid><category>Onboarding operations</category><description>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.</description></item><item><title>The advance warehouse cutoff date is the deadline that costs exhibitors most</title><link>https://eventanalytics.ai/blog/advance-warehouse-cutoff-date/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/advance-warehouse-cutoff-date/</guid><category>Onboarding operations</category><description>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.</description></item><item><title>Building an exhibitor deadline calendar from a service kit nobody reads</title><link>https://eventanalytics.ai/blog/exhibitor-deadline-calendar/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/exhibitor-deadline-calendar/</guid><category>Onboarding operations</category><description>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.</description></item><item><title>Foreign exhibitor tax forms and why the W9 workflow breaks at the border</title><link>https://eventanalytics.ai/blog/foreign-exhibitor-tax-forms/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/foreign-exhibitor-tax-forms/</guid><category>Onboarding operations</category><description>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.</description></item><item><title>Backup withholding on exhibitor payments and the paperwork gap that triggers it</title><link>https://eventanalytics.ai/blog/backup-withholding-on-exhibitor-payments/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/backup-withholding-on-exhibitor-payments/</guid><category>Onboarding operations</category><description>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.</description></item><item><title>TIN matching validation before an exhibitor payment file reaches accounts payable</title><link>https://eventanalytics.ai/blog/tin-matching-validation/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/tin-matching-validation/</guid><category>Onboarding operations</category><description>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.</description></item><item><title>Exhibitor W9 collection and the five fields that decide whether it is usable</title><link>https://eventanalytics.ai/blog/exhibitor-w9-collection/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/exhibitor-w9-collection/</guid><category>Onboarding operations</category><description>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.</description></item><item><title>Where the exhibitor onboarding process stalls between signed contract and move in</title><link>https://eventanalytics.ai/blog/exhibitor-onboarding-process/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/exhibitor-onboarding-process/</guid><category>Onboarding operations</category><description>Model the exhibitor onboarding process as dated states, measure median days resident in each one, and the stall becomes visible months before move-in.</description></item><item><title>An industry taxonomy mapping table beats forcing every show to renumber</title><link>https://eventanalytics.ai/blog/industry-taxonomy-mapping-table/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/industry-taxonomy-mapping-table/</guid><category>Data platform</category><description>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.</description></item><item><title>Drawing an event bus matrix before you model a single fact table</title><link>https://eventanalytics.ai/blog/event-bus-matrix/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/event-bus-matrix/</guid><category>Data platform</category><description>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.</description></item><item><title>Conformed dimensions across shows are what make a portfolio roll up work</title><link>https://eventanalytics.ai/blog/conformed-dimensions-across-shows/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/conformed-dimensions-across-shows/</guid><category>Data platform</category><description>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.</description></item><item><title>Modelling the venue and hall dimension when a show changes buildings</title><link>https://eventanalytics.ai/blog/venue-and-hall-dimension/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/venue-and-hall-dimension/</guid><category>Data platform</category><description>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.</description></item><item><title>Adding days to show open to your date dimension</title><link>https://eventanalytics.ai/blog/days-to-show-open/</link><guid isPermaLink="true">https://eventanalytics.ai/blog/days-to-show-open/</guid><category>Data platform</category><description>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.</description></item></channel></rss>
