User identifying hidden field error

Hi @churry How are you passing the user ID into the form? 

Hello Liz, 

I am sending the link via push notification. Users can click on the push notification and be directed to typeform page, during which the user_id from the db should be transferred to typeform and then be recorded in the user_id column. This is how it used work fine, but started failing recently as the image above. 

Ohhh interesting. I actually haven’t seen a typeform in a push notification before. @mathio have you seen this? 

@Liz neither have I. I think this is a clever approach and could lead to high submission rate.

@churry are you displaying the typeform in your app or are you opening it directly in device browser? Are you sure the value is populated correctly in the URL when your typeform is opened?

Hello @mathio

More the latter. On the app, only push notification is visible to users, and only when they click on it, they are directed to typeform web browser to start fill in the survey. 

I do make one adjustment to the deeplink, which in the original typeform link, the hidden variable appears as 

• #user_id=xxxxx

When I insert the link in our deeplink, I change this to 

• ={user_id_secure}

Not exaclty sure why I have to do this, but was told to do it. And this has been working fine for a time until my orginal inquiry started happening few weeks ago..

Hi @churry 

I dont think this is a change on our end. If you see the value as {user_id_secure} that means this is what you pass as a value in the URL.

It looks like your app is not putting user ID value into your typeform URL.

You mention deep linking - are you displaying the typeform in your app inside a webview or are you opening it directly in device browser?