# Understand traffic sources for your profile and events
Understand source-report availability, consented measurement and tagged links.

Events now focuses on running shows. Source and campaign reports have been removed from the Events hub and event editor. Open **Analytics** from the main navigation, choose a time range, then select an event row or the public-profile card to inspect available measurements. Use **Guests** for current admission records and the event editor for settings. Existing consent-based measurement and external analytics connections are unchanged.

The definitions below explain collected data; they do not mean every measurement or breakdown can currently be released. See [Understand event performance](/support/bookings-events/understand-event-performance) for the Analytics page and its filters.

## Report availability

The Channel column can show measured visit counts when collection coverage is verified and the full channel breakdown passes the privacy release. Widget visits without campaign tags appear as **gigiii widget**; visits without reliable source evidence appear as **Direct / unknown**. A dash means the count is unavailable or protected, while 0 is a released zero for that channel. Medium remains unavailable. Account owners and admins can approve up to eight exact `utm_campaign` tags and display names in **Business → Connections**. Campaign counts appear only when the complete channel and campaign partition passes privacy checks. Other tags are grouped as **Other tagged campaigns**; absent tags as **Untagged**. Arbitrary date filters remain unavailable. A large total alone does not make every breakdown safe.

Channel and campaign measurement uses completed Berlin days within the selected 7, 30 or 90 day preset. The page labels its source period separately because the operational page-view chart also includes today. Today's clicks cannot appear in this breakdown until the day closes and coverage is verified. The Excel Sources sheet uses the same released values and states as the page.

Attendance, guest-list and order tools remain available under their existing permissions. Unavailable source reporting does not prevent RSVPs or ticket purchases and does not change your analytics connections or the collection of consented measurements.

## What measurement means

Only visitors who accept Analytics are measured. Measured views count actions, including repeat views. A resource session counts once for each resource visited; it is not a person or a unique account-wide visitor. Event conversion measurement requires an eligible registration or native paid order linked to the measured event session in the same period. Checkout starts and external-link clicks are intent, not confirmed purchases.

Direct / unknown describes missing reliable source information for a measured visit. Missing attribution is different: it can result from absent consent, blocking, timing, expired data or missing linkage. Do not interpret unavailable reporting as a count of consent refusals.

## Tagged links

You can still use tagged links to describe campaign context, for example:

```
https://www.gigiii.com/en/events/my-night?utm_source=newsletter&utm_medium=email&utm_campaign=autumn&utm_content=hero
```

Supported parameters are `utm_source`, `utm_medium`, `utm_campaign`, `utm_id`, `utm_content` and `utm_term`. Do not include names, email addresses, phone numbers, attendee IDs or other personal data. Invalid labels are discarded. Labels are not verified campaign evidence; an approved display name, complete coverage and privacy release are all required for a named campaign count.

A host-site consent choice does not replace the separate cookie choice on gigiii. Source records retain their existing 90-day window. Visitors can change their choice in Cookie Preferences without losing the ability to register or buy tickets.

RSVP confirmation emails are delivered independently of registration success. Native purchases are counted from confirmed payment evidence; browser clicks do not add purchases. A previously confirmed RSVP without attribution is not assigned a guessed source when submitted again.