A Source describes where and when media ran. Associating one with a Campaign is what tells Mira to compute exposure for it.

For creating Sources and uploading files to them, see Sources. For what exposure is and how it is computed, see Sources and Exposure.

Associating a Source

Sources can be associated while creating a Campaign, or added later from the Campaign's Sources tab using the + Associate Source button. Either way, the association carries two optional settings that are worth understanding, because they are difficult to reproduce afterwards.

Filters

Filters narrow the Source data before exposure is computed.

This matters when a Source carries more than your campaign. A vendor delivering a continuous stream of play logs is sending everything they run, so a filter on their campaign identifier selects only your rows. Without one, exposure would be computed against their entire book of business.

To add one, create or select a filter key and enter the accepted values separated by commas. Click Add New Filter for additional keys.

Labels

Labels attach a dimension that does not exist in the underlying data at all.

If you want results broken out by flight and the vendor's file has no flight column, label the association flight / summer. That value is then attached to every exposure from this association, and flight becomes available as a cut on the Study.

Click Add New Label, then create or select a label key and enter a single value. Labels take one value each - use a separate association if you need to distinguish two sets of exposures.

📘

Filters Subtract, Labels Add

A filter removes rows you do not want. A label adds information the rows never carried. Reach for a label whenever you want to cut on something the vendor does not send.

Click Associate Source to save the configuration.

How Source Data Arrives

Mira checks for new work every fifteen minutes. Data reaches a Source one of two ways.

You upload it. A file uploaded through the Console or the API is picked up on the next cycle, normalised into Mira's internal format, and stored. Accepted types and size limits are on the Sources page.

It arrives on a schedule. For vendors delivering continuously, Mira polls an agreed location and ingests each new file as it appears. These are managed Sources, set up by our team. Because the arrangement is a standing one, a missed delivery raises an alarm rather than passing unnoticed - so a gap in a managed feed gets investigated rather than silently producing an incomplete study.

Ingest alone does not compute exposure. That happens once the Source is attached to a Campaign and the corresponding location data is available, which is typically a few days behind real time.

Adding Data Mid-Campaign

Uploading a file to a Source part-way through a campaign backfills the exposure it implies for dates already covered. You do not need to re-associate the Source or resubmit the Study - though a Study whose Sources change will be queued for recompute, as described in Configuring Measurement Studies.

🚧

Check Coverage Before You Rely On It

Exposure can only be computed for inventory Mira has data for. If a vendor delivers only part of a buy, the Study measures only that part, and nothing in the Console will flag the difference. The Attribution Checklist covers what to confirm with each vendor.