Skip to main content

The Tour Events Tab

The Tour Events tab brings key show, ticketing, link, tracking, and targeting information into a single table and supports Excel export.

The Tour Events tab is the central planning view for event-level tour details in M. Use the Tour Events tab to...

  • Review event-by-event operational details across a tour

  • Confirm ticketing dates, presale windows, and outbound links

  • Validate pixel readiness before campaigns launch

  • Set and verify DMA and radius targeting used by downstream child campaigns

  • Export the full event list to Excel for sharing and auditing

This article documents all details shown in the Tour Events tab and the matching Excel export, along with how geographic targeting values flow into child campaigns created from Master Campaigns.

Understanding the Tour Events Tab

Each row in the Tour EVENTS tab represents a tour event.

The columns are grouped into four practical categories so teams can quickly find what they need.

Column Reference

Show & Venue

Column

Description

How it is used

VENUE

The name of the venue where the show takes place.

Used to distinguish events within the same market and align planning with venue-specific ticketing or promotional activity.

MARKET

The event market, typically the city or market label used for planning and reporting.

Helps identify the local market at a glance and supports coordination across routing, media, and reporting workflows.

SHOW DATE

The calendar date of the event.

Drives timing awareness for campaign setup, presale planning, and launch sequencing.

ANNOUNCE

The announcement date for the event.

Used to coordinate public reveal timing and ensure media and ticketing milestones align to the event launch plan.

DOOR TIME

The time doors open for attendees.

Provides operational context and may support messaging, day-of-show planning, and stakeholder reference.

SHOW TIME

The scheduled start time of the performance.

Used as a reference for operations and show-specific communications.

Ticketing & Presale Windows

Column

Description

How it is used

TIX COMPANY

The ticketing provider or platform associated with the event.

Helps teams understand where inventory is hosted and who owns ticketing execution.

PRESALE DATE (PROMOTER)

The promoter presale start date.

Used to schedule promoter-led messaging and align ad timing to the correct access window.

PRESALE DATE (VENUE)

The venue presale start date.

Used to support venue-specific promotion and verify that the correct link and password timing are in place.

PRESALE DATE (RADIO)

The radio partner presale start date.

Helps coordinate media-partner promotion and market-specific activation.

PASSWORD

The access code required for a presale, when applicable.

Referenced when validating gated access details tied to a presale link or communication plan.

ONSALE DATE

The public on-sale date.

Serves as a key launch milestone for campaign pacing, creative timing, and readiness checks.

PRESALE DATES

A consolidated view of presale timing for the event.

Provides a quick reference when several presales exist and helps users compare windows without checking multiple columns individually.

Links & Tracking

Column

Description

How it is used

TICKET LINK

The primary ticket purchase URL for the event.

Used in campaign setup, review, and export validation to ensure traffic is directed to the correct destination.

PRESALE LINK

The destination URL for presale access.

Used when a presale requires a separate landing page or access flow from the public on-sale link.

VIP LINK

The destination URL for VIP packages or VIP-specific sales.

Helps teams support premium inventory or package-specific promotion.

PIXEL STATUS

The status of tracking pixel readiness for the relevant destination or workflow.

Used as a quick operational checkpoint before launch so teams can confirm whether tracking requirements have been met.

Geographic Targeting

The Tour EVENTS tab stores the event-level DMA and RADIUS values that are used when creating downstream advertising from Master Campaigns.

Column

Description

How it is used

DMA

The designated market area associated with the event for market-level targeting.

Used to define the primary local market for campaign targeting and planning.

RADIUS

The distance-based targeting radius associated with the event.

Used when campaigns need geo-fenced coverage around a point or venue rather than relying only on market boundaries.

These values act as the source settings for local child campaign targeting unless a user intentionally adjusts targeting later in the campaign workflow.

The Workflow for Tour Excel Exports

The Tour EVENTS tab supports Excel export so users can review the event table outside M, share it with stakeholders, and validate details in bulk.

Common reasons to export include:

  • Cross-functional review with marketing, ticketing, and operations teams

  • Bulk validation of dates, links, and passwords

  • Offline planning and annotation

  • Audit support for event-level campaign setup inputs

Understanding Tour Exports

The Excel export reflects the Tour EVENTS tab and includes the same 19 columns documented on this page:

  • MARKET

  • VENUE

  • SHOW DATE

  • ANNOUNCE

  • DOOR TIME

  • SHOW TIME

  • TIX COMPANY

  • PRESALE DATE (PROMOTER)

  • PRESALE DATE (VENUE)

  • PRESALE DATE (RADIO)

  • PASSWORD

  • ONSALE DATE

  • PRESALE DATES

  • TICKET LINK

  • PRESALE LINK

  • VIP LINK

  • PIXEL STATUS

  • DMA

  • RADIUS

How To Export A Tour To Excel

It's best to export after key event details have been updated and before campaign generation or stakeholder distribution. This helps reduce mismatches between in-app records and shared planning files.

  1. Open the relevant tour in M.

  2. Go to the Tour EVENTS tab.

  3. Review the event table for completeness and accuracy.

  4. Use the Excel export option to download the current event list.

  5. Open the exported file and confirm that dates, links, and targeting values are present as expected.

  6. Share the file with internal or external stakeholders as needed for planning, review, or reconciliation.

Did this answer your question?