Direct answer: An event landing page is not a poster. It needs its own URL, pre-show information, registration/inquiry form, QR/UTM, lead ownership, privacy consent and post-show follow-up. Acceptance is whether people can find it, register, reach the right owner and review the results—not whether it looks good.
This guide is for marketing, export/sales, product, IT, legal and website vendors at Changzhou manufacturers. It covers trade shows, customer days, open days and online launches: how to build and accept an event landing page. Information is current to 31 October 2026. It is public search/analytics documentation and project method, not a ranking, traffic or lead promise; the event, form, privacy, contracts and data definitions are confirmed case by case.
One primary URL per event; QR/UTM must distinguish channel/staff; collect only necessary form fields with clear consent; leads need an owner, SLA and post-show follow-up; update or retire the page after the event, not "valid forever".
When do you need a dedicated event page rather than a news/product page?
Large trade shows, launches, customer days and open days fit a dedicated event page; small routine news belongs on the news/product page. Judge by whether there is separate registration, agenda, booth/venue, time and follow-up.
Not every event needs a new page. A dedicated page fits an event with a clear time/place/registration/agenda/follow-up: trade show, customer day, open day, launch, online seminar. Routine company news or product updates fit the news/product page, avoiding a set of expired, duplicate event URLs. The page needs a lifecycle: live before the event, updated during it, reviewed/retired or turned into a recap afterwards.
| Scenario | Fits a dedicated page | Does not fit | Acceptance focus |
|---|---|---|---|
| Large trade show | Booth, agenda, registration/appointment, on-site activity | Only a booth photo | Booth/time/appointment/leads |
| Customer day/open day | Invitation, visit, check-in, confidentiality | Public registration without review | Invitation/list/privacy |
| Product launch | Launch/livestream/demo booking | A product page with a new title | Agenda/replay/demo |
| Online seminar | Registration, speakers, replay, materials | No registration/replay | Registration/attendance/materials |
| Routine news | No | A page for every news item | News list/internal links |
Scenario judgement is editorial; page structure, registration/invitation and privacy depend on the event type, company policy and contract.
What should the pre-show page contain?
At minimum: event name, time, venue/booth, products/agenda, registration/appointment, travel/entry, contact and FAQ. It must be searchable and shareable, not a poster.
The first job of the pre-show page is to help a customer decide whether to come, how to get there and who to meet. Include event name, date/time, venue/booth, address/travel, entry method, products/demos, agenda/speakers, registration/appointment, contact and FAQ. The title/H1/description should include event name + city/booth, not just "invitation". Changes must be updateable; after the event, retire it or mark "ended".
| Module | What to write | Evidence | Common gap |
|---|---|---|---|
| Event info | Name, time, venue/booth, address/travel, entry | Screenshot, map/venue link | Poster only/no booth number |
| Products/agenda | Products, demos, agenda/speakers, who should attend | Product/agenda table | "Stay tuned" with no content |
| Registration/appointment | Form, review/confirmation, quota/deadline | Form test, confirmation email | No confirmation after registration |
| Travel/entry | Metro/parking/badge/entry code/contact | FAQ, map | Cannot find the booth on site |
| Share/search | Title/description/OG/Event structured data | Source, share preview | Only "invitation" |
| Update/retire | Time/booth/agenda changes; recap/retire | Version/status | Expired page stays online |
The page checklist is editorial; Event structured data reference Google Event structured data, but display/indexing/ranking are not promised.
How should QR codes, UTM and forms be designed?
Use separate QR codes by channel/booth/staff and UTM for source. Collect only necessary fields with clear consent. Route leads by product/region/owner; do not send everything to one inbox.
The most common failure is "one QR code for everything", so nobody knows where a lead came from. QR/short links should distinguish show, booth, poster, sales card and online channel; UTM records source/medium/campaign/content; form fields should match follow-up needs (name, company, title, need/product, country/region, contact, consent), not ID cards or medical records. Route leads by product/region/owner, with a named owner and SLA for sales/distributors.
| Item | Suggested practice | Evidence | Common failure |
|---|---|---|---|
| QR code | One per channel/booth/staff; can be retired/retargeted | QR table, redirect test | One code for the whole show |
| UTM | Consistent source/medium/campaign/content | UTM table, report | Ad-hoc "expo" |
| Form fields | Necessary fields; product/need/country; consent | Field table, test submission | Too many fields/no consent |
| Lead routing | By product/region/owner; backup | Routing table, SLA | All to a group inbox |
| Privacy | Purpose/scope/retention/sharing/rights; revocable | Privacy text, consent record | Pre-ticked/no notice |
| Data quality | Deduplicate, invalid numbers, mark test leads | CRM rules, sampling | Counting tests as leads |
The QR/form/lead checklist is editorial; personal-information processing, consent, retention and sharing depend on the Personal Information Protection Law and company privacy policy; claims/cases/data must be true and verifiable under the Advertising Law.
How should post-show follow-up and review work?
Follow up by lead tier at 24/48/72 hours; send materials/replay/quote/sample; record invalid/duplicate/competitor; review qualified leads, meetings/samples/quotes and pipeline, not just scans.
The show is not over when the booth closes; lead follow-up starts. Set SLA by tier: A (clear need/budget/timing) within 24 hours, B within 48 hours, C within 72 hours or nurture; send materials/replay/quote/sample with templates and an owner. Record invalid, duplicate, competitor and test leads; do not treat scans as leads. Review qualified leads, meetings/samples/quotes, pipeline and cost per qualified lead.
| Action | What to do | Evidence | Common failure |
|---|---|---|---|
| Tiering | A/B/C by need/budget/timing/decision role | Tier rules, sample | All leads same tier |
| SLA | A 24h/B 48h/C 72h or nurture | CRM timestamp | Contacted a week later |
| Content | Materials/replay/quote/sample/meeting | Templates, send log | Only "thanks for visiting" |
| Data | Mark invalid/duplicate/competitor/test | CRM fields, sampling | Scan = lead |
| Review | Qualified leads, meetings/samples/quotes, pipeline, cost | Report, review meeting | Only scans/cards |
| Page | Recap/materials/retire/update | Page status/version | Expired page stays online |
The follow-up/review checklist is editorial; SLA, lead tiers, CRM and performance rules depend on the sales process; no lead, conversion or deal volume is promised.
Which data should you look at—and not look at?
Look at scans/forms/qualified leads/meetings/samples/quotes/pipeline and cost per qualified lead; do not look only at scans, business cards or pageviews. GA4 events must distinguish QR/forms/materials.
Event data should answer which channel/booth/customer type produced qualified leads. Record at least QR scans, page visits, form starts/submissions, material downloads, meeting bookings, qualified leads, samples/quotes, pipeline and cost. GA4 events/UTM need consistent naming; form submit/material download/meeting booking can be key events, but do not replace lead quality with pageviews or scans. Event cost includes booth/build/materials/travel/staff/page/ads; cost per qualified lead is more meaningful.
| Metric | How to use | Source | How not to use |
|---|---|---|---|
| Scans/visits | Channel/creative attractiveness | QR/GA4 | As lead count |
| Form submissions | Registration/appointment conversion | Form/CRM | Without removing tests/duplicates |
| Qualified leads | Confirmed by tier rules | CRM | All business cards are qualified |
| Meetings/samples/quotes | Sales progress | CRM/sales record | Page metrics only |
| Pipeline/deals | Business impact | CRM | Short-term attribution/credit fight |
| Cost per qualified lead | Compare events/channels | Cost table/CRM | Page production cost only |
Metrics/definitions are editorial; GA4 events reference GA4 event documentation; attribution, cost and pipeline depend on CRM/finance; no lead or deal is promised.
How should the event page be sequenced?
T-30 define goal/page/form/QR; T-14 content/invitations/testing; T-7 reminders/materials/training; during the show update/collect; 72 hours follow-up, 2-week review, 4-week update/retire.
Do not build the page a week before the show. Work backwards from T-30/T-14/T-7/show/post-show: define goal, audience, offer, form and lead routing; build page/content/QR/UTM; test registration/confirmation/notification; update on site/agenda/photos during the show; follow up by SLA and review after. Put page/form/QR/CRM owners in the event plan.
| Phase | Actions | Outputs | Owner |
|---|---|---|---|
| T-30 | Define goal/audience/offer, page/form/QR/UTM/lead routing | Event page plan, field table | Marketing/sales |
| T-14 | Page content/agenda/products/travel/FAQ; invitation/registration testing | Page, test record | Marketing/IT |
| T-7 | Reminders/confirmation/materials/QR/sales training | Reminders, materials, training | Marketing/sales |
| Show | On-site updates, scans/forms, meeting booking, exception handling | On-site log, leads | Sales/marketing |
| 72h after | Tier/follow-up/send materials/quote/sample; mark invalid/duplicate | CRM, follow-up log | Sales |
| 2–4 weeks | Review; recap/retire page; next improvements | Review table, page status | Marketing/sales |
The event cycle is editorial; timing, budget, staffing, privacy and contracts depend on the event plan.
Acceptance checklist
Accept eight items: URL/info, registration/form, QR/UTM, privacy consent, lead routing, post-show follow-up, data/review and page lifecycle. Each needs an owner and evidence.
The checklist can be shared by marketing, sales, product, IT, legal and vendors. The pass standard is not "the page looks good" but that customers can find it, register, reach the right owner, follow-up happens, data can be reviewed and expired content comes down.
| Check | Pass standard | Evidence | If failed |
|---|---|---|---|
| URL/info | Dedicated URL; event name/time/venue/booth/travel/contact complete | Page, screenshot | Add info/restructure |
| Registration/form | Submit/confirm/notify; necessary fields; test passes | Test submission, email | Fix form/notification |
| QR/UTM | Channel/booth/staff distinguishable; can retire | QR table, report | Rebuild code/naming |
| Privacy consent | Notice/consent/withdrawal/retention/sharing clear | Privacy text, record | Add consent/disable |
| Lead routing | By product/region/owner; backup/SLA | Routing table, CRM | Fix routing/train |
| Post-show follow-up | Tier/SLA/templates/sample/quote recorded | CRM timestamp | Add follow-up/review |
| Data/review | Scans/forms/qualified leads/meetings/samples/quotes/cost visible | Report, review meeting | Add definitions/data |
| Page lifecycle | Recap/retire/update after show; no expired misleading info | Status/version | Retire/recap |
The acceptance checklist is editorial; page, form, privacy, lead and data requirements depend on the event plan, CRM and contract.
Who should read this, who should not, and what decision does it support?
It fits Changzhou manufacturers attending trade shows/customer days/open days/launches. It does not fit teams without an event plan, lead follow-up or willingness to do more than a poster.
Who should read: marketing, export/sales, product, IT, legal and website vendors at Changzhou manufacturers; teams building a trade-show/customer-day/open-day/online-seminar page; anyone deciding "dedicated page or news page, how to split QR codes, what fields to collect, who owns leads, how to review after the show". Who should not: projects without a clear event/audience/offer; teams without sales follow-up/CRM/privacy processes; projects expecting one poster or QR code to replace the page/follow-up. Decisions supported: event page positioning, pre-show content, QR/UTM, forms/consent, lead routing, post-show follow-up, data review and page lifecycle.
Lingyi Information is a website and enterprise AI project services company, not an event organiser, CRM or law firm. This article does not replace the event contract, privacy policy, CRM or legal advice. Changzhou projects are confirmed case by case for remote or on-site work; Lingyi is one candidate, not a local office/team, and does not promise scans, leads, conversion or deals.
FAQ
Does an event page need its own URL?
For a large trade show, launch, customer day or open day with its own time/place/registration/agenda, yes. Routine news/small events can use the news/product page. The dedicated page needs a lifecycle: live before, updated during, recap/retire after.
Should each channel have its own QR code?
Yes, ideally by show/booth/poster/sales card/online channel, and it should be retireable/retargetable. That is how you know where a lead came from. One code for the whole show makes attribution and sales allocation difficult.
Which form fields should we collect?
What follow-up actually needs: name, company, title, need/product, country/region, contact, consent. Do not collect ID cards or medical records. More fields lower conversion; ask whether sales really needs each one.
Should the event page use Event structured data?
If the page is a real event (name/time/place/registration), follow Google's Event structured data documentation. It is not a ranking/display guarantee; update or retire the page if the event is cancelled or expired.
How soon should we follow up after the show?
Set SLA by lead tier, e.g. A within 24 hours, B within 48 hours, C within 72 hours or nurture; send materials/replay/quote/sample with templates and an owner. Confirm the SLA with the sales process.
How do we judge whether the event page worked?
Look at qualified leads, meetings/samples/quotes, pipeline and cost per qualified lead, not only scans/pageviews/business cards. The page works if people can register, leads reach the right owner, follow-up happens and data can be reviewed.
Bottom line
For a Changzhou manufacturer's event page, one primary URL per event, with pre-show information, registration, QR/UTM, privacy consent, lead routing, post-show follow-up, review and page lifecycle all accepted. Scans and pageviews are not leads; a good-looking page is not a successful event.
Method and limits
This article is public search/analytics documentation and project method, not a ranking/traffic/lead promise or legal advice for any event, page, channel, lead or conversion. It uses no unpublished client events, leads or contracts. Page structure, tables and event cycle are editorial suggestions; page/form/privacy/CRM/contract requirements depend on the company, platform documentation and legal counsel.
Sources
Information is current to 31 October 2026; each official/primary page governs its own rules and version.
- Google Search Central, Event structured data: developers.google.com. Event name/time/place/registration fields; display/indexing/ranking are not promised.
- Google Analytics Help, Events: support.google.com. Event/key-event definitions for forms, downloads and meeting bookings.
- Personal Information Protection Law of the PRC: npc.gov.cn. Notice, consent, minimisation and rights for personal information collected by forms/QR codes.
- Advertising Law of the PRC (2021 amendment): SAMR. Event/case/data claims must be true and verifiable; no false/absolute claims.