Overview

The BCC Email integration allows merchants to submit customer information to RaveCapture by blind carbon copying (BCC) a special email address during transactional email sends (e.g., order confirmations). This method is ideal for merchants using a custom CRM, invoicing platform, or non-integrated storefront that lacks direct API support.

This feature supports Company Reviews only and is available on all plans.

How It Works

When a qualifying outbound email is sent to a customer (e.g., post-purchase), you include your RaveCapture BCC email address in the BCC field. RaveCapture parses the email for three specific data fields to create a Company Review Request.

The customer will not see that RaveCapture was BCC’d.

Setup Instructions

Step 1: Locate Your BCC Email Address

Go to Integrations > Company Reviews > BCC Email
Copy your unique RaveCapture BCC email address (e.g., yourstore@direct.ravecapture.com)

Step 2: Authorize Your Sending Email Address

To prevent abuse, only whitelisted sender email addresses can use this feature.

Enter the sending "From" email address that will BCC RaveCapture
Save the changes

Only messages from this address will be accepted and parsed.

Step 3: Add BCC to Outgoing Emails

Add the unique RaveCapture BCC address as a blind copy recipient in your email platform (CRM, invoicing system, etc.). This ensures RaveCapture receives a copy of each outgoing message.

Step 4: Format Required Tags

The body of the BCC email must include these three tagged fields:

TrustSpotDirectEmail 
[name]John Smith[/name] 
[email]john@example.com[/email] 
[order]123456[/order]

Replace the sample values dynamically with your platform's customer data. Tags must be exact and complete.

If any tag is missing or malformed, the message will be ignored.

Limitations and Considerations

Only one customer submission can be included per BCC email
No support for Product Reviews via BCC
No logging or error display if the message is ignored due to formatting
RaveCapture does not enforce rate limits, but requests must conform to the tag structure
There is no need to batch emails or delay send timing