Passing your Source URL to CRM via Concierge

Concierge can automatically capture the page URL where a prospect submitted your form (the source URL) when you pass it in as a Data Field, and also write it to your CRM fields afterward. 

Because this Data Field is not a standard field in most form tools/CRMs, you will need to add it to your form mapping. It will be automatically populated at submission time, as Chili Piper passes the source URL in the form submission data.

Table of Contents

• What does passing sourceURL do?
• Step 1: Create your Data Field and Map to CRM
• Step 2: Add the Data Field to your Concierge Form Mapping
• Step 3: Test and Validate

What does passing sourceURL do?

When you pass a data field named sourceURL into Concierge, Concierge can capture the URL of the page where the form was submitted and use it in routing, logging, and downstream workflows (depending on your setup).

Common use cases include:

• Reporting on which landing pages generate meetings
• Routing differently based on the page a prospect came from
• Storing the submission page URL alongside the lead/contact for context

Step 1: Create your Data Field and Map to CRM

1. As an Admin, navigate to the Data Fields option in the Admin Center's left-hand menu.
2. Click Create Person Data Field on the right-hand side.
3. Give the Data Field a name. Tip: Use the Source URL or something similar for easier searching.
4. You may want to change the Data Format to Long Text to accommodate certain URLs, rather than Short Text. 
5. Expand Mapping to Salesforce/HubSpot and click Add Mapping
6. Select the Object you would like to map to
   1. Salesforce available objects are: Lead, Contact, Account, Opportunity, Case
   2. HubSpot available properties are: Contact, Company, Deal, Ticket
7. Then, select the Field.
8. Enable the Overwrite setting if you want to overwrite previously existing values with new ones from the form submissions. Fields with no previously filled-in data will still have the form data written, regardless of whether Overwrite is enabled.
9. Once ready, publish it

Note: If your CRM field is not available in the search done in step #7 of this section, you may want to check if the Data Format used (step #2 of this section) is correct. 

For example, if you created the Chili Piper Data Field as a picklist but your CRM field is a short-text field, it won't appear in the search because the Data Format between Chili Piper and your CRM must match.

Step 2: Add the Data Field to your Concierge Form Mapping

First, ensure Concierge is expecting a field named sourceurl from your form submission payload.

1. In Chili Piper, open Router under Concierge in the left-hand menu. There, open the relevant Router that is connected to your form.
2. Click and open the Router’s Trigger 
3. Within the Webform is submitted option, click Add Mapping
4. For the Form Field Name field, you can map it as sourceurl, sourceUrl, sourceURL, or variations of this wording. Different naming, such as source_URL, source-url, 0-1/source-url, will not work.
5. In the Data Fields column, associate with the Data Field created in Step 1: Create your Data Field and Map to CRM
6. Publish your changes once ready
   
   

Step 3: Test and Validate

After configuring the Data Field and mapping, you can run a test submission to confirm that Chili Piper and your CRM are receiving the value.

1. Open a landing page where you can test the form.
2. Submit a test lead form submission.
3. Confirm the Concierge flow runs as expected (routing/scheduling). Depending on your setup, you do not need to book a meeting to check if the field was populated.

4. Open the submission details in the Logs page, which is located under Concierge in the left-hand menu. 
   The form data will be seen in the following places if it was received correctly from the submission:
   

   

5. Check in your CRM if the mapped field was also populated.