Sending custom form data with conversion events
As of Conversion Bridge 1.6, it is possible to include specific form data submitted by users with your conversion events for specific form integrations. Currently supported are WS Form Pro, Gravity Forms and Ninja Forms with more in the works.
Every platform has specific requirements for how data should be sent. Allowing you to have direct control over what gets sent means you are taking on the responsibility of doing so properly to best work with your integrated platforms. So please take the following into strong consideration:
Sending personally identifiable information
When sending data, it is important to understand what you are sending to your analytics or ad platforms. No analytics platforms want personally identifiable information while ad platforms do.
If you are sending personally identifiable information, it is important to set your key to start with an underscore “_”. This is how Conversion Bridge identifies personally identifiable information and will filter it out when sending the conversion events to analytics platforms while allowing it to be sent to ad platforms. For example, if you were to send an address you would want to set the key to be “_address”.
Predetermined key names
Since each platform wants to receive information in their own specific way, Conversion Bridge has predetermined key names that you should use:
- _first_name: First name
- _last_name: Last name
- _email: Email (recommended minimum to include)
Conversion Bridge will recognize these special keys and transform them into the necessary format for each of your integrated platforms.
Still need help?
If you have not yet found your answer in the documentation articles, please contact support
Contact support