42min

    Help Event types

    UTM tracking

    When you promote a link — in an email, an ad, a social post — you usually want to know which one actually produced the meeting. 42min reads the standard UTM parameters off your links and saves them with each booking, so you can see the traffic source of every meeting and every routing-form response.

    There's nothing to turn on. Tag your links and 42min captures the rest.

    What it is

    UTM parameters are the utm_… tags marketers add to the end of a link. Add them to a booking-page link or a routing-form link, and when someone opens that link and books (or submits the form), 42min stores the values alongside the booking.

    42min captures these eight parameters:

    • utm_source — where the traffic came from (e.g. newsletter, google, linkedin).
    • utm_medium — the channel (e.g. email, cpc, social).
    • utm_campaign — the campaign name (e.g. spring_launch).
    • utm_term — the paid-search keyword.
    • utm_content — which specific link or ad variant (for A/B tests).
    • gclid — Google Ads click ID.
    • fbclid — Facebook/Meta click ID.
    • referrer — the referring URL.

    Anything else in the link is ignored for tracking. These tags are recorded only — they are never filled into the booking form as answers, so they stay out of your invitee's way.

    When to use it

    • You run the same booking link across several channels (email, LinkedIn, a webinar) and want to know which one drives meetings.
    • You're paying for ads and need to tie booked calls back to a campaign or keyword.
    • You want a per-meeting record of where each lead came from, exportable for your CRM or spreadsheet.

    How to do it

    1. Start from the link you'd normally share — a booking page (42min.us/<username>/<event-slug>) or a routing form (42min.us/routing/<slug>).

    2. Append the tags as query parameters. Join the first with ? and the rest with &: 

      42min.us/sarah-chen/intro-call?utm_source=newsletter&utm_medium=email&utm_campaign=spring_launch

      The same works for a routing-form link:

      42min.us/routing/sales-intake?utm_source=google&utm_medium=cpc&utm_campaign=brand

    3. Share that tagged link. When someone books or submits the form through it, 42min records the values.

    4. Read them back:

      • Per meeting — open the meeting in Meetings and expand its details. Captured tags appear under a Traffic source heading, shown with their raw utm_* names. For a group event, each invitee's traffic source is listed separately.
      • Per routing-form response — on Routing Forms, open the form's Responses; each response shows its Traffic source under the answers.
      • In exports — the meetings CSV export and the routing-form responses CSV export each include one column per parameter, so you can pivot on them in a spreadsheet.
    Expand a meeting to see its Traffic source — the captured utm_* parameters are shown with their raw names.

    Tip

    Use a consistent naming scheme — lowercase, no spaces, the same utm_campaign value across a campaign's links. 42min stores exactly what's in the URL, so Spring_Launch, spring launch, and spring_launch count as three different campaigns in your reports.

    Common pitfalls

    • The tags must be on the link people actually click. If you shorten or wrap the link somewhere that drops the query string, nothing is captured. Test your final link and confirm the Traffic source shows up on the booking.
    • Capitalization and spelling count. The values are stored verbatim. Inconsistent casing or typos split one campaign into several in your exports.
    • Only the eight parameters above are kept. Other custom query parameters aren't recorded as traffic source (some are used to prefill the booking form instead).
    • No tags, no source. Bookings from an untagged link simply have no traffic source — that's expected, not an error.

    Last updated May 29, 2026.

    PreviousBooking questionsNext Schedules