Documentation
Documentation
Documentation
  • Documentation
  • Products
    • Fanplayr Targeting Portal
    • Fanplayr 360
    • PrivacyID
    • SiteSpeed
  • Features
    • Merchandising
    • Security
    • SMS
    • Web Push Notifications
      • Direct Integration Guide
      • Popup Integration Guide
      • Imaging Sizing Guide
    • Data Residency
  • Fanplayr Targeting
    • E-Commerce Integrations
      • Fanplayr Tracking for GA4 eCommerce
      • BigCommerce
      • CommerceV3
      • Magento 1
        • Getting Started
        • Configuration
      • Magento 2
      • Miva Merchant
      • PrestaShop
      • Salesforce Commerce Cloud
      • Shopify
      • Volusion
      • VTEX
      • VTEX IO
    • Custom Integration
      • Page tracking
        • Apply to cart
        • Session offers
      • Order tracking
      • Data types
        • CartAction
        • Product
      • Data Layer API
      • Enhanced user identification
        • Manual Integration
      • Segmentation as a service
      • Lazy loading
      • Page caching
      • Tag managers
      • Single page apps
      • Custom data for verticals
        • Travel
      • User Consent for Data
    • Pixel Integration
    • ESP Integrations
    • Link Decoration
    • User Management
      • User Identity
      • User Properties
  • Other
    • CSP & Domains
Powered by GitBook
On this page
  • Tag Configuration
  • Tag Triggering

Was this helpful?

  1. Fanplayr Targeting
  2. E-Commerce Integrations

Fanplayr Tracking for GA4 eCommerce

PreviousE-Commerce IntegrationsNextBigCommerce

Last updated 2 months ago

Was this helpful?

Fanplayr Tracking for GA4 eCommerce Integration

To integrate Fanplayr tracking with your GA4 eCommerce setup, it is essential that you have already implemented the GA4 eCommerce tracking according to the official Google Analytics guide (). Once you have added the Fanplayr template to your workspace, follow the steps below to configure the tag properly.

Tag Configuration

Account Key

Enter the Account Key provided by the Fanplayr team. This key is valid only for the specific domains that have been agreed upon.

Page Type

The Page Type should be a dynamic variable that reflects the page the user is visiting. Possible values include:

  • home – Homepage

  • prod – Product page

  • cat – Category page or product list

  • srch – Search results page

  • cart – Shopping cart page

  • checkout – A page within the checkout flow (excluding the order confirmation page)

  • order – Order confirmation page

  • blog – Blog page

  • page – Any other page (e.g., "About", "Contact", etc.)

Custom Data

The Custom Data section allows you to define additional variables to track in the Fanplayr platform. Ensure that the keys you include here are also present in the list of custom data configured in your Fanplayr portal to ensure accurate tracking.

Custom Loader

If your website requires specific processing of data before sending it to Fanplayr, you may need to add a custom JavaScript file URL provided by the Fanplayr team to the Custom Loader field.

Tag Triggering

The Fanplayr tracking tag should be triggered by the following events:

  • Page View (typically All Pages, or a specific page view event if your website is a single-page application)

  • purchase

  • view_cart

  • view_item

  • view_item_list

  • add_payment_info

  • add_shipping_info

  • add_to_cart (see note below)

  • remove_from_cart (see note below)

Important Notes:

The add_to_cart and remove_from_cart events should only be used as triggers if the "add to cart" or "remove from cart" actions do not cause a page redirect to the cart page and do not automatically trigger the view_cart event.

Measure ecommerce