JB Email Send Log questions and answers

No. JB Email Send Log is installed per org through a documented custom install process, not from an AppExchange listing. The setup is standard Salesforce configuration: Named Credentials, permission sets and a Lightning App Builder component. Read the installation guide to see what is involved before you decide.

We quote JB Email Send Log pricing on request. Tell us about your org and what you need on the request information page, and we reply within one business day.

No. JB Email Send Log stores nothing in Sales Cloud or Service Cloud. The email history stays in Marketing Cloud Engagement, and the component queries it on demand from an indexed copy of the Send Log. Your send volume therefore adds nothing to your Salesforce data storage.

The standard Marketing Cloud Connector syncs send logs, tracking data and subscriber records into your Salesforce org, and every synced record uses storage. JB Email Send Log stores nothing in your org and reads the Send Log from Marketing Cloud Engagement on demand. It shows sends, opens and clicks in one view, links to the personalised content the customer received, and lets agents resend an email. Credentials live in Salesforce Named Credentials, not inside a managed package, so your security team can audit and rotate them with standard tooling.

Since v1.45 (18 December 2025) you can add the JB Email Send Log component to any Lightning record page in Lightning App Builder. Contact, Person Account, Case and Account all work, where earlier versions only supported the standard Contact record page. If the record ID is not the Marketing Cloud subscriber key, set the Subscriber ID Field API Name property to the field that holds it. See Person Accounts for the most common case.

JB Email Send Log uses Salesforce Named Credentials, the standard place to store API credentials in Salesforce. During setup you create one External Credential that holds the Marketing Cloud Engagement client ID and client secret. You also create two Named Credentials, one for the Marketing Cloud token endpoint and one for the content endpoint. A permission set gives users access to the credential, and the installation guide lists the exact labels, API names and callout options.

Every user who views the component needs two permission sets: Email Send Log, which is part of the app, and External Credential Access. You create External Credential Access during setup so the user can call Marketing Cloud Engagement. Only the people who configure the app also need Email Send Log Admin, added in v1.49, which opens the Email Send Log Settings tab. The installation guide walks through creating and assigning each one.

Yes, from v1.45 onwards. Marketing Cloud Engagement usually identifies a subscriber by Contact ID, which on a Person Account sits in PersonContactId, not the record ID. Add the component to the Person Account record page in Lightning App Builder and set Subscriber ID Field API Name to PersonContactId. You can point the component at any standard or custom field the same way, for example External_ID__c, using its exact, case-sensitive API name.

Yes. An agent can resend an email, such as an order confirmation, directly from Service Cloud. They do not need to open Marketing Cloud Engagement.

Yes, since v1.49 (23 March 2026). A user with the Email Send Log Admin permission set opens the Email Send Log Settings tab from the App Launcher. There you choose which columns show, set their order, and rename the component title and every column header. The same release added Email Name, From Name and Open Date as selectable columns, and the installation guide has the exact clicks.

Yes. In Lightning App Builder, select the component and untick the loadOnRecordLoad property, which is on by default. Users then click a button to load the emails, which you may prefer for performance. The installation guide shows where the property sits.

Check two things. First, upgrade to v1.45 (18 December 2025) or later, because earlier versions only worked on the standard Contact record page. Second, in Lightning App Builder set the component’s Subscriber ID Field API Name to PersonContactId, which holds the Contact ID on a Person Account. The Person Accounts answer explains why, and the installation guide shows the property.