Find out which channel fills your event
If you share one event in a newsletter, on social media and through a partner, you probably want to know which one worked. Traffic sources reports answer that for every event. They are available on the Entry and Pro plans.
New to UTM tags? Start with What are UTM Parameters?.
Step 1: Build a tagged link
- Go to My Events and open the event's Stats page.
- Find the Traffic sources card and use the link builder.
- Enter a source, medium and campaign (for example
newsletter,email,spring-launch). - Copy the tagged link and use it in that one channel.
Make a separate link for each place you share the event.
Step 2: Read the report
The Traffic sources card groups activity by source, medium, campaign or referring site. For each row you'll see:
- Views of the event page.
- Calendar adds, the number of times someone saved the event.
- Adds per view, which tells you which channel brings people who actually act.
A channel with fewer views but a higher adds-per-view rate is usually worth more of your time than a noisy one.
Step 3: Export it
Use the export button on the card to download a CSV for your own reporting. Campaign names are escaped so the file is safe to open in Excel or Google Sheets.
Embedded widget traffic
If you embed the Add-to-Calendar widget on your own site, SendToCal records the address and hostname of the page where it's embedded, so you can see which of your pages drives saves.
What is (and isn't) collected
- Only the six standard UTM tags are kept. Values are lower-cased, trimmed and capped at 100 characters.
- For a referring website we keep only the hostname, never the full address, path or query string.
- If a link carried an ad click ID (such as
gclid), we record only which ad network it came from, never the ID itself. - No cookies or browser storage are used for this.
- Campaign-source data is kept for 400 days.
- It is recorded only for events owned by Entry and Pro organizers. Events on the Free plan still count views and calendar adds, but no source breakdown is stored.