Google Analytics events tracked by Raisely

Raisely’s Google Analytics integration sends events to your connected Google Analytics property so you can understand how supporters interact with your campaign.

This article explains which events Raisely sends to Google Analytics 4 (GA4), including donation activity, sign-ups, and ticket purchases.

Note: The event names below apply to GA4. Legacy Universal Analytics integrations use different event names.

Understanding events and parameters

An event records an action, such as a supporter selecting a donation amount or completing a sign-up.

A parameter provides additional information about that action. Depending on the event, Raisely may include details such as:

• Value: The monetary value associated with the action.
• Currency: The currency associated with the amount.
• Method: The method used to log in or sign up.
• Instance ID: An identifier for the donation form instance.
• Items: Details about tickets or other items included in an e-commerce event.

Not every event includes parameters.

Donation events

Use these events to understand how supporters move through your donation form.

Opening the form and selecting an amount

• donation_form_loaded — The donation form loads. Includes instance_id and non_interaction.
• donation_form_amount_clicked — A supporter clicks a donation amount. Includes instance_id, value, and currency.
• donation_form_amount_selected — A donation amount is selected. Includes value and currency.

Completing details and making a payment

• donation_form_giftaid_completed — A supporter completes the Gift Aid step.
• donation_form_details_completed — A supporter completes their details. Includes value.
• donation_form_payment_details_entered — A supporter enters their payment details. Includes value.
• donation_form_payment_failed — A payment attempt fails. Includes value.
• donation_form_donation_updated — The donation is updated. Includes instance_id and value.

Using a digital wallet

• donation_form_wallet_opened — A supporter opens a digital wallet. Includes instance_id and value.
• donation_form_wallet_submitted — A supporter submits payment through a digital wallet. Includes instance_id and value.

Completing a donation

• purchase — A one-off donation or recurring donation subscription is successfully created.

Important: Both successful one-off donations and successful subscription creation use the purchase event in your connected GA4 property.

Account and engagement events

These events track account activity and other interactions with your campaign.

• login — A supporter logs in. Includes method.
• sign_up — A supporter creates an account. Includes method.
• sign_up_progressed — A supporter progresses through a sign-up stage. Includes stage.
• share — A supporter shares content. Includes content_type, item_id, and is_logged_in.
• generate_lead — A lead form is submitted. Includes form_name.
• post_created — A post is created.
• qrcode_downloaded — A QR code is downloaded.

Sign-up form events

These events track progress through a sign-up form. The events you see depend on the steps included in your form.

Form progress

• signup_form_loaded — The sign-up form loads.
• signup_form_exercise_goals_selected — Exercise goals are selected.
• signup_form_details_completed — The details step is completed.
• signup_form_ticket_form_completed — The ticket form step is completed.
• signup_form_attendee_details_completed — Attendee details are completed.
• signup_form_profile_completed — The profile step is completed.

Donations and promotional codes

• signup_form_donation_added — A donation is added. Includes the donation amount in decimal units.
• signup_form_donation_completed — The donation step is completed.
• signup_form_donation_skipped — The donation step is skipped.
• signup_form_promo_code_added — A promotional code is added.

Tickets and checkout

• add_to_cart — A ticket is added. Includes item details.
• remove_from_cart — A ticket is removed. Includes item details.
• begin_checkout — Ticket selections are confirmed. Includes item details.
• add_payment_info — The form is submitted. Includes currency, value, coupon, payment_type, and items.

Successful sign-up

• signup_form_succeeded — The sign-up is completed successfully.

A successful sign-up can also send a purchase event when the transaction value is greater than zero.

Ticket form events

These events track activity in a standalone ticket form.

Form progress

• ticket_form_form_loaded — The ticket form loads.
• ticket_form_details_completed — The details step is completed.
• ticket_form_ticket_form_completed — The ticket selection step is completed.
• ticket_form_attendee_details_completed — Attendee details are completed.

Note: The form-load event is named ticket_form_form_loaded, including the repeated word “form.”

Donations and promotional codes

• ticket_form_donation_added — A donation is added.
• ticket_form_donation_completed — The donation step is completed.
• ticket_form_donation_skipped — The donation step is skipped.
• ticket_form_promo_code_added — A promotional code is added.

Tickets and checkout

• add_to_cart — A ticket is added. Includes item details.
• remove_from_cart — A ticket is removed. Includes item details.
• begin_checkout — Ticket selections are confirmed. Includes item details.
• add_payment_info — The ticket form is submitted. Includes item details.

Successful ticket form submission

• signup_form_succeeded — The ticket form is completed successfully.

Note: Ticket forms currently use signup_form_succeeded as their success event name, rather than ticket_form_succeeded.

Why is there a second Google Analytics property on my campaign?

Alongside your connected Google Analytics property, Raisely loads its own property: G-K2K0QDLR9Y.

This property receives a core set of events for Raisely’s analytics, as acknowledged in Raisely’s Terms of Service. These include donation form loads, successful donations and subscriptions, successful sign-up and ticket form submissions, and technical session information.

The events sent to Raisely’s property are separate from those sent to your connected property. Some event names also differ. For example:

• Your connected GA4 property receives purchase for a successful donation.
• Raisely’s property receives donation_form_succeeded for a successful donation.

Most core events sent to Raisely’s property only fire when the campaign is in LIVE mode or on a .test domain.

What if my integration uses a legacy Universal Analytics ID?

Raisely uses legacy event naming when the configured Analytics account ID contains UA-.

Legacy events can have names such as user-login, donate-stage, or success, with additional category and label information. They do not match the GA4 event names listed above.

If you are comparing older reports with GA4 reports, check which integration type was used before comparing event names.