Skip to content
English
  • There are no suggestions because the search field is empty.

BCC Advanced Options and Fields

Send customer, order, meta data and product information to ResellerRatings through a transactional email. This setup uses an HTML comment inside the email’s source to register review requests with the details you provide.

Why use the advanced setup?

Basic BCC reads information from the email’s recipient and subject. The advanced setup gives you explicit control over the data used to register the request.

Use it to:

  • Collect product-specific feedback. Include purchased SKUs so the request identifies the products involved.
  • Choose the review types you need. Explicitly request brand reviews, product reviews, or both.
  • Provide more complete order information. Send the actual transaction date, order number, customer name, and order total.
  • Keep useful context with the order record. Include custom metadata such as a store number, loyalty tier, or product attribute.
  • Work around missing BCC fields. Send a separate order-triggered notification directly to ResellerRatings.
  • Avoid relying on subject-line formatting. Supply the customer and order information in a structured block.

This approach is useful when your collection workflow needs more detail than a customer email address and order number.

Only need basic BCC collection? Start with Automatically request reviews using BCC.

How it works

Your notification includes a small block of structured data inside an HTML comment. The comment stays out of the email’s normal visual layout, while remaining available in its source.

When ResellerRatings receives the email, it reads that block and uses the supplied information to register the review request.

Important: With this configuration, the customer data comes from the comment block. The email’s To and Subject fields are ignored for that extraction.

Before you begin

You’ll need:

  • Access to your ResellerRatings dashboard.
  • Access to your notification’s HTML or code editor.
  • Your platform’s customer and order variables.
  • A notification workflow that can send to your collection address.
  • A test order and an email address you control.

If someone else manages your email templates, they may need to help map the order variables and check the rendered JSON.

Step 1: Copy your collection address

In ResellerRatings:

  1. Open Collect Surveys → Automatic Collection.
  2. Select the incoming email option.
  3. Find Merchant Incoming Email Address.
  4. Copy the complete address from your account.

Use this address as the destination for your notification.

Step 2: Choose how to deliver the email

There are two options.

Delivery method How to configure it
Customer notification with BCC Add the HTML comment to your customer email and place your collection address in BCC.
Separate notification Send an order-triggered email directly to your collection address and include the HTML comment in that email.

For either method, the email field inside the comment must contain the customer’s email address.

Choose one intended trigger, such as an order, shipping, or delivery notification. Check for other

 

Step 3: Add the HTML comment

Open your notification’s HTML source or code editor.

Insert the comment into the email source, typically inside the <head> section. Do not paste it into a visual editor as customer-facing text.

This example explicitly requests a brand review only:

<!--#rsr.data:{   "email": "customer@example.com",   "invoice": "AB12345-US",   "transaction_date": "2026-11-16",   "cart_total": 40.99,   "brand": true,   "product": false }-->

 

hese are sample values. Before using the template, replace them with your platform’s dynamic customer and order variables.

For example:

  • email should populate with the customer’s email address.
  • invoice should populate with the order or invoice number.
  • transaction_date should populate with the transaction date.
  • cart_total should populate with the numeric order total.

Variable names and syntax differ between platforms. Use your platform’s supported variables rather than copying variable syntax from another system.

Step 4: Add product information when needed

To request product reviews, include the purchased SKUs and set product to true.

This example requests product reviews only:

<!--#rsr.data:{   "email": "customer@example.com",   "invoice": "AB12345-US",   "transaction_date": "2026-11-16",   "sku": ["SKU-001", "SKU-002"],   "product_name": ["Everyday Backpack", "Travel Bottle"],   "first_name": "Alex",   "last_name": "Morgan",   "cart_total": 89.98,   "brand": false,   "product": true }-->

Use the actual identifiers for the purchased products. If you supply product names as an array, keep them in the same order as the SKUs.

Choose which review types to request

Review types brand product
Brand only true false
Product only false true
Brand and product true true

 

Step 5: Include optional customer and order details

The following fields are supported in the structured data block.

Field Required? Format and purpose
email Yes String containing the customer email address that should receive the invitation.
invoice No String containing the order or invoice number.
transaction_date No ATOM or ISO 8601 date, such as "2026-11-16".
sku No Array of purchased SKUs for product review requests.
product_name No Product name or array of product names.
first_name No Customer’s first name.
last_name No Customer’s last name.
cart_total No Numeric order total, such as 89.98, without a currency symbol.
custom_field No Object containing additional merchant metadata.
brand No Boolean controlling the brand review trigger.
product No Boolean controlling the product review trigger.

Although sku is optional in the overall format, include the purchased SKUs when configuring product review requests.

Add custom metadata

Use custom_field to attach additional context to the order record.

The following complete example includes a loyalty tier, store number, and attributes for one SKU:

<!--#rsr.data:{   "email": "customer@example.com",   "invoice": "AB12345-US",   "sku": ["SKU-001"],   "custom_field": {     "loyalty_tier": "gold",     "store_number": "123",     "SKU-001": {       "year": "2026",       "color": "Silver"     }   },   "brand": false,   "product": true }-->

Custom fields support:

  • Flat key/value pairs, such as "loyalty_tier": "gold".
  • SKU-specific metadata, where the top-level key is the SKU and its value is a flat object.

Deeper nesting is not supported.

Step 6: Check the data format

The content inside the comment must be valid JSON.

Follow these rules:

  • Preserve the opening <!--#rsr.data: marker and closing -->.
  • Use double quotation marks around field names and text values.
  • Separate properties with commas.
  • Do not add a trailing comma after the final property.
  • Use square brackets for arrays.
  • Write booleans as true or false, without quotes.
  • Write cart_total as a number, without a currency symbol.
  • Do not include ellipses such as ... inside an array.

Check the finished email, not just the template. Your platform must replace its variables with real values before sending.

Dynamic text also needs proper JSON escaping. For example, quotation marks inside a product name can break the data block if they are not escaped. Use your platform’s JSON serialization or escaping feature where available.