{“fields”:[{“name":“email”,“value”:"test.four+t4@yahoo.com”},{“name”:“firstname”,“value”:“t4-nf”},{“name”:“lastname”,“value”:“t4-nl”}],“context”:{“pageUri”:“local.test:8000\/aaa-bbb\/”,“pageName”:“Post: AAA BBB”},“legalConsentOptions”:{“consent”:{“consentToProcess”:true,“text”:“I agree to allow Example Company to store and process…”,“communications”:[{“value”:true,“subscriptionTypeId”:999,“text”:“Yes, I agree to receive other communications from YYY ZZZ”}]}}}
But when I view the signup, via Newsletter Submissions the Other Values (in the right sidebar / slide out) is something like:
Process consent
[green circle ] I consent
Yes, I agree to receive other communications fromYYY ZZZ.
[green circle ] I consent
So the Consent > Communications > text string is correct, but the Consent > text is only showing “I consent”, which isn’t what was sent. I presume I consent is a default. Fair enough. But why is HS using the default, when the text sent is different?
All the other values being sent are ok, best I can tell.
@dennisedson - Thanks again for the bump. When do you think this might be answered?
The good news is, while I’ve been waiting, I added some spam protection to my form using https://CleanTalk.org. I’ve heard good things. The price is nice. Implementation was straightforward. Etc. CAPTCHA be gone!
I’ve run some tests and I am seeing the same results as you are seeing. However, on the contact level, if you check the ‘communication subscriptions’ and view the history, you do see the set text in the explanation. So I suppose this is used to understand how the contact has given consent.
Thanks. To confirm…This is not a functionality bug. It’s more UX bug. The behavior is expected. The API POST is being done correctly. It’s captured correctly. However, HS has similar fields displayed differently.
Of all my questions I was certain this was the easiest. Boy, I was mistaken 