All Collections
Integrations
Analytics & Custom Scripts
How to track the source of your registrations or ticket sales with Google Analytics
How to track the source of your registrations or ticket sales with Google Analytics

Create custom links to track where your registrations are coming from

Updated over a week ago

One powerful way to use the Google Analytics integration is to track where registrations, ticket sales, and/or donations are coming from. This guide will cover how to create custom links to track custom parameters on your RSVPify event registrations.

If you need instructions on how to connect Google Analytics to your RSVPify event, head here first.

About UTM parameters

UTM is a piece of code added to a link to help track the source of your traffic. UTM parameters can be added to any URL, including your RSVPify event's link. You can add up to five parameters to your URLs:

  1. source (required)

  2. medium

  3. campaign name

  4. term

  5. content.

You can create a URL yourself, but you can use Google Analytics’ URL Builder as an easy way to help you build your link (especially if you're new to this concept!).

How to add UTM parameters to your RSVPify link

First step, get your RSVPify link. It will look something like this: https://startupconference.rsvpify.com/

As an example, let's say my conference has 3 people promoting the event: Ben, Kelly, and Amy. To track who referred the most registrations or sales, we would set up 3 links:

If these links are too long, you can always use a tool like bit.ly to create shortened versions.

Tracking your analytics in GA4

Once traffic begins hitting your page and registrations start coming in, you'll be able to layer your conversion events with the content of your links to get detailed reporting.

In the example below, we've filtered the example scenario by registrations submitted (event) by the event UTM parameter's medium value.

Need more help? Get support from our Community Forum.
Find answers and get help from the RSVPify Support team and our community.

Did this answer your question?