REVSET LABS · EXPERT GUIDE·Funnels & Websites
Fixing Custom Values Not Working on Landing Page in GoHighLevel
1,102 words·5 min read·Updated 28 April 2026·beginner· Quick Answer
To ensure custom values display correctly on your landing page via URL parameters, verify the custom field exists in Settings → Custom Fields and the parameter name matches the custom value key in your funnel's input field. This process typically takes 5-10 minutes.
Key Takeaways
- ✓Always verify your custom field exists and is correctly configured in GoHighLevel's settings before using it.
- ✓The 'Parameter Name' in your funnel's input field must exactly match the URL parameter you pass.
- ✓Test your URL parameters thoroughly by manually constructing test URLs after each configuration change.
- ✓Review any workflows or automations that might overwrite or incorrectly map custom field data after submission.
- ✓Clear your browser and GoHighLevel caches if values still do not appear, as stale data can cause display issues.
Understanding Custom Values and URL Parameters in GoHighLevel
Custom values are powerful tools in GoHighLevel that allow you to personalize content and pre-fill forms. When you pass these values through URL parameters, you create dynamic landing pages tailored to specific leads. If your custom values are not appearing on your landing page, it usually means there is a mismatch in how the field is set up, how the funnel input is configured, or how the URL parameter is structured. This guide will walk you through the precise steps to diagnose and fix these common issues.
✅ This guide assumes you have basic familiarity with GoHighLevel funnels and custom fields. Follow each step carefully to ensure proper setup.
Step 1: Verify Custom Field Existence and Type
The first step is to confirm that the custom field you intend to use actually exists in your GoHighLevel account and is configured correctly. An incorrectly set up custom field cannot receive or display data.
1
Access Custom Fields Settings — Click Settings in the left navigation menu. Then select Custom Fields from the submenu to open your custom field library.
2
Locate or Create Your Custom Field — Scan the list to find your desired custom field. If it does not exist, click + Add Custom Field and create a 'Text' field type for most URL parameter uses.
3
Note the Custom Field Key — Click on the custom field to edit it. Make note of the 'Field Key' value, as this will be crucial for mapping later.
⚠️ Ensure the custom field type matches the data you expect. Using a 'Number' field for text input will cause data display failures.
🔥 Pro Tip
Use descriptive and unique 'Field Keys' for your custom fields. This prevents confusion and potential conflicts when integrating with other systems or automations.
Once your custom field is confirmed, you must ensure the input element on your funnel page is correctly linked to this custom field and expects the right URL parameter name. This is a common point of failure.
1
Navigate to Your Funnel Page — Go to Sites → Funnels. Select the funnel containing your landing page, then click on the specific page to open its editor.
2
Select the Input Element — On your funnel page, click directly on the form input field where you expect the custom value to appear. This will open its properties panel on the right.
3
Link to the Custom Field — In the input field's properties, find the 'Custom Field' dropdown. Select the exact custom field you verified in Step 1 from the list.
4
Set the Parameter Name — Scroll down in the properties panel to the 'Advanced' section. Locate the 'Parameter Name' field and enter the exact 'Field Key' you noted from your custom field in Step 1. This name will be used in your URL.
⚠️ If the 'Custom Field' dropdown is not linked or the 'Parameter Name' is misspelled, your custom value will not populate the field.
🔥 Pro Tip
Always double-check the spelling and capitalization of your 'Parameter Name'. It must be an exact match to what you use in the URL.
Step 3: Construct and Test Your URL Parameter
After configuring your custom field and funnel input, it is time to test the setup by constructing a URL with the parameter and observing the result. This step confirms the data flow.
1
Retrieve Your Funnel Page URL — Save your funnel page changes. Then, navigate back to Sites → Funnels, locate your page, and copy its public URL.
2
Construct the URL with Parameter — Append your parameter to the URL using a question mark `?` followed by the 'Parameter Name' (from Step 2), an equals sign `=`, and your test value. For example: `yourdomain.com/landing-page?firstname=John`.
3
Test in an Incognito Browser — Open an incognito or private browser window. Paste your constructed URL and press Enter. Observe if the custom value 'John' appears in the designated input field.
⚠️ Do not test in a regular browser session if you have previously submitted data to the page. Browser caching can interfere with accurate testing.
✅ If the value appears, your setup is correct! If not, proceed to the next steps for deeper troubleshooting.
🔥 Pro Tip
Use simple, unique test values like 'TestName' or 'SampleData' to easily identify if the parameter is working correctly.
Try GoHighLevel Free
Start your 30-day GoHighLevel free trial
Everything in this guide is in your free trial. 30 days, no credit card — the platform behind 78+ revenue systems.
Some links are affiliate links — if you sign up we may earn a commission, at no extra cost to you. We only recommend GoHighLevel because we build on it every day.
Step 4: Review Workflow Automation and Field Mapping
Sometimes, the custom value might be correctly passed to the page, but subsequent automations or field mappings prevent it from being saved or correctly used. This step focuses on processes that occur after a form submission.
1
Access Workflow Settings — Go to Automation → Workflows. Identify any workflows that are triggered by a form submission on your landing page.
2
Inspect 'Update Contact Field' Actions — Within relevant workflows, look for actions like 'Update Contact Field' or 'Create/Update Contact'. Ensure these actions are not overwriting your custom field with a blank or incorrect value.
3
Verify Field Mapping in Forms — If your funnel page uses a GoHighLevel form, go to Sites → Forms. Edit the form and check its field settings. Ensure the form fields are correctly mapped to your custom fields.
⚠️ An automation might inadvertently reset a custom field to a default value or map it incorrectly if not configured precisely.
🔥 Pro Tip
Use the 'Test Workflow' feature in GoHighLevel to simulate a contact going through your automation. This helps identify issues without real contact data.
Step 5: Clear Caches and Re-test
Caching issues, both in your browser and within GoHighLevel itself, can sometimes prevent updated configurations from displaying immediately. Clearing these caches often resolves stubborn display problems.
1
Clear Your Browser Cache — Completely close all browser windows and clear your browser's cache and cookies. This removes any stored versions of your landing page.
2
Force GoHighLevel Page Refresh — While editing your funnel page, save your changes, then refresh the entire GoHighLevel platform in your browser. Sometimes, a hard refresh (Ctrl+F5 or Cmd+Shift+R) is needed.
3
Re-test with New Incognito Window — After clearing caches, open a fresh incognito window and re-test your constructed URL from Step 3. This ensures no old data interferes.
⚠️ Ignoring cache issues can lead to wasted time troubleshooting a problem that no longer exists in the backend.
🔥 Pro Tip
Always test significant changes in an incognito window. This isolates the test from your browser's history and cookies, providing a clean slate.
Step 6: Inspect for JavaScript Conflicts (Advanced)
For advanced users or pages with custom code, external JavaScript could potentially interfere with GoHighLevel's ability to parse URL parameters or populate fields. This is a less common but possible scenario.
1
Disable Custom JavaScript — Temporarily remove or comment out any custom JavaScript code added to your funnel page. This includes code in the Page Settings → Custom CSS/HTML or elements with custom code.
2
Test Parameter Functionality — After disabling custom scripts, re-test your URL parameter in an incognito window. If the custom value now appears, your JavaScript is likely causing a conflict.
3
Review Script for Conflicts — If a conflict is identified, carefully review your custom JavaScript for any code that manipulates form fields, URL parameters, or the DOM, which might interfere with GoHighLevel's native functions.
⚠️ Proceed with caution when modifying or disabling JavaScript, as it can affect other functionalities on your page.
🔥 Pro Tip
If you suspect a JavaScript conflict, add scripts one by one and re-test after each addition to pinpoint the problematic code.
Troubleshooting Common Issues
⚠️ Custom value field remains blank even after following all steps.
Double-check the 'Parameter Name' in your input field's advanced settings in the funnel editor. Ensure it's an EXACT match (case-sensitive) to the parameter name in your URL and the 'Field Key' of your custom field.
⚠️ Custom value shows up, but disappears after form submission.
Review any GoHighLevel workflows triggered by that form. An 'Update Contact Field' action might be overwriting your custom value with a blank or default value after submission. Adjust the workflow to retain or correctly map the data.
⚠️ Value only appears sometimes or on certain browsers.
This often points to a caching issue. Clear your browser's cache, cookies, and local storage. Test consistently in a new incognito window to eliminate browser-specific problems.
⚠️ The 'Custom Field' dropdown is empty for my input element.
Go to Settings → Custom Fields and ensure you have created the custom field. If it exists, try refreshing the funnel editor page. If it still doesn't appear, contact GoHighLevel support.
⚠️ I used the correct URL, but the field shows 'undefined' or 'null'.
Verify that the custom field type in Settings → Custom Fields matches the data you are trying to pass. For example, passing text 'John' to a 'Number' type field will cause issues. Change the custom field type to 'Text'.
Common Mistakes to Avoid
- →Misspelling the 'Parameter Name' in the URL or the input field, leading to no data transfer.
- →Forgetting to link the input field on the funnel page to the correct custom field in its settings.
- →Not saving changes in the funnel editor or custom fields settings before testing the URL.
- →Testing in a browser session with old cache or cookies, which can mask current configuration issues.
- →Using a custom field type (e.g., 'Number') that does not match the data type being passed through the URL parameter (e.g., text).
Frequently Asked Questions
QWhat is the difference between a 'Custom Field Key' and a 'Parameter Name'?
The 'Custom Field Key' is the internal identifier for your custom field within GoHighLevel, found in **Settings → Custom Fields**. The 'Parameter Name' is what you assign to an input field on your funnel page, telling it which URL parameter to listen for. For custom values to work, the 'Parameter Name' you define on the input field must exactly match the 'Custom Field Key' of the custom field you link it to, and also the parameter name used in your URL.
QCan I pass multiple custom values through a single URL?
Yes, you can pass multiple custom values. After the first parameter (which starts with a `?`), subsequent parameters are added using an ampersand `&`. For example: `yourdomain.com/page?firstname=John&lastname=Doe&email=john@example.com`. Each parameter name must correspond to a correctly configured input field on your landing page.
QWhy is my custom value showing on the page but not saving to the contact record?
If the value appears but doesn't save, the issue is likely with the form submission or subsequent automation. Ensure your form field is correctly mapped to the custom field. Also, check any workflows triggered by the form submission; an 'Update Contact Field' action might be overwriting the data or failing to map it correctly to the contact record.
QDoes the order of URL parameters matter?
No, the order of URL parameters generally does not matter. As long as each parameter is correctly formatted with its name and value (e.g., `?param1=value1¶m2=value2`), GoHighLevel will parse them independently. The critical factor is that the parameter names in the URL exactly match the 'Parameter Name' set on your funnel page's input fields.
QWhat if my custom field is a dropdown or multi-select type?
Passing values to dropdowns or multi-select fields via URL parameters requires the URL parameter's value to exactly match one of the predefined options in your custom field. For multi-select, you might need to pass comma-separated values, depending on how your specific GHL setup handles it. Always test thoroughly with exact option values to ensure proper population.
Try GoHighLevel Free
Start your 30-day GoHighLevel free trial
Everything in this guide is in your free trial. 30 days, no credit card — the platform behind 78+ revenue systems.
Some links are affiliate links — if you sign up we may earn a commission, at no extra cost to you. We only recommend GoHighLevel because we build on it every day.
Arsalan Zaffar
Revset Labs · Revenue Systems · 78+ GHL Builds
Arsalan writes GHL guides from real build experience — 78+ systems, $9.2M in client pipeline. Wharton, CXL & Google certified.
Connect on LinkedInTags:GoHighLevelCustom ValuesURL ParametersFunnelsLanding PageTroubleshootingAutomationCustom Fields
