Missing Event Parameters in Platform Reports

Introduction

When event parameters don't appear in Facebook, TikTok, or GA4 reports as expected, it can indicate issues with parameter naming, data types, or platform-specific requirements. This guide helps you diagnose and fix missing parameter issues.

Common Causes of Missing Parameters

1. Incorrect Parameter Names

Symptoms: Parameters don't appear in reports or appear with different names.

Causes:

• Parameter names don't match platform requirements (case-sensitive)
• Typos in parameter names
• Using custom parameter names that platforms don't recognize

Solution:

• Check platform documentation for exact parameter names
• Use standard parameter names (e.g., value, currency, content_ids)
• Verify parameter names are spelled correctly
• Check case sensitivity (Facebook uses lowercase, GA4 uses snake_case)

2. Incorrect Data Types

Symptoms: Parameters appear but with wrong values or don't process correctly.

Causes:

• Numbers sent as strings (e.g., "99.99" instead of 99.99)
• Arrays sent as strings
• Boolean values as strings instead of booleans

Solution:

• Send numbers as numbers: value: 99.99 not value: "99.99"
• Send arrays as arrays: content_ids: ["123", "456"] not content_ids: "123,456"
• Send booleans as booleans: is_test: true not is_test: "true"

3. Platform-Specific Requirements

Symptoms: Parameters work in one platform but not others.

Causes:

• Different platforms have different parameter naming conventions
• Some parameters are platform-specific
• Platforms process parameters differently

Solution:

• Check platform-specific documentation
• Verify parameters are supported by the target platform
• Use platform-specific parameter names when required

Platform Parameter Requirements

Facebook CAPI Parameters

Facebook uses standard parameter names in custom_data:

• value: Number (decimal)
• currency: String (ISO 4217 format, e.g., "USD")
• content_ids: Array of strings
• content_type: String (e.g., "product")
• content_name: String
• contents: Array of objects with id, quantity, item_price

TikTok ePIG Parameters

TikTok uses similar parameter names but in properties:

• value: Number
• currency: String
• content_type: String
• content_id: String (or array)
• quantity: Number
• price: Number

GA4 Parameters

GA4 uses snake_case parameter names in params:

• currency: String
• value: Number
• transaction_id: String
• items: Array of item objects

Diagnosing Missing Parameters

Step 1: Check ServerTrack Event Logs

1. Go to Event Logs in your ServerTrack dashboard
2. Find the event in question
3. Click to view event details
4. Check the event payload
5. Verify parameters are present in the payload

Step 2: Check Platform Event Logs

• Facebook: Events Manager → Test Events (for real-time) or Events tab (for historical)
• TikTok: Events Manager → Web Events
• GA4: Debug View or Real-time reports

Step 3: Compare Payloads

1. Compare what you're sending (ServerTrack logs) vs what platforms receive
2. Check if parameter names match exactly
3. Verify data types are correct
4. Look for any transformations or mappings

Fixing Missing Parameters

Fix 1: Correct Parameter Names

Ensure parameter names match platform requirements:

// ✅ Correct - Facebook
{
    value: 99.99,
    currency: "USD",
    content_ids: ["123", "456"],
    contents: [
        { id: "123", quantity: 2, item_price: 49.99 }
    ]
}

// ❌ Incorrect - Wrong parameter names
{
    amount: 99.99,  // Should be "value"
    currency_code: "USD",  // Should be "currency"
    product_ids: ["123"]  // Should be "content_ids"
}

Fix 2: Correct Data Types

Ensure data types match platform expectations:

// ✅ Correct - Proper data types
{
    value: 99.99,  // Number
    currency: "USD",  // String
    content_ids: ["123", "456"],  // Array
    quantity: 2  // Number
}

// ❌ Incorrect - Wrong data types
{
    value: "99.99",  // String instead of number
    currency: "USD",  // OK
    content_ids: "123,456",  // String instead of array
    quantity: "2"  // String instead of number
}

Fix 3: Correct Parameter Structure

For Facebook, parameters go in custom_data:

// ServerTrack automatically structures for Facebook
st('track', 'Purchase', {
    currency: "USD",
    value: 99.99,
    transaction_id: "ORD-12345",
    content_ids: ["123", "456"],
    contents: [
        { id: "123", quantity: 2, item_price: 49.99 }
    ]
}, userData);

Platform-Specific Troubleshooting

Facebook CAPI Missing Parameters

• Check Events Manager → Test Events to see raw event data
• Verify parameters are in custom_data object
• Ensure parameter names use lowercase or match Facebook's naming
• Check that arrays are properly formatted

TikTok ePIG Missing Parameters

• Check Events Manager → Web Events for received events
• Verify parameters are in properties object
• Ensure parameter names match TikTok's requirements
• Check event mapping in ServerTrack

GA4 Missing Parameters

• Check GA4 Debug View for real-time parameter inspection
• Verify parameters are in params object
• Ensure parameter names use snake_case
• Check that items array is properly structured

Parameter Validation Tips

• Test in Platform Test Tools: Use Facebook Test Events, TikTok Events Manager, GA4 Debug View
• Compare Documentation: Always check platform documentation for exact requirements
• Start Simple: Test with minimal parameters first, then add complexity
• Check Examples: Review platform example payloads

Common Parameter Issues

Value and Currency

Issue: Purchase value not showing correctly.

Check:

• value is a number, not a string
• currency is a 3-letter ISO code (e.g., "USD", not "dollars")
• Both parameters are included together

Content IDs / Product IDs

Issue: Products not appearing in reports.

Check:

• content_ids is an array, not a string
• IDs are strings: ["123", "456"] not [123, 456]
• Array is not empty

Contents Array

Issue: Product details missing.

Check:

• contents is an array of objects
• Each object has required fields: id, quantity, item_price
• item_price is a number (price per item, not total)

Testing Parameters

Test in Platform Test Tools

1. Send a test event with parameters
2. Check platform test tools (Facebook Test Events, TikTok Events Manager, GA4 Debug View)
3. Verify all parameters appear correctly
4. Check parameter values match what you sent

Validate Payload Structure

1. Check ServerTrack Event Logs for sent payload
2. Compare with platform-received payload
3. Identify any missing or transformed parameters
4. Fix parameter structure if needed

Summary

Missing parameters are usually caused by:

• Incorrect parameter names (typos, wrong names, case sensitivity)
• Wrong data types (strings instead of numbers, strings instead of arrays)
• Platform-specific requirements not met
• Parameters in wrong location (wrong object structure)

To fix:

1. Check platform documentation for exact parameter requirements
2. Verify parameter names match exactly (case-sensitive)
3. Ensure data types are correct (numbers as numbers, arrays as arrays)
4. Test in platform test tools to verify parameters appear
5. Compare sent payload vs received payload

Always test parameters in platform test tools before relying on them in production reports.

For more information, see our Standard Events Reference Guide and Event Parameter Best Practices.