Standard Events Reference Guide

Introduction

This comprehensive guide covers all standard events supported by ServerTrack. Standard events are predefined event types that platforms like Facebook, TikTok, and GA4 recognize and use for tracking conversions and user behavior.

What are Standard Events?

Standard events are predefined event types with specific meanings:

• Platform Recognized: Platforms understand and process standard events
• Conversion Tracking: Used for tracking conversions and optimization
• Consistent Naming: Same event names across platforms
• Standard Parameters: Expected parameters are well-defined

Standard Events List

PageView

Description: Tracks page views on your website.

When to Use: Fire on every page load.

Common Parameters:

• content_name (optional): Page name or title
• content_category (optional): Page category

ViewContent

Description: Tracks when users view product pages, blog posts, or other content.

When to Use: Fire when a user views a product page, article, or content item.

Common Parameters:

• content_ids (required): Array of content/product IDs
• content_type (optional): Type of content (e.g., "product")
• content_name (optional): Name of the content
• value (optional): Value of the content
• currency (optional): Currency code

AddToCart

Description: Tracks when users add items to their shopping cart.

When to Use: Fire when a user clicks "Add to Cart" button.

Common Parameters:

• content_ids (required): Array of product IDs added
• content_type (optional): Type (e.g., "product")
• value (optional): Total value of items added
• currency (optional): Currency code
• contents (optional): Array of item objects with id, quantity, item_price

InitiateCheckout

Description: Tracks when users begin the checkout process.

When to Use: Fire when user clicks checkout or enters checkout page.

Common Parameters:

• content_ids (required): Array of product IDs in cart
• value (optional): Total cart value
• currency (optional): Currency code
• num_items (optional): Number of items in cart
• contents (optional): Array of item objects

AddPaymentInfo

Description: Tracks when users add payment information during checkout.

When to Use: Fire when user enters payment information.

Common Parameters:

• value (optional): Cart value
• currency (optional): Currency code
• content_ids (optional): Product IDs

Purchase

Description: Tracks completed purchases/transactions.

When to Use: Fire on order confirmation page or after successful payment.

Common Parameters:

• value (required): Purchase value/amount
• currency (required): Currency code (e.g., "USD")
• transaction_id (optional but recommended): Unique transaction/order ID
• content_ids (optional): Array of purchased product IDs
• contents (optional): Array of item objects with id, quantity, item_price
• num_items (optional): Number of items purchased

Lead

Description: Tracks when users submit lead forms or sign up.

When to Use: Fire when user submits contact form, newsletter signup, or registration.

Common Parameters:

• value (optional): Lead value if applicable
• currency (optional): Currency code
• content_name (optional): Form or lead source name

CompleteRegistration

Description: Tracks completed user registrations.

When to Use: Fire when user successfully completes account registration.

Common Parameters:

• value (optional): Registration value
• currency (optional): Currency code
• status (optional): Registration status

Common Parameters Explained

content_ids

Array of content/product identifiers. Use strings, not numbers.

content_ids: ["product-123", "product-456"]

value and currency

Numeric value and 3-letter ISO currency code (e.g., "USD", "EUR").

value: 99.99,
currency: "USD"

contents

Array of item objects with product details.

contents: [
    {
        id: "product-123",
        quantity: 2,
        item_price: 49.99
    }
]

Platform Compatibility

All standard events work with:

• Facebook Conversions API: Full support for all standard events
• TikTok ePIG: Full support for standard e-commerce events
• Google Analytics 4: Events are automatically mapped to GA4 event names

Best Practices

• Use Standard Names: Always use standard event names (exact spelling)
• Include Required Parameters: Include all required parameters
• Consistent Data Types: Use correct data types (numbers, strings, arrays)
• Transaction IDs: Always include transaction_id for Purchase events
• Currency Format: Use 3-letter ISO currency codes

Summary

Standard events provide:

• Platform-recognized event types
• Conversion tracking capabilities
• Consistent naming across platforms
• Well-defined parameters

Use standard events to ensure compatibility and optimal tracking performance across all platforms.