CAPI Errors

Symptom

Server-side CAPI integration shows errors:

  • “Connection failed” in Integrations page
  • Events not reaching ad platforms
  • Error messages in TrackShift

Checking CAPI Status

  1. Go to TrackShift → Integrations
  2. Look at each provider’s status:
Status Meaning
✅ Connected Working properly
⚠️ Warning Partial issues
❌ Error Not working
⏳ Pending Not yet configured

Click on any provider to see detailed error messages.

Common CAPI Errors

Error: “Invalid Access Token”

Cause: Your access token has expired or been revoked.

Solution:

For Meta CAPI:

  1. Go to Meta Events Manager
  2. Select your Pixel
  3. Go to Settings
  4. Scroll to Conversions API
  5. Click “Generate new access token”
  6. Copy the new token
  7. Update in TrackShift → Integrations → Meta

For GA4:

  1. Go to Google Analytics
  2. Admin → Data Streams → Your stream
  3. Scroll to Measurement Protocol API secrets
  4. Create new secret or copy existing
  5. Update in TrackShift

For TikTok:

  1. Go to TikTok Events Manager
  2. Settings → Generate new access token
  3. Update in TrackShift

Error: “Permission Denied”

Cause: Token doesn’t have required permissions.

Solution: Regenerate token with correct permissions:

Platform Required Permissions
Meta ads_management, business_management
TikTok Pixel events management
Pinterest Full access to conversions
Snapchat Marketing API access

Error: “Invalid Pixel/Tag ID”

Cause: The Pixel ID entered is incorrect or deleted.

Solution:

  1. Go to your ad platform
  2. Navigate to your pixel/tag
  3. Copy the ID exactly
  4. Update in TrackShift
  5. IDs should be numbers only (no letters)

Error: “Rate Limited”

Cause: Too many requests sent to the platform API.

Solution:

  • This is temporary and usually resolves itself
  • TrackShift automatically retries with exponential backoff
  • Events will be queued and sent later
  • No action needed unless persists > 24 hours

Error: “Network Error” or “Timeout”

Cause: Temporary network issues between servers.

Solution:

  • Usually resolves automatically
  • Check TrackShift status page
  • If persists, contact support

Error: “Duplicate Event”

Cause: Same event ID sent twice (usually not an error).

Solution:

  • This is expected behavior for deduplication
  • Ad platform ignores the duplicate
  • No action needed

Error: “Invalid Event Data”

Cause: Event payload doesn’t match platform requirements.

Solution:

  1. Check your product catalog IDs match
  2. Verify currency codes are valid (USD, EUR, etc.)
  3. Ensure prices are positive numbers
  4. Contact support if persists

Testing CAPI Connections

Method 1: TrackShift Test Button

  1. Go to Integrations
  2. Click on the provider
  3. Click Test Connection
  4. Result shows success or specific error

Method 2: Check in Ad Platform

After sending test event:

Meta:

  • Events Manager → Test Events tab
  • Should show test event within seconds

GA4:

  • DebugView or Realtime report
  • Should show event within minutes

TikTok:

  • Events Manager → Test Events
  • Similar to Meta

Method 3: Check TrackShift Logs

  1. Go to Health Dashboard
  2. Look at recent events
  3. Failed CAPI events show error status

Retry Logic

TrackShift uses exponential backoff for failed events:

  • 1st retry: After 1 minute
  • 2nd retry: After 5 minutes
  • 3rd retry: After 15 minutes
  • 4th retry: After 1 hour
  • After 4 failures: Event marked as failed

Events remain in queue for 24 hours before being discarded.

Preventing CAPI Issues

  1. Monitor regularly: Check Integrations page weekly
  2. Update tokens proactively: Regenerate before they expire
  3. Set up alerts: Configure Slack notifications for failures
  4. Test after changes: Always test after updating credentials

—

Last updated: January 16, 2026