Entry Link Error Codes
Entry links must also include a unique user ID, and an MD5 hash of the unique user ID and any applicable demographic data, if included.

Entry link with demographic data.
In the example above, the following demographic data was hashed:
- unique_user_id
- ip_address
- gender
- date_of_birth
- zip_code
Error codes
3432
and4tt32
are triggered when the MD5 hash is incorrect, or missing from the entry link.

Error code: 4tt32
To correct the issue, suppliers should hash all the demographic data and validate their entry link from the Supplier Dashboard:
MD5 HASH
The MD5 hash should not include the
si
,ssi2
,ssi3
, oroffer_id
parameters from the entry link.
Updated about 1 year ago
What’s Next