Claspo can send not only the fields collected in the widget, such as email or name, but also extra data: submission details, location, device and browser data, UTM tags, and marketing click IDs.
You can map each Claspo field to a matching field in your CRM, spreadsheet, email platform, or another connected app.
What data you can map
The available fields may depend on the widget and the integration you use. In most cases, you can map several types of data.
Regular form fields
Regular form fields are the fields visitors fill in or interact with in the widget:
First name
Email
Promo code
For example, if your widget collects an email address and shows a promo code after submission, you can send both values to your email platform, CRM, spreadsheet, or another connected app.
Hidden fields
You can also map hidden fields. These fields are not shown in the widget, but Claspo can still collect their values and send them with the submission. Use them for custom website data, such as user IDs, product details, or other internal values.
Read the Hidden fields article to learn how to set them up.
Context fields
Context fields describe the submission or visitor context:
Submission date & time
Site language
City
Country
Country code
These fields help you understand where and when the submission came from. For example, you can pass the visitor’s country to your CRM or send the submission date and time to Google Sheets for easier reporting.
Device and browser fields
These fields show what device or browser the visitor used. You can map:
Device language
Device class
Operation system
Environment
Browser name
IP
This data can help with troubleshooting, segmentation, or reporting. For example, if you receive a support-related submission, browser and device details can give your team extra technical context.
UTM fields
Claspo can pass UTM values stored for the visitor’s session. For example, if a visitor lands on your site through this URL: https://example.com/?utm_source=facebook&utm_campaign=spring_sale Claspo can keep the UTM value during the session, even if the visitor opens another page where the UTM tags are no longer visible in the URL.
You can map:
UTM source — where the visitor came from, such as Facebook, Instagram, or newsletter.
UTM medium — the traffic type or channel, such as CPC, email, or social.
UTM campaign — the campaign name or label.
UTM term — the paid search keyword, if used.
UTM content — the specific link, button, banner, or ad variant.
This can help you pass campaign context to your CRM, spreadsheet, email platform, or automation tool.
Marketing click IDs
Marketing click IDs are added by advertising platforms and analytics tools. They help pass ad-click context with the submission. In Field mapping, you can map values such as:
Google gclid
Facebook fbclid
TikTok ttclid
LinkedIn li_fat_id
Microsoft msclkid
Twitter twclid
Pinterest epik
Reddit rdt_cid
Snapchat sccid
Amazon ascsubtag
Before you start
First, create the needed field in the app that will receive the data. Claspo only maps to fields that already exist there. For example, to send Google gclid to your CRM, add a GCLID field in the CRM first. After that, it can become available in Claspo Field mapping.
Some apps do not support custom fields or field mapping. In that case, they may not be able to receive all Claspo fields.
How to map fields
1. Open your widget.
2. Go to Integrations.
3. Add a new integration or open an existing one.
4. Find the Field mapping section.
5. Find the Claspo field you want to send.
6. Open the dropdown on the destination app side and choose the matching field.
7. Click Done to save the integration.
If a value is missing
If a mapped value is not available, Claspo will not send it for that submission.
However, the form itself still works as usual. For example, if a visitor does not have a gclid value in the session, the form can still be submitted, but the Google gclid field will not be passed.
Troubleshooting
The field does not appear in the dropdown
Make sure the matching field or property already exists in the destination app. Claspo only lists the fields that are available in the connected app. If the field is not in the dropdown, create it in that app first. Then reopen the integration settings in Claspo and check the list again.
The field stopped working after renaming
If you rename a field after setting up Field mapping, the integration may stop receiving this value. After renaming a field, open the integration settings and check the mapping. You may need to select the field again. Then send a test submission to make sure the value reaches the connected app.
The value appears in Claspo but not in the integration
Open the integration settings and check the mapping. The value can be stored in Claspo, but the connected app receives it only after you map it to one of its fields. If you do not see the needed field in the app, create it there first and then return to Claspo.