Data Pass Case Guide

Vehicle Data Pass Script Generator

Set up a button on an inventory listing to carry vehicle information to a custom page and fill in the matching custom form field. Start with the case workflow, then use the generator below.

What is a data pass?

A data pass sends a value from a vehicle on a Search Results Page (SRP) or Vehicle Details Page (VDP) to a custom form. For example, a button can include that vehicle's VIN in the custom page URL. The script on that page reads the URL and fills the VIN field in the form.

VIN example: The Pricing 2.0 button points to a custom page with a VIN parameter. The generator supplies the query string for the button and the script for the custom page. /custom-page.html?vin=#VIN# The #VIN# replacement code is filled with the vehicle's VIN when the inventory button is rendered.

How to Complete a Data Pass Case

Case titles vary. Look for a request to send vehicle data from an inventory button to a custom page with a form, even if the case does not say “Data Pass” or “VIN Pass.”

  1. Confirm the requested data

    Identify which value the dealer wants in the form, such as VIN, stock number, year, make, or model, and which inventory button should send it.

  2. Get the custom form code

    Review the case for the form code. If it is missing, return the case to Support and ask them to add it before continuing.

  3. Find the destination field

    Check that the form has an input for each requested value. For VIN, a field labeled “VIN Number” could have id="field5". Add the field to the form if the requested input is missing.

  4. Check field numbering

    Verify that the form's numbered fields run in order, from field1 through the last field, with no duplicate IDs or names. In the example, VIN is field5 and Comments is field6.

  5. Locate the inventory button

    Look in Pricing 2.0 first. If the button is in Inventory Settings or a VDP block, assess whether it should be moved into the Pricing 2.0 price stack so Support can manage it there.

  6. Locate the custom page

    Use the destination URL in the case. If it is missing, return the case to Support and ask for it in the URLs section. Add the supplied custom form to that page.

  7. Configure the generator

    Select the vehicle values to pass and enter the matching form field's CSS selector. For the example VIN input with id="field5", select VIN and enter #field5.

  8. Add the custom page script

    Copy the generated script into the custom page's Body Bottom section. Choose the hide option below only if that form field should disappear after a value is passed.

  9. Update the button URL

    In Pricing 2.0, append the generated query string to the custom page URL and save the button. The Complete URL output below can help you check the finished link.

  10. Test an actual vehicle

    Use the red “View Current Client Without Cache” button, open an SRP or VDP, click the button linked to the custom page with the custom form, and confirm the correct vehicle value appears in the custom form.

Custom Form Example: VIN in field5

The field numbers in this example show the correct order: first name through email use field1 to field4, VIN uses field5, and comments use field6. Keep any other required form fields and tracking code from the case.

<div class="dealerOnform" id="TestCustomForm">
<div class="form-group">
<label for="field1">First Name</label>
<input id="field1" name="field1" type="text">
</div>
<div class="form-group">
<label for="field2">Last Name</label>
<input id="field2" name="field2" type="text">
</div>
<div class="form-group">
<label for="field3">Phone</label>
<input id="field3" name="field3" type="tel">
</div>
<div class="form-group">
<label for="field4">Email</label>
<input id="field4" name="field4" type="email">
</div>
<div class="form-group">
<label for="field5" class="control-label">VIN Number</label>
<input id="field5" name="field5" type="text" class="form form-control" placeholder="VIN Number" rel="">
</div>
<div class="form-group">
<label for="field6">Comments</label>
<textarea id="field6" name="field6"></textarea>
</div>
</div>

1. Select data and match the form fields

Choose each value requested in the case. Enter the CSS selector for its destination input on the custom form. An input with id="field5" uses #field5. The numbers shown below are examples; check the actual form code.

2. Add the script to the custom page

Copy this script into the custom page's Body Bottom section, where the form is installed. This version uses jQuery to fill the selected fields. It leaves them visible unless you select the option below.

When selected, the generated script hides each populated field's immediate parent element. For the example form, that parent is its .form-group. Leave this unchecked if visitors should see the passed values.

Custom page script

3. Update the inventory button URL

Copy the Query String and add it to the custom page URL used by the button in Pricing 2.0. The first parameter starts with ?; additional parameters start with &. Save the button, then test it on an actual SRP or VDP vehicle.

Enter the page URL to build a complete example. Leave this blank to copy just the query string.

Query String

Complete URL

Example Button HTML

The HTML is a reference for checking the link. Update the existing inventory button in Pricing 2.0 for the case.

Replacement codes such as #VIN# and #STOCK# must be evaluated on the inventory button. Check the rendered link and the form value when testing.

If the value does not appear in the form

  1. Check the form: Confirm the requested input exists, its ID and name are unique and correctly numbered, and the generator selector matches it exactly. For the VIN example, use #field5.
  2. Check the button: Open a real vehicle listing and inspect the button's final URL. For VIN, it should include a value after ?vin=, not an unresolved #VIN# token. Confirm the button opens the intended custom page.
  3. Check the custom page: Confirm the form and generated script are on the destination page, the script is in Body Bottom, and jQuery is available. Test with Feature Overrides if the changes are not showing.
  4. Ask for help: If the form, URL, and script all look right but the data still does not pass, ask another designer in #design-internal or #creative-support.