Documentation Index
Fetch the complete documentation index at: https://docs.mention-me.com/llms.txt
Use this file to discover all available pages before exploring further.
Overview
The order tracking tag captures conversion data when a customer completes a purchase. Place it on your order confirmation page alongside the referrer tag, or use it standalone if you only need conversion tracking without the referral overlay.Integration
- JavaScript tag
- 1x1 tracking pixel
Add this snippet to the bottom of the
<body> tag on your order confirmation page:Parameters
Both the JavaScript tag and the tracking pixel accept the same parameters.Mandatory
The customer’s email address. Please URL encode. Example:
doreen@example.comThe unique order identifier from your system. Has a maximum of 50 characters. Example:
ORD-12345The order subtotal (excluding VAT/taxes and shipping) in the currency indicated by the
order_currency parameter. If you can’t remove VAT, let us know. Example: 49.99The three character (ISO 4217) currency code that the order total is in. Example:
GBPThe coupon code used by the customer (if any). Example:
SAVE10Recommended
The unique customer identifier from your system. Example:
CUST-789The number of items in the basket (if applicable). This helps us understand the type of purchase and can be a signal of advocacy. Example:
3The discount amount — our assumption is this has already been taken off the order subtotal provided. This allows us to calculate the Cost Per Acquisition for referral. Example:
5.00String representing a customer segment (for example one of: men, women) used to pass segmentation data about your customer to us. Has a maximum of 50 characters. Example:
vipWhether this order is for a subscription (recurring). This helps us qualify and categorise the revenue. Example:
trueWhether this order is a gift (being bought for someone else). Gifts can be signals of advocacy. Example:
falseOptional parameters
Optional parameters
Any piece of custom data you wish to pass to us.
The customer’s address line 1 (if known).
The customer’s address line 2 (if known).
The customer’s address city (if known).
The customer’s address county (if known).
The customer’s address postcode (if known).
The customer’s address country (if known).
A piece of text you can use to pass into sharing widgets, such as what the user bought or how much they saved.
The date and time the order was placed. The format must be in ISO 8601 format and URL encoded. If not provided or invalid, we will use the date and time at the point we received the tag.
In some cases it may be desirable to ensure that email addresses and other information is not in clear text. See encrypted parameters.
Locale code (e.g.
en_GB).Verb Aliases in the URL
The verb in the URL path (order) can be replaced with booking, signup, or transaction, matching whichever term best describes the action on your site. All four verbs behave identically.
The same applies to the pixel form: orderpixel can be replaced with bookingpixel, signuppixel, or transactionpixel. Each pixel verb still ends with /pixel.gif.
For example, a signup pixel would look like:
Parameter Aliases for Non-Ecommerce
If your business tracks bookings or signups rather than orders, you can use alternative parameter names. The tag behaviour is identical — only the parameter names differ.Booking aliases
Booking aliases
Alias for
order_number.Alias for
order_subtotal.Alias for
order_currency.Alias for
order_date.Alias for
order_item_count.Alias for
order_is_subscription.Alias for
order_is_gift.Alias for
order_discount_amount.Signup aliases
Signup aliases
Alias for
order_number.Alias for
order_subtotal.Alias for
order_currency.Alias for
order_date.Alias for
order_item_count.Alias for
order_is_subscription.Alias for
order_is_gift.Alias for
order_discount_amount.