MediaMath Troubleshooting & Debugging | OpsBlu Docs

MediaMath Troubleshooting & Debugging

Fix MediaMath pixel delays, conversion attribution mismatches, and TerminalOne audience segment issues with diagnostic steps.

Symptom Library

  • T1 (TerminalOne) pixel not firing or mt.trackingTag requests absent from Network tab
  • Conversion attribution mismatches between TerminalOne reports and your analytics platform
  • Audience segments stuck at 0 users or not populating within the expected 24-48 hour window
  • Bid strategy returning NO_BID for eligible inventory
  • API authentication failures with HTTP 401 or 403 responses
  • Creative assets rejected during the approval queue review

T1 Pixel Verification

MediaMath's tracking relies on the T1 Universal Pixel (UPixel). Debug in Chrome DevTools:

  1. Open Network tab and filter for mathtag.com.
  2. Look for requests to https://pixel.mathtag.com/event/js?mt_id=[ADVERTISER_ID]&mt_adid=[AD_ID].
  3. Confirm the response is 200 OK and Set-Cookie includes uuid (MediaMath's user ID).
  4. For conversion events, verify additional parameters:
// Expected conversion pixel parameters
// mt_id: Your advertiser ID (required)
// mt_adid: Ad ID for attribution (required for click-through)
// v1: Revenue value (e.g., "49.99")
// v2: Order ID for deduplication
// v3: Custom parameter
// s1-s3: String parameters for segmentation
  1. If the pixel loads but events are not recorded, check that the mt_id matches the advertiser ID in your TerminalOne campaign settings.

TerminalOne Campaign Troubleshooting

Common TerminalOne issues and their resolutions:

Issue Likely Cause Fix
Campaign shows "Inactive" Flight dates expired or budget cap reached Extend flight end date or increase budget
Zero impressions on active campaign Targeting too narrow or bid below floor Check strategy targeting overlap; raise base bid by 20%
Delivery below 50% of daily budget Frequency cap too restrictive Increase from 3/day to 5/day or broaden audience
"No Eligible Inventory" warning Deal ID expired or PMP misconfigured Verify deal ID status with the SSP partner
Pacing set to "Even" but spending in bursts Inventory availability fluctuates Switch to "ASAP" pacing temporarily to diagnose

Conversion Postback Debugging

MediaMath supports server-to-server conversion postbacks for offline attribution:

  1. Configure postback URLs in TerminalOne under Advertiser > Attribution > Postback Settings.
  2. Test the postback endpoint independently. MediaMath sends a GET request with query parameters:
# Example postback URL pattern:
# https://your-server.com/postback?mt_adid={AD_ID}&mt_uuid={UUID}&revenue={REVENUE}&order_id={ORDER_ID}

# Test with curl:
curl "https://your-server.com/postback?mt_adid=12345&mt_uuid=abc-def-123&revenue=29.99&order_id=ORD-001"
# Expected: HTTP 200 response within 5 seconds
  1. If postbacks fail silently, check TerminalOne > Reports > Postback Log for error entries. Common errors include TIMEOUT (your server took longer than 10 seconds) and HTTP_ERROR (non-2xx response).

Segment Builder Issues

When audience segments do not populate:

  • Minimum segment size: MediaMath requires at least 1,000 matched users before a segment becomes targetable. Check the segment size in Data Management Platform > Segments.
  • Cookie sync lag: First-party data uploaded via CSV takes 24-48 hours to match against MediaMath's cookie pool. Third-party segments from data providers sync within 4-6 hours.
  • Segment expiration: Default segment TTL is 30 days. Users who do not revisit are automatically removed. Increase TTL if your conversion cycle is longer.

Common API Error Responses

MediaMath's T1 API uses OAuth 2.0 authentication:

HTTP Code Error Body Fix
401 {"error":"unauthorized"} Access token expired; refresh using your refresh_token
403 {"error":"forbidden"} Your API user lacks permission for this advertiser. Check role assignments in TerminalOne > Admin > Users
429 {"error":"rate_limit_exceeded"} Default limit is 100 requests/minute. Implement exponential backoff
400 {"error":"invalid_entity"} Required field missing in POST/PUT body. Check the errors array for specifics
500 {"error":"internal_error"} MediaMath server issue. Retry after 30 seconds; file a support ticket if persistent

Escalation & Communication

  • MediaMath support portal: Include your Advertiser ID, campaign IDs, and the date range of the issue.
  • T1 API support via the developer documentation portal -- include your request_id from the response headers.
  • For pixel issues, export a HAR file from DevTools and attach it to your support ticket.

Preventive Maintenance

  • Weekly pixel health audit: verify mathtag.com requests fire on conversion pages after deployments.
  • Monthly segment size review: flag segments that have dropped below 5,000 users.
  • Quarterly API token rotation and permission audit for all service accounts.
Nach oben