Understanding Integration Log Fields

Each event on the Logs page shows fields such as Customer, Order total and Source. These are Mention Me’s names for the values your tags, order files and APIs send us. A field means the same thing on every event type, whether it came from a referrer tag, a customer dashboard tag or an order upload. Open an event, then look under Documented properties in this payload to jump to the matching entry below.

​

Customer

​

Customer Email

The customer’s email address. It comes from the email parameter on every tag, and it is the main way we recognise a customer.

​

Customer ID

Your own identifier for the customer, from the customer_id parameter.

​

Hashed Email

A one-way hash of the customer’s email (SHA-256, combined with your secret key), sent instead of the email itself. It only appears on orders sent in files, through the CustomerHashedEmail column in SFTP data files or an order upload. Tags never send it. Orders with a hashed email do not reward referrers or referees. See Hash Historical Customer Emails for the formula.

​

Order

​

Order ID

Your order number, from the order_number parameter. Bookings, sign-ups and transactions can send it as booking_id, signup_id or transaction_id instead. We use it to spot the same order arriving twice. Those events get the Duplicates status on the Logs page.

​

Order Total

The order value, from the order_subtotal parameter. order_total and the booking and transaction versions also work. Send it as a plain number, such as 49.99, excluding VAT and shipping. Currency symbols or commas leave the total empty, which shows as an error on order events.

​

Currency

The three-letter ISO 4217 code for the order total, such as GBP, from the order_currency parameter.

​

Page and Campaign

​

Situation

Where on your site the tag fired, from the situation parameter. Common values include postpurchase, landingpage and dashboard. Situations are also used in reporting.

​

Locale

The language and country the campaign is shown in, from the locale parameter. Send it in the form en_GB. If a tag sends en-GB, the log shows it as en_GB.

​

Segment

A label for the customer’s group, such as vip, from the segment parameter.

​

Custom Field

Any extra data you pass, from the custom_field parameter, up to 255 characters. For Shopify webhook orders, it holds the order’s tags.

​

Request

​

Receipt Cookie

An anonymous ID that our tags store in the customer’s browser, in the mm_id cookie, when your cookie settings allow. We use it to:

• Recognise a referee who returns before we know their email, so we can link their order to the referral
• Keep the offers a customer sees consistent between visits
• Spot the same person making several referrals, as part of fraud checks

If the browser blocks cookies, or the customer has not accepted them, it shows a new value on every event. It is empty on events from files and webhooks. See Understanding Cookies and Going Cookieless.

​

Page URL

The page where the tag fired. It comes from the href tag parameter, or from the page the browser reports if href is missing. For Shopify webhook orders, it is your shop’s domain.

​

Where It Came From

​

Source

How the event reached us.

​

If a Field Is Empty or Wrong

Look at the event’s Source, then check what sent it:

• JS tag, SFTP / S3 batch or File upload: the parameter or column named in the field’s entry above
• Consumer, Entry point or Merchant API: the request your system sent, against that API’s docs
• Shopify webhook: the order in your Shopify admin

Then send a test event and look for it on the Logs page.

​

See Also