Common failures for Parse.ly responses, Civis exports, and tracking pixels.
Where is the failure?
Which surface is failing?
Parse.ly metrics null or empty
Confirm PRC_PLATFORM_PARSELY_API_KEY and PRC_PLATFORM_PARSELY_SECRET. Call Parsely::is_configured(). Match the canonical URL Parse.ly tracks.
Check auth or consent
For Civis 401, regenerate the API key under Settings → Analytics → Civis Exports. For missing pixels, confirm the pixel constant, prc-privacy-consent, and marketing consent.
This answer needs a valid destination.
Edit the block and connect this answer to another question or outcome.
Parsely metrics returning null
Symptom: parsely_metrics is null in REST responses.
Cause: Missing Parse.ly constants, or Parse.ly has no data for the URL.
Fix: Set PRC_PLATFORM_PARSELY_API_KEY and PRC_PLATFORM_PARSELY_SECRET in vip-config/keys-and-tokens.php. Verify with Parsely::is_configured(). Pass the exact canonical URL Parse.ly tracks.
Civis endpoints returning 401
Symptom: {"code":"civis_api_key_missing","message":"X-Civis-API-Key header is required."} (or civis_api_key_invalid).
Cause: Key not configured in wp-admin, or the request header does not match.
Fix: Go to Settings → Analytics → Civis Exports, generate and save a key, then update Civis “Import from URL” configuration.
Tracking pixels not loading
Symptom: Pixel scripts absent from page source after granting consent.
Cause: Pixel ID constant unset, wp-consent-api / prc-privacy-consent inactive, or marketing consent not granted.
Fix: Define the pixel constant (for example PRC_PLATFORM_META_PIXEL_ID). Confirm consent plugins are active. For temporary vendor verification, disable Require marketing consent for that pixel in Settings → Analytics.