Skip to main content

DMA & Radius Targeting for Tours

DMA and RADIUS are the two geographic targeting fields in the Tour EVENTS tab. Together, they define the local market footprint used for event-level advertising.

Understanding Tour Targeting

Note: Review event targeting before generating child campaigns so inherited values are correct from the start. Recheck targeting after generation if the campaign requires market-specific exceptions.

DMA Targeting

DMA identifies the broader market area for an event. This is typically used when campaign coverage should align to the established media market around the show. DMA Targeting is:

  • Best for market-level reach

  • Useful when planning aligns to standard media geographies

  • Provides a clear market label for coordination and reporting

Radius Targeting

Radius defines a distance-based targeting boundary around the event location or configured point. This is typically used when coverage should be constrained to a local drive area. Radius Targeting is:

  • Best for localized targeting around a venue or city point

  • Useful when market boundaries are too broad

  • Supports practical audience reach around the show

Impact of DMA & Radius on Child Campaigns generated via Master Campaigns

When child campaigns are generated from Master Campaigns, the event-level targeting context follows the event. In practice, this means the child campaign inherits the local geographic setup captured in the Tour EVENTS tab for that show.

  1. A tour event is configured with its DMA and RADIUS values in the Tour EVENTS tab.

  2. A Master Campaign is used to generate child campaigns for one or more events.

  3. Each resulting child campaign inherits the event-level targeting settings associated with its source event.

  4. Teams then review the generated campaigns and make any required platform-specific refinements.

Note: Inherited targeting improves consistency, but it does not replace final QA. Users should still validate campaign settings, destination links, and tracking readiness before launch.

Did this answer your question?