> ## Documentation Index
> Fetch the complete documentation index at: https://docs.remapdb.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Custom button

> Replace the quote button with your own contact or booking link and optionally send the selected vehicle and tuning figures to your website.

Use a custom button when visitors should contact you or book through another page instead of the Remapdb quote form. The button appears in the vehicle results, in the same position and style as **Request a Quote**.

Custom buttons are included with **Plus, Pro, API, and Max**. Free accounts can hide quoting but cannot display a custom replacement. Existing paid accounts receive access without waiting for renewal.

## Set up the button

**1. Turn off quoting**

Open [Quoting](https://app.remapdb.com/widget/quoting) and turn off **Enable quoting**. Your quote form settings remain saved.

**2. Enable your custom button**

Turn on **Enable custom button** to reveal the settings. Enter **Button text**, such as “Contact us” or “Book an appointment”, and a full **Destination URL**, such as `https://example.com/contact`.

The label allows up to 100 characters and is used in every widget language. The destination allows up to 2,048 characters and must use HTTP or HTTPS. Relative URLs, credentials in URLs, and executable links are not supported.

**3. Choose how the link opens**

Choose **New tab** (the default) or **Current browser tab**. Current browser tab navigates the whole website page, not just the widget iframe.

**4. Optionally include vehicle details**

Turn on **Include vehicle details** if the destination can read the query parameters described below. Leave it off to use your destination without adding parameters.

**5. Save and test**

Click **Save**. The live preview shows the complete widget, including vehicle selection, vehicle results, and your custom button. It uses the same preview as **Widget → Settings**. The custom button opens your configured destination with details from the displayed vehicle when enabled.

On your website, load a vehicle and test the button. Confirm the destination opens correctly and reads the details you need.

> [!NOTE]
>
> The destination must read these parameters itself. Adding them does not automatically populate Google Calendar, a booking provider, or a third-party contact form. Check the destination's supported integration before enabling vehicle details.

## Styling and quoting behavior

The custom button uses the existing quote button colors, size, and layout. Style it through [Branding](https://docs.remapdb.com/widget/branding); your plan's existing styling permissions still apply. For custom CSS, the replacement link has the selector `#custom-vehicle-button`.

* The button becomes available after vehicle results load, for both catalog selections and registration lookups.
* Turning **Enable quoting** back on restores the native quote button. Your custom button settings remain saved.
* Turning off **Enable custom button** immediately disables the replacement and hides its settings. Its saved label, URL, and options are kept. Turning it on reveals the settings; click **Save** to activate it.
* With quoting and the custom button both disabled, neither button appears.
* A custom link does not submit a Remapdb quote, send quote emails, or consume the daily quote allowance.
* Losing paid-plan access hides the custom button without deleting its settings. It can return when access is restored. A scheduled downgrade takes effect at the scheduled plan change.

## Vehicle query parameters

When enabled, Remapdb appends the following fixed parameter names. Existing destination parameters and the `#fragment` are preserved. The `rdb_` prefix is reserved: remove existing parameters with that prefix before saving a destination with vehicle details enabled.

| Parameter | Value |
| - | - |
| `rdb_context_version` | `1` |
| `rdb_type` | Vehicle type name |
| `rdb_manufacturer` | Manufacturer or brand name |
| `rdb_model` | Model name |
| `rdb_generation` | Generation name |
| `rdb_engine` | Engine name |
| `rdb_vehicle_name` | Complete vehicle name, including engine |
| `rdb_power_unit` | `PS` (metric horsepower) |
| `rdb_torque_unit` | `Nm` |
| `rdb_oem_power` | Available original engine power |
| `rdb_oem_torque` | Available original engine torque |
| `rdb_stages` | URL-encoded JSON array of available tuning stages |

Names follow the vehicle results, including available translations and your catalog customizations. Missing names or measurements are omitted, not replaced with zero. Power and torque always use PS and Nm, regardless of the visitor's display-unit selection.

Each stage contains `stage_number`, available numeric `power` and `torque` values, and `estimated`. Stage order is preserved, including multiple entries with the same stage number. `estimated: true` identifies a registration-derived stage estimate; `false` does **not** certify a measured dyno result. An empty stage list is `[]`.

For registration hybrids, original engine figures refer to the combustion baseline used for stage estimates. Separate provider-reported figures that may include electric output are not substituted when that baseline is unavailable.

VINs, registration numbers, customer contact details, authentication tokens, and internal catalog IDs are not sent.

### Example

Given this destination:

```text theme={null}
https://example.com/contact?source=widget#enquiry
```

The link includes parameters such as:

```text theme={null}
https://example.com/contact?source=widget&rdb_context_version=1&rdb_type=Cars&rdb_manufacturer=Example&rdb_model=Tourer&rdb_generation=II&rdb_engine=2.0%20Turbo&rdb_vehicle_name=Example%20Tourer%20II%202.0%20Turbo&rdb_power_unit=PS&rdb_torque_unit=Nm&rdb_oem_power=150&rdb_oem_torque=300&rdb_stages=%5B%7B%22stage_number%22%3A1%2C%22estimated%22%3Afalse%2C%22power%22%3A190%2C%22torque%22%3A370%7D%5D#enquiry
```

After URL decoding, `rdb_stages` in this example is:

```json theme={null}
[{"stage_number":1,"estimated":false,"power":190,"torque":370}]
```

The figures above are sample data. URLs become longer with more stages, so test your destination's URL-length limits.

## Read the details on your website

URL parameters are visitor-editable. Validate them and treat them as enquiry context, not authoritative vehicle identification or a guaranteed price or performance result.

> [tab] JavaScript
>
> ```html theme={null}
> <label for="vehicle">Vehicle</label>
> <input id="vehicle" name="vehicle" maxlength="500">
> <script>
>   const params = new URLSearchParams(window.location.search);
>   if (params.get('rdb_context_version') === '1') {
>     document.getElementById('vehicle').value =
>       (params.get('rdb_vehicle_name') || '').slice(0, 500);
>
>     let stages = [];
>     try {
>       const parsed = JSON.parse(params.get('rdb_stages') || '[]');
>       if (Array.isArray(parsed)) stages = parsed;
>     } catch {
>       // Ignore malformed visitor-supplied stage data.
>     }
>     // Validate individual stage fields before using them in your integration.
>   }
> </script>
> ```

> [tab] PHP
>
> ```php theme={null}
> <?php
> $version = $_GET['rdb_context_version'] ?? null;
> $name = $_GET['rdb_vehicle_name'] ?? '';
> $vehicleName = $version === '1' && is_string($name)
>     ? mb_substr($name, 0, 500) : '';
> $rawStages = $_GET['rdb_stages'] ?? '[]';
> $stages = is_string($rawStages) && strlen($rawStages) <= 16000
>     ? json_decode($rawStages, true) : [];
> if (!is_array($stages) || !array_is_list($stages)) $stages = [];
> // Validate individual stage fields before using them in your integration.
> ?>
> <input name="vehicle" value="<?= htmlspecialchars($vehicleName, ENT_QUOTES, 'UTF-8') ?>">
> ```

## Troubleshooting

* **No button:** Check paid-plan access, turn off native quoting, enable and save the custom button, then load vehicle results.
* **Old label or URL:** Save the settings and reload the live widget.
* **Form is not populated:** Check that **Include vehicle details** is enabled and the destination explicitly reads the documented parameter names.
* **Missing values:** Some registration results do not supply all names or engine measurements; unavailable values are omitted.
* **Navigation blocked:** Test the live website outside its editor. A site builder's sandbox can restrict opening tabs or navigating the top page.

For native quote-form problems, see [Quoting issues](https://docs.remapdb.com/support/quoting-issues.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.