JB Email Send Log

The problem

Your Marketing Cloud Engagement team sends order confirmations, newsletters and offers to the same people your agents talk to. Inside Sales Cloud and Service Cloud, none of that is visible. When a customer calls about “the email you sent me”, the agent cannot see when it went out or what it said. They ask the customer to forward it, or they guess.

The standard Marketing Cloud Connector can bring send data into your org, but only by copying records into Salesforce storage. This consumes your scarce storage space.

What the app does

JB Email Send Log adds a Sent Emails component to any Lightning record page. It lists every email Marketing Cloud sent to that person. The component shows sent date, subject and sender address. Email name, from name and open date are available as extra columns.

An agent can open the content the customer actually received, personalisation included, and resend it. Agents resend a lost order confirmation from the record, without asking the marketing team.

Nothing is copied into your org. The component queries Marketing Cloud when the page loads and shows the result.

How it works

The package contains a Lightning Web Component, an Email Send Log Settings tab and two permission sets: Email Send Log for users and Email Send Log Admin for the people who configure it. The component is a page element you place with Lightning App Builder.

• Any record page. Add the component to Contact, Lead, Person Account, Case, Account or a custom object. In the component properties you set the Subscriber ID Field API Name, the field that holds the Marketing Cloud subscriber key for that record. On a Contact that is usually the record Id. On a Person Account it is PersonContactId. In the component properties you also choose whether the list loads when the page opens or on request.
• Live query, no storage. When an agent opens the record, the component calls Marketing Cloud through a Named Credential. It reads from an indexed copy of the send log in Marketing Cloud (the data extension that records every send). The results are displayed and not saved. Your data storage in Sales Cloud or Service Cloud does not grow.
• Credentials you control. The Marketing Cloud API credentials live in a Named Credential in your org, the standard Salesforce place for API credentials. Your security team can audit, rotate and restrict them with standard Salesforce tooling.
• Your labels, your columns. In the Email Send Log Settings tab you rename the component title and the column headers. You also choose which columns appear and in what order. The Email Send Log Admin permission set controls who may change these settings.

How this compares to the Marketing Cloud Connector

The Marketing Cloud Connector from Salesforce syncs send logs, tracking data and subscriber information into your org as records. Its sync is not granular: it brings over everything in scope, including every open and click event. At any real send volume those records grow quickly, and so does your storage bill. Many admins first notice when a storage warning or an overage invoice arrives.

JB Email Send Log stores nothing. The history stays in Marketing Cloud, where it already is, and is read on demand. If you have low send volumes and plenty of storage headroom, the connector may be all you need. If you send at B2C volumes, the storage cost alone is a reason to look at Email Send Log. So is letting agents see the actual content and resend it.

Get it

JB Email Send Log is not on AppExchange. You install it per org by following a documented custom install process that anyone at home in Salesforce Setup can follow, and we assist during setup. The installation guide covers both the Marketing Cloud and the Salesforce side, and the FAQ and release notes sit next to it. Pricing is on request: send us a request for information and we reply within one business day.