We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
https://developers.facebook.com/docs/marketing-api/conversions-api/guides/gtm-server-side
Documentation suggest passing hashed user data as user_data.email_address, etc.
When this data is undefined/null on web container, it does not get removed from server side capi call, instead undefined gets hashed.
Workaround is to use x-fb-ud-em, etc.
The text was updated successfully, but these errors were encountered:
Good call! This was kicking my ass!
Sorry, something went wrong.
It is there for null but not undefined
function hashFunction(input){ if(input == null || isAlreadyHashed(input)){ return input; } return sha256Sync(input.trim().toLowerCase(), {outputEncoding: 'hex'}); }
One could rewrite that first line to handle undefined
undefined
Looks like this is resolved incommit e4ebdf48fdfee975755614579e9664be7876a235
No branches or pull requests
https://developers.facebook.com/docs/marketing-api/conversions-api/guides/gtm-server-side
Documentation suggest passing hashed user data as user_data.email_address, etc.
When this data is undefined/null on web container, it does not get removed from server side capi call, instead undefined gets hashed.
Workaround is to use x-fb-ud-em, etc.
The text was updated successfully, but these errors were encountered: