Skip to content

PX Tag Bundle — Error Code Reference

Endpoint: GET /v1/campaigns/px/{pxDealId}/pull/{pxAdUnitId}/bundle

This document describes the error responses you may receive from the Lucit PX bundle tag endpoint when silent_fail=0 (debug mode on). When silent_fail=1, all errors are suppressed and the server returns an empty 204 No Content response instead.

Error responses are returned as XML with http-code, internal-code, and message attributes.

Request Parameters

Parameter Required Notes
snapshot_hash Yes A unique hash identifying this ad impression snapshot. Must be present on every request.
rendered_on_play No Set to 1 or true when firing the tag at play/impression time rather than on load.
ad_id No Optional ad identifier passed through with the request.
silent_fail No Set to 1 to suppress all error responses (returns empty 204 instead). Recommended for production tags.
timestamp No Unix timestamp of the impression event.
impressions No Impression count to record.
no_pingback No Set to 1 to skip recording a Lucit pingback for this pull.
3p_tag_id No Third-party tag identifier.
3p_tag_fire_method No How the third-party tag should fire. Accepted values: none, once, per_impression.

Error Codes

Invalid Request Parameters

HTTP Code internal-code Message What it means
422 invalid_parameters Invalid or Missing Parameters The request is missing a required field or contains an invalid value. The most common cause is a missing snapshot_hash. If 3p_tag_fire_method is provided, it must be one of none, once, or per_impression. Check that all required parameters are present and correctly formatted.

PX Deal Configuration

HTTP Code internal-code Message What it means
422 px_deal_id_not_found This px deal does not exist, has not been linked, or has been deleted The PX Deal ID in the request URL has not been linked to a Lucit campaign. The deal has been registered in Lucit so it can be linked — log in to Lucit and associate this deal ID with a campaign.
422 px_deal_id_mapping_unknown_campaign This px deal is mapped to an unknown campaign The PX Deal ID is known but has not been fully linked to a campaign in Lucit. Open the deal in Lucit and complete the campaign association.
422 export_id_not_found This campaign does not exist, cannot be found, or has been deleted The campaign previously linked to this PX deal no longer exists in Lucit. It may have been deleted. Re-link the deal to a valid active campaign.

Campaign Setup

HTTP Code internal-code Message What it means
422 export_pull_not_supported This campaign does not support pulls via the lucore rest api v1 The linked Lucit campaign is not configured to serve creatives via the tag pull API. Verify that the campaign has the correct delivery settings enabled in Lucit.
422 export_xml_format_not_supported This campaign does not support delivering results on this endpoint via xml, try another supported format The campaign is not configured to deliver creatives in the XML/HTML format required by this endpoint. Contact Lucit support to review the campaign's delivery format settings.

Board / Screen Mapping

HTTP Code internal-code Message What it means
422 px_deal_id_mapping_unknown_board This px deal is mapped to an unknown board The Ad Unit ID (pxAdUnitId) in the request URL does not match any screen registered in Lucit for this deal. Verify that the Ad Unit ID is correct and that the screen has been added to the Lucit campaign.
204 (empty response) (no body) The screen was not previously associated with this campaign, but Lucit has automatically added it. The tag should begin serving on the next request. This is normal behavior during initial setup.
422 invalid_location_id Location id specified is invalid, has no creatives, or is not part of this campaign The screen identified by the Ad Unit ID is not part of this campaign, or the campaign has no creatives assigned to this screen. In Lucit, confirm the screen is included in the campaign and that at least one creative has been assigned to it.

Creative / Content Availability

HTTP Code internal-code Message What it means
422 export_puller_no_data No data is stored for this campaign or this data is unavailable The campaign exists in Lucit and the screen is configured correctly, but creative content has not been generated yet. This typically occurs immediately after a campaign is created or updated — content is usually available within a few minutes. If this persists, contact Lucit support.
204 (empty response) (no body) The campaign has no approved creatives available for this screen. This may mean all creatives are pending review, have been rejected, or the campaign has no active content. Check the creative approval status in Lucit. This response is always returned silently regardless of the silent_fail setting.

Unexpected Errors

HTTP Code internal-code Message What it means
422 export_puller_factory_uncaught_error (varies) An unexpected error occurred while preparing the campaign for delivery. The message will contain additional detail. This typically indicates a campaign misconfiguration in Lucit — contact support with the full error message.
422 export_puller_uncaught_error (varies) An unexpected error occurred while retrieving campaign content. The message will contain additional detail. Contact Lucit support with the full error message.
422 px_pull_html_unkown_error (varies) An unexpected error occurred processing the request. Contact Lucit support with the full error message and the PX Deal ID and Ad Unit ID from the request.

Silent Fail Behavior

When silent_fail=1 is included in the request, all 422 error responses are replaced with an empty 204 No Content response. This is the recommended setting for production ad tags since it prevents error markup from being rendered in the ad slot.

Use silent_fail=0 (or omit the parameter) during initial setup and troubleshooting to see descriptive error responses.

The two 204 responses listed above (screen auto-attach and no approved creatives) are always returned silently regardless of silent_fail.