Google Analytics Custom Events: Upcoming Changes

We’re overhauling the custom GA events we integrated into Newspack sites since late 2023. This overhaul simplifies the number of events we send, standardizes most of the event parameters sent with different events, and should improve the accuracy and usability of these analytics going forward.

Note that to use these events, you will still need to connect your site to the Google Analytics API. Sites that have already completed this connection will not need to take any further action.

What’s changing

Deprecated events: These events will no longer be sent:

• np_donation_new – Can now be tracked via np_modal_checkout_interaction with an action param of form_submission_success and action_type of donation.
• np_donation_subscription_cancelled – Deprecated and not replaced; may be reinstated in the future.
• np_newsletter_subscribed – Deprecated and not replaced; may be reinstated in the future.

Events with new/updated event parameters: These events describing reader funnel entry and early funnel activity are already being sent by Newspack sites and will continue to be sent, but with improved event parameters and trigger accuracy:

• np_gate_interaction
  • The action_type=paid_membership param is now replaced by action_type=checkout_button, for better consistency with np_modal_checkout_interaction events.
  • Event params related to donation and non-donation products more closely match those sent with np_modal_checkout_interaction events.
  • Events with action=form_submission_success are no longer sent. Instead, to track conversions starting from np_gate_interaction events, look for np_reader_registered, np_reader_logged_in, and np_modal_checkout_interaction events with a matching gate_post_id param.
  • Boolean-style params describing the purpose of the content gate have been expanded upon and improved for accuracy. Note that these params describe whether the element was actually visible to the reader at the time of the event, not just that it exists inside the gate’s content (as elements can be hidden by conditional logic):
    • gate_has_donation_block: Sent if the content gate was showing a Donation block at the time the event was triggered.
    • gate_has_registration_block: Sent if the content gate was showing a Reader Registration block at the time the event was triggered.
    • gate_has_checkout_button: Sent if the content gate was showing a Checkout Button block at the time the event was triggered.
    • gate_has_registration_link: Sent if the content gate was showing a link to open the reader registration modal at the time the event was triggered.
    • gate_has_signin_link: Sent if the content gate was showing a link to open the reader sign-in modal at the time the event was triggered.
• np_reader_registered
  • Now includes newspack_popup_id or gate_post_id params if the registration started from inside a Newspack Campaigns prompt or content gate, respectively.
• np_reader_logged_in
  • Now includes newspack_popup_id or gate_post_id params if the login started from inside a Newspack Campaigns prompt or content gate, respectively.
  • New param login_method indicates the method used to log in (auth modal, magic link, or “Sign in with Google” SSO button).

Prompt interaction events: Events with an event name of np_prompt_interaction are largely unchanged and will continue to be sent as described in Help site documentation.

Transactional events: Events with an event name of np_modal_checkout_interaction can be used to track interactions with Newspack’s streamlined modal checkout experience, from transaction start to dismissal or completion. These events include params that connect them to events that started with np_gate_interaction or np_prompt_interaction events, allowing you to build a complete picture of readers’ journeys through the funnel all the way to successful conversion. Relevant funnel params:

• Now includes newspack_popup_id or gate_post_id params if the transaction started from inside a Newspack Campaigns prompt or content gate, respectively.
• action_type params allow you to connect transactional events to other event types with matching action_type values of donation or checkout_button.
• Transaction detail params offer additional info on the transaction itself:
  • amount
  • action_type
  • currency
  • product_id
  • product_type
  • recurrence
  • variation_id (only if is_variable)