Skip to main content
After installing and initializing the SDK, verify that events are being sent correctly before releasing to production.

Enable Debug Logging

Enable debug logging to see SDK activity in the Xcode console:

What to Look For

Successful Initialization

When the SDK initializes successfully, you’ll see:

Successful Event Tracking

When events are accepted by Permutive servers:
The format is Accepted: X / Y where X is the number of events accepted and Y is the total sent.

Schema Validation Errors

If event properties don’t match your schema:
Schema validation errors mean events are being rejected. Fix the property names or types to match your event schema in the Permutive dashboard.

Verification Checklist

1

SDK Initializes

Look for SDK ready in the console after app launch.
2

Events Are Sent

Navigate through your app and look for Accepted: X / X messages.
3

No Rejections

Ensure there are no event rejection error messages.
4

Check Dashboard

Log into your Permutive dashboard and verify events appear (may take up to 5 minutes).

Verification Code Example

Add this verification helper during development:

PageTracker Verification

Verify PageTracker is working correctly:

Common Verification Issues

Problem: Console is silent, no Permutive logs appear.Solutions:
  • Confirm logModes = LogMode.all is set before calling start()
  • Check Xcode console filter isn’t hiding messages
  • Verify SDK is actually being initialized (add a breakpoint)
Problem: Events sent but rejected by server.Solutions:
  • Check event name matches schema (alphanumeric and underscores only)
  • Verify property names and types match your Permutive dashboard schema
  • Remove any extra properties not in the schema
Problem: Console shows Accepted but events not in dashboard.Solutions:
  • Wait up to 5 minutes for events to process
  • Verify you’re looking at the correct workspace
  • Check the date range filter in the dashboard
  • Confirm credentials match the dashboard environment
Problem: cohorts returns an empty set.Solutions:
  • Cohorts are evaluated server-side and may take time to populate
  • Ensure you’ve tracked sufficient events to qualify for cohorts
  • Check with your Customer Success Manager that cohorts are configured

Disable Logging for Production

Always disable debug logging before releasing to production to avoid performance overhead and prevent sensitive data from appearing in device logs.

Next Steps

Once verification passes:

Page Tracking

Implement page tracking throughout your app

Identity Management

Set up user identity tracking

Google Ad Manager

Integrate with GAM for ad targeting

Issues

Troubleshoot common problems