prefill all form fields based on contact ID
C
CJ Gorrell
It would be great to be able to associate each form field with a contact value(custom or standard). If the contact id parameter is added to the form url and a parameter like "autofill=true" is added, the form will pre-fill any field where the existing contact has data. So instead of creating an explicit parameter for each form field, only two parameters are needed, and any updates to the form don't require the url to be updated to match.
Log In
C
Cate Scolnik
Have you seen and tried this: https://www.youtube.com/watch?v=V4hjy-fdZPA
It's a short video on how to use trigger links to get form fields prefilled, and tells you why you should include the contact ID. The code to add is in the comments too.
L
Lars Nelissen
This works but not on mobile: https://example.com/widget/form/abc123xyz?contact_id={{contact.id}}&prefill=true
It populates nicely on desktop, but not on mobile. The 'birth date' field also doesn't pre-populate.
B
Brook Borup
So right now we can use the variables but they only pull the data that was typed into the form before not data that was uploaded or already populated. Its like it does half but it relies on cookies so when the cookies on a browser have to be erased all the data disappears.
C
Clifford Paulick
Right now, you can do this to UPDATE an existing contact, although it still will not prefill their form fields like we want:
https://example.com/widget/form/abc123xyz?contact_id={{contact.id}}
Adding an additional URL parameter like initially proposed:
&prefill=true
would be excellent because:
1) it wouldn't break existing functionality of tying a form submission to a contact (like I demonstrated)
2) it wouldn't break existing functionality of Sticky Contact, which GHL Support confirmed is only intended to be browser-based, not contact-based. plus, Sticky Contacts don't work on Hidden fields or Custom fields.
3) I could combine prefill functionality with URL query parameters, which would take precedence, such as to get the user to update their own contact information themselves but with the ability to override the query parameter's value:
...?contact_id={{contact.id}}&value=7
-> when their current CRM value=6
but they could choose to change it to 8
Related ticket# 2626538
ע
עידן זיואון
Clifford Paulick if you a have survey with 4+ pages (10+ fields) it will be too complicated.
C
Clifford Paulick
עידן זיואון what do you mean by “too complicated“?
ע
עידן זיואון
Clifford Paulick it will be a long line and you have to define each variable.. ex: ?name={{contact.name}}&phone={{contact.phone}}&..&..&..&..&..&..&..&..&..&...
C
Clifford Paulick
עידן זיואון that's the point - that would be solved by passing ALL custom field values via the
contact_id
URL paramF
FusionPro Staff
📣📣 This is so important! I have to allow duplicate contacts for our business, but when the contact fills out a form, it just creates a new contact with the information gathered, and it's very messy to keep the data organized. Help!
M
Michael Romrell
This is required in cases that we have to turn on "Allow Duplicate Contacts" for a location (done when many contacts have the same building phone number). Since that option also removes the ability to update an existing contact by matching their email to new form submissions, We have no alternative in the form to match a contact to a form submission using their contact ID.
Side request: change "Allow Duplicate Contacts" to two different settings 1) "Allow Duplicate Phone numbers" and 2) "Allow Duplicate Emails" ---- Until then, we need the ability to prefill form fields (Or match form submissions) based on the Contact ID.
J
JJ King
Along the same lines, it would also be nice to be able to fill funnel dynamic data based on contact id.
J
Jeanette De Witt
Yes! Agreed!