Yes, you can include an identifier for each recommendation and associate feedback with a logged-in user in Webflow—but only with workarounds or using third-party tools, as Webflow’s native form system has limitations.
- Use a Hidden Form Field to include the Recommendation ID (or slug).
- On the Recommendation CMS Template Page, add a hidden input field with a value bound to a CMS field (e.g.,
slug
, name
, or custom unique ID). Use Webflow’s CMS bindings to insert this dynamically. - This ensures each time someone submits feedback, it includes the identifier of the specific recommendation.
2. Capture Logged-In User Identity (Requires Memberstack, Outseta, or Similar)
- Webflow doesn’t natively support user login awareness in form submissions.
- Use a membership tool like Memberstack, Outseta, or Firebase Auth integrated with Webflow.
- With these tools, you can:
- Retrieve the logged-in user’s ID or email via JavaScript.
- Inject that info into a hidden form field, ensuring it’s submitted with the form.
- Example: Use custom JavaScript to populate a hidden input like
user_email
or user_id
once the user is authenticated.
- Webflow forms natively email the form data or send it to tools like Zapier or Make, but not into Webflow CMS itself.
- To store the feedback directly in the Webflow CMS, use:
- Zapier or Make (Integromat) to catch the form submission and create a CMS item.
- Pass along the recommendation ID and user data as part of the form payload.
4. Best Practices
- Clearly label hidden fields in Webflow and match them to your integration triggers.
- Validate user data privacy (especially with logged-in user emails).
- Consider CAPTCHA or spam protection if using hidden fields.
Summary
You can attach a recommendation identifier to feedback forms via hidden fields. To include the logged-in user’s identity, you’ll need a third-party login solution like Memberstack and custom scripts to insert user data into the form before submission.