Pixel Parameters Recommended Implementation

This guide details how to correctly implement pixel parameters.

Recommended Implementation of br_data.user_id for Web Users

br_data.user_id Parameter Overview

Parameter DescriptionParameter Value type with example
If you track users via a universal customer ID, populate this parameter with that ID. This should be an anonymized string and should not contain the user's email or other personally identifiable information.

This parameter is only required if you track users via a universal customer ID. Ensure that the tracking of users aligns with your privacy policy and your country's regulations.

This parameter allows Bloomreach to recognize identified users in a way that is aligned with your system for various personalization features. Please note that the correct implementation of this parameter can vary for different user scenarios. Learn what parameter value you can set for each scenario in the next section.

If you do not track users this way, leave this blank.
string, "947345478564"

Recommended Implementation

If you track users, here’s how you can correctly implement the br_data.user_id parameter for various web user scenarios:

Web User Scenariosbr_data.user_id Implementation
1.User is a Guest (or Anonymous) userDo not set br_data.user_id field or value.
Alternatively set it to an empty string br_data.user_id = "";
Common mistake is to set "null" or "undefined".
2.Guest user logs in i.e. becomes a Logged-in User
  • Always send the universal user ID. For instance:br_data.user_id = "61WwurfPU9f9dB5";
  • Avoid sending personally identifiable information such as a clear text email address or username.
3.User logs out i.e. becomes a Guest user againAfter logout, do not set br_data.user_id value, or set it to an empty string br_data.user_id = "";

Note: When the user logs out, then the visit breaks.