This guide explains how to set up and analyze sales funnels in Google Analytics 4 using the events tracked by IgnitionStack’s checkout flow.
IgnitionStack tracks a comprehensive set of events throughout the purchase journey, enabling you to build detailed sales funnels in GA4. This helps you:
| Event Name | Description | Key Parameters |
|---|---|---|
pricing_section_view | User views the pricing section | locale, page_path |
pricing_tier_view | User views a specific tier card | tier, tier_price |
pricing_cta_click | User clicks a pricing CTA button | tier, tier_price, is_highlighted |
pricing_promo_banner_view | Promotional banner is displayed | spots_remaining, days_remaining |
| Event Name | Description | Key Parameters |
|---|---|---|
checkout_page_view | User lands on checkout page | tier, tier_price |
checkout_step_view | User reaches a checkout step | step_name, step_number, tier |
checkout_auth_method_selected | User selects auth method | method (google/email_login/email_register) |
checkout_auth_success | User successfully authenticates | method, user_id |
checkout_auth_error | Authentication fails | method, error_type |
checkout_terms_accepted | User accepts terms/license | terms_type, accepted |
checkout_payment_button_click | User clicks payment button | tier, tier_price, user_id |
begin_checkout | GA4 e-commerce event | value, currency, items[] |
checkout_stripe_redirect | User redirected to Stripe | tier, user_id |
purchase | Payment successful | transaction_id, value, items[] |
purchase_failed | Payment failed/cancelled | tier, error_reason |
checkout_error | Any checkout error | error_type, error_message |
checkout_abandoned | User leaves checkout | last_step, time_on_page, was_authenticated |
checkout_back_to_plans | User returns to pricing | tier |
Funnel Name: Checkout Conversion Funnel
Steps Configuration:
Step 1: Pricing Page View
├── Event: pricing_section_view
├── OR Event: pricing_tier_view
Step 2: Pricing CTA Click
├── Event: pricing_cta_click
Step 3: Checkout Page View
├── Event: checkout_page_view
Step 4: Authentication Complete
├── Event: checkout_auth_success
Step 5: Terms Accepted
├── Event: checkout_terms_accepted
├── Filter: accepted = true
Step 6: Payment Initiated
├── Event: checkout_payment_button_click
Step 7: Stripe Redirect
├── Event: checkout_stripe_redirect
Step 8: Purchase Complete
├── Event: purchaseAdd these dimensions to analyze funnel performance:
High-Intent Users:
Include users where:
- checkout_page_view occurred
- AND checkout_auth_success occurredAbandoned Cart:
Include users where:
- checkout_payment_button_click occurred
- AND purchase did NOT occur within 30 minutesError Segment:
Include users where:
- checkout_error occurred
- OR checkout_auth_error occurredPurpose: Compare conversion rates across pricing tiers
Configuration:
tierInsights:
Purpose: Analyze authentication method performance
Configuration:
Step 1: checkout_auth_method_selected
Step 2: checkout_auth_successmethodInsights:
Purpose: Identify where users abandon the checkout
Configuration:
checkout_abandoned eventlast_stepKey Metrics:
time_on_page - Average time before abandonmentwas_authenticated - Did they complete auth?last_step - Which step caused the drop-off?Purpose: Track and diagnose checkout errors
Events to track:
checkout_errorcheckout_auth_errorpurchase_failedBreakdown by:
error_typeerror_messagetierName: Checkout Completion Rate
Formula: purchase / checkout_page_view
Format: PercentageName: Auth Success Rate
Formula: checkout_auth_success / checkout_auth_method_selected
Format: PercentageName: Stripe Redirect Rate
Formula: checkout_stripe_redirect / checkout_payment_button_click
Format: PercentageName: Cart Abandonment Rate
Formula: checkout_abandoned / checkout_page_view
Format: PercentageCondition: checkout_error count > 10 in 1 hour
Severity: Critical
Action: Investigate Stripe integration
Condition: purchase / checkout_page_view < 5% over 24 hours
Severity: Warning
Action: Review checkout UX
Condition: checkout_auth_error count > 5 in 1 hour
Severity: Warning
Action: Check OAuth configuration
IgnitionStack uses GA4 standard e-commerce events:
{
event: "begin_checkout",
items: [{
item_id: "pro",
item_name: "Pro Plan",
price: 297,
quantity: 1
}],
value: 297,
currency: "BRL"
}{
event: "purchase",
transaction_id: "stripe_session_xxx",
items: [{
item_id: "pro",
item_name: "Pro Plan",
price: 297,
quantity: 1
}],
value: 297,
currency: "BRL"
}purchase events will appear in Ecommerce purchasesvalue parameterAll events include standard parameters:
locale - User’s languagepage_path - Current pagepage_title - Page titletier - Selected pricing tierfunnel_stage - conversionawareness → consideration → conversion
↓ ↓ ↓
Landing Pricing Checkout
Page Section FlowEvents are logged to console in development mode:
npm run dev
# Open DevTools > Console
# Filter by "[GA4]" to see eventsNEXT_PUBLIC_GA_ID is setThe analytics library includes deduplication:
Required parameters are validated:
localepage_pathpage_titlefunnel_stagesource_component