Photos, sessions and prints are different event counts

Do not use photos, sessions, prints and people as interchangeable counts. One group can complete one session, generate several images and request multiple print copies. Define the unit behind each number before presenting a result to the event team or sponsor.

Create a small metric dictionary

For each available report field, ask the provider what it counts and whether repeat sessions or test activity are included. Record the reporting window and any filters. Use the source’s supported definition rather than renaming an upload count “unique guests.”

Keep physical outputs separate from digital delivery. A printed copy does not establish that an email arrived, and a delivery record does not establish that someone viewed or shared the image.

Label the report plainly

Use precise headings and explain exclusions. If a figure is unavailable, leave it unresolved rather than estimating from a different metric. Separate actual observed results from planning projections.

Plan activation measurement before the event so the team chooses definitions while there is still time to configure the supported reporting flow.

A hypothetical reconciliation

Suppose an illustrative event records 40 sessions and 120 physical prints. The print total could reflect multiple copies per group; it does not prove 120 unique participants. If the system also records delivery actions, keep those as another unit rather than adding them to prints and calling the result “people reached.”

Create a dictionary with metric name, counted object, report source, filters, and known exclusions. Include test activity if the report cannot exclude it.

Fotozap reporting can be organized by date, campaign and device. Use those dimensions to define the relevant event window before interpreting the totals. A precise label is more useful than a larger number with an ambiguous unit.