Pass-Through Additional User Information
How to Pass Additional User Information in PAVE API
The PAVE API allows you to pass additional information about specific users in the JSON results for a session. This is useful when you want to combine information from different sources in a single session, for example, from a lead form on a website to the results payload sent to your CRM.
Separating Contact Name into First Name and Last Name
You can use the contact object within the session details to separate the contact name into two fields: first_name and last_name. If you are using the SMS method to send the capture link, you can keep the contact name separated into two fields instead of including the to_name in the sms object. The contact object is optional, but both fields are required if used.
Adding Additional User Information
You can add any additional user information in the reference object in the session details. PAVE will include any fields you provide within the reference object in your results payload and will delete it a few hours after the session completes.
IMPORTANT: Do not include any sensitive information such as credit card or social security numbers in these fields. PAVE requires you to use methods such as Cloud Data Loss Prevention (DLP) to de-identify sensitive data in text content. De-identification is the process of removing identifying information from data by masking, deleting, encrypting, or obscuring it.
Sample Request with Pass-Through Contact Information
Here is a sample request with pass-through contact information:
Sample Result with Pass-Through Contact Information
Here is a sample result with pass-through contact information:
Last updated