Skip to main content

How to resolve cdp_segments_invalid and cookie2_cdp_segments_invalid alerts

Updated

Overview

These alerts mean that one or more segmentation ID pairs in the cdp_segments value inside the cookie2 pixel parameter could not be validated for Discovery segmented search.

The alert does not always mean that every segmentation feature is unavailable. Event Diagnostics validates the segment values that are exposed to Search/Real-Time Segments (RTS). Merchandising segment values may not be available to that validator.

Recommended implementation

Send only the segmentation ID and segment ID pairs that are exposed to Discovery Search/RTS in the cdp_segments value.

The value must be Base64-encoded and appended to the normal cookie2 value. For example:

uid=<cookie_uid>:v=<tracker_version>:ts=<timestamp>:hc=<hitcount>:cdp_segments=<base64_value>

Do not add merchandising-only segment pairs to the Discovery pixel. If your implementation currently sends both Search and merchandising segments, the merchandising pair can be reported as invalid even when the Search segment is valid.

Troubleshooting steps

  1. Capture the affected event. Record the account ID, domain key, event timestamp, and the complete cookie2 value with any personal identifiers removed.

  2. Inspect cdp_segments. Decode the value and list each segmentation_id:segment_id pair.

  3. Check the segment type. Confirm that every pair is exposed for Search/RTS, not only for merchandising.

  4. Check the IDs exactly. The segmentation ID and segment ID must be valid, current, and known to the Search integration. Check for stale IDs, missing pairs, spelling differences, or values from another environment.

  5. Retest after clearing the old cookie. Generate a new visitor cookie and confirm that the new event contains only the intended Search/RTS pairs.

  6. Review Event Diagnostics again. A valid Search/RTS pair should no longer produce the invalid-segment alert.

When to contact Support

Contact Bloomreach Support if:

  • A Search/RTS segment is present and correctly encoded but is still reported as invalid;

  • The same pair is valid in the Discovery configuration but is not recognised in Event Diagnostics; or

  • You need help identifying whether a segmentation is exposed to Search or only to merchandising.

Include the account ID, domain key, a redacted sample of the decoded pair, the event timestamp, and a screenshot of the alert.

Related documentation