This page is a reference for everything the Add On sends to Google Analytics: the four ecommerce events across the membership checkout, the event parameters and user properties added to every pageview, and the User-ID for logged-in members.

Ecommerce Events

The Add On tracks four GA4 recommended ecommerce events. Each event includes the membership level as the item (level ID and name, with your site name as the affiliation) and the level’s initial payment as the value. Values are reported in the currency set in your Paid Memberships Pro payment settings.

• view_item: Sent when someone views your Membership Levels page. One event is sent for each level that allows new signups. If you selected specific levels in the Levels to Track setting, only those levels are included.
• add_to_cart: Sent when the membership checkout page loads for a level.
• begin_checkout: Sent the first time someone clicks or types on the checkout page, such as entering a username or email address.
• purchase: Sent on the membership confirmation page after a successful checkout, including free checkouts. This event also includes the order code as the transaction ID, plus the tax amount and discount code when the order has them.

The purchase event is only sent if the member interacted with the checkout form for the same level in the same browser. This prevents a duplicate purchase when someone reloads or revisits the confirmation page without a new checkout.

To use these events as conversions, mark them as key events in your GA4 property. Our guide on setting up GA4 conversion events for membership sites walks through the process.

Event Parameters

These parameters are added to the Google Analytics configuration on each page load. A parameter is only sent when it has a value for the content being viewed.

• post_type: The post type of the single post, page, or custom post type being viewed, such as post or page.
• author: The display name of the author of the single post, page, or custom post type being viewed.
• category: The category slug of the blog post being viewed. Posts with more than one category send a comma-separated list of slugs. Only sent for single blog posts.

Developers can add parameters with the pmproga4_custom_dimensions filter or remove default parameters with the pmproga4_default_custom_dimension filter. See Action and Filter Hooks.

User Properties

• membership_level: The membership level ID of the logged-in member. Visitors who aren’t logged in and users without an active membership are sent as no_level.

Developers can add user properties with the pmproga4_user_properties filter. For example, you might send a non-identifying User Field that members fill out at checkout or on their profile. Never send personally identifiable information, such as names or email addresses, to Google Analytics.

Event parameters and user properties won’t appear in your reports until you create matching custom dimensions in GA4.

User-ID

When a user is logged in, the Add On sends their WordPress user ID as the GA4 user_id. You can use this ID to match activity in Google Analytics to a user on your membership site, or to connect data from other tools that send to the same GA4 property.