Understanding how to pass Order ID and Order Amount values into your MNTN Conversion Pixel can significantly improve attribution accuracy and reporting insights. This guide covers how to use dynamic and hardcoded variables, structure multiple conversion points, and configure revenue values—giving your team the tools to de-duplicate conversions, align data with internal systems, and make the most of the Conversion Details Table in reporting. Whether you're tracking purchases, form fills, or subscriptions, these fields help match campaign results to real business outcomes.

⚠️ Warning: The details below typically work for our client base; however, the capabilities outlined in this article are entirely dependent on what's available within your site's configuration and setup.

The Conversion Pixel's Order ID field allows you to match MNTN-attributed conversions to your internal database and records. The order ID field can be leveraged for any unique identifier associated with the conversion event.

To leverage a specific unique ID, that ID must exist within your site's data layer or the URL of the conversion confirmation page.

⚠️ Warning: You can't pass personal privacy information (PII) into the conversion pixel's order ID field. PII includes: names, email addresses, phone numbers, etc.

We recommend leveraging a dynamic order ID mapping within the order ID field:

📘 Example: Identifiers: purchase order ID, confirmation ID, lead ID, subscriber ID, quote ID, booking ID, etc.

You can also leverage hardcoded parameters within the order ID field. This is helpful for identifying conversion event types within the Conversion Details Table.

However, a hardcoded order ID mapping does not allow our system to de-duplicate conversions in your MNTN Reporting Dashboard. This is why we recommend leveraging a hardcoded parameter and a dynamic variable if wanting to utilize a hardcoded parameter.

You can leverage several variables within the order ID field. This can be any combo of identifiers and parameters:

📘 Example:

If your team is tracking multiple conversion events with the MNTN conversion pixel, the order ID field can be used to differentiate the conversion types driven by your efforts within the Conversion Details Table.

⚠️ Warning: We do not recommend having multiple conversion points if your conversion types are not of equal value.

Formatting comes down to what is most important to your team's needs, however, you can move forward with mapping in the unique dynamic IDs associated with the conversion events, or a combo of hardcoded and dynamic variables.

📘 Example:

If you need help mapping several variables into the order ID field of your conversion pixel, reach out to us for guidance.

You can also map an accompanying Order Amount to the conversion pixel's order amount field, allowing you to attribute revenue to a given on-site conversion event.

💡 Pro Tip: When mapping order amount, keep in mind if you want that field to be inclusive or exclusive of tax and shipping when referencing revenue metrics in your reporting dashboard.

In most cases, the order amount field would be the purchase amount. However, this field can also be used if you consider a non-revenue conversion point as carrying specific value to your business.

Within MNTN's Reporting Dashboard exists the Campaign report. The Campaign report houses the Conversion Details Table, which breaks out the below within a line item:

The Conversion Details table can be exported as a CSV, Excel, or JSON file to compare these unique, MNTN-attributed conversions back to internal records across the defined date range: