EVENTODIT.
EDITABLE WORK DOCUMENT

Lead, booking and entry connection log

Confirm storage and permissions by capture route, then record links and gaps across booking and check-in states.

Audience recruitment and promotionEvent-day operations
WHAT THIS TEMPLATE HELPS YOU PREPARE

A handover record of traceable lead, booking and entry routes for the same observed cohort

File formats
English XLSX · CSV (UTF-8)
Version
2.0
Editorial review
31 Oct 2026
Use this for
Use before linking AI conversations or lead capture with booking/check-in and after capture-route changes.

When to use it

Use before linking AI conversations or lead capture with booking/check-in and after capture-route changes.

Use only fictional work IDs in examples; keep real personal information in restricted systems. Verify features and retention in the actual account. Traceable conversions do not establish causal advertising impact.

Start with the guide: TikTok AI leads, event bookings and attendance measurement

Fill in the template step by step

When to use it

Test system connection and data scope before campaign launch; update before observation cutoffs and backups.

What to have ready

  • Actual account feature, permission and retention replies
  • Form, message and own-website routes and stores
  • Booking, cancellation, check-in and deduplication definitions
  • Permitted fictional test IDs, cohort/cutoff and backup plan

  1. Verify storage, admin access and retention for every capture route.

  2. Use permitted fictional IDs to test lead receipt and return signals separately.

  3. Align ownership and rules for booking, cancellation, entry and re-entry.

  4. Record traceable routes and gaps for the same cohort and cutoff, then arrange authorised backup and handover.

Worked example

Fictional example, not an actual event or supplier record

Eight columns · scroll horizontally to view the complete worked example.

Lead, booking and entry connection log — fictional worked example
Test ID, campaign and routeStore, permissions and retentionInbound and return-signal testsBooking state and updateEntry, cancellation and duplicatesCohort and observation cutoffConnection result and gapStatus, owner, backup and due
LD-01 / CAM-A / in-app formStore S01 / admin R01 / retention reply D01QA-L01 received in CRM; return signal untestedPending→confirmed M01 / booking ownerC01 check-in / re-entry separate; duplicate rule under review11-01 to 11-03 cohort / cutoff 11-10 18:00 KSTInbound only; booking return and entry link unverifiedHold / CRM lead / return and duplicate test by 11-04 12:00
LD-02 / CAM-A / own web formWeb CRM S02 / access R02 / deletion D02QA-L02 received; no automatic ad-platform storeMatches booking M02 / update owner namedQA-L02 cancellation reflected; no check-in11-01 to 11-03 cohort / cutoff 11-10 18:00 KSTWeb CRM and booking linked; separate from ad lead storeIsolate tests / analysis / hand over scope by 11-04 15:00
LD-03 / CAM-B / proposed new featureKorean-account support and permission unconfirmed—Booking integration documentation not received—Observation period unsetAvailability and actual data route unknownHold adoption / advertising / official reply by 11-05 10:00
LD-04 / CAM-A / messagesStore S04 / admin R04 / account conditions D04QA-L04 inbound and separate QA-C04 cancellation return testedQA-L04 booking confirmed; separate QA-C04 cancellation syncedQA-L04 one entry and one re-entry counted as one person11-01 to 11-03 cohort / cutoff 11-10 18:00 KSTSpecified test linked only; unsupported routes excludedBackup B04 checked / operations and analysis / actual data in restricted ledger

Blank template preview

This preview shows a few rows. The downloaded file contains 24 prepared rows.

Eight columns · scroll horizontally to view the complete blank worksheet.

Lead, booking and entry connection log — blank worksheet
Test ID, campaign and routeStore, permissions and retentionInbound and return-signal testsBooking state and updateEntry, cancellation and duplicatesCohort and observation cutoffConnection result and gapStatus, owner, backup and due
————————
————————
————————

Check your completed template

  • Route, store, access, retention and backup owners are confirmed.
  • Inbound, return-signal, booking, entry, cancellation and duplicate tests are distinct.
  • Collection period, cutoff and untraceable scope are stated.

What to pass to the next person

CRM sends results and open items to advertising, booking, on-site and analysis leads. Share personal records only within authorised access.

Check before using this template

Choose cohorts and windows for the actual event. This log does not back up leads, replace a personal-data register or transmit advertising conversion signals.

Sources used to develop this template

EVENTODIT created this template using the working methods described in the public sources below. It is not an official form and has not been reviewed or approved by those organisations.