Hi,
Thank you for getting back to us.
By reviewing your query, I understand that your issue is regarding the
user_data_service.proto.
Please note that the 'v13' is deprecated and about to
sunset at the end of January 2024. I would recommend migrating to the latest version
v14 and you may follow this link to
Upgrade to the latest version.
Upon checking your screenshot, it appears that we are not able to see the complete value of the hashedEmail. Also, please refer to the article to know more
About the customer matching process and
About audience segments in Audience manager.
with that, please provide us with the complete API logs (
request and
response with
request-id and
request header) generated at your end in a text format.
If you are using a client library and haven't enabled the logging yet, I would request you to enable logging for the specific client library that you are using. You can refer to the guides
Java,
.Net,
PHP,
Python,
Ruby or
Perl to enable logging at your end. For REST interface requests, you can enable logging via the curl command by using the -i flag.