B2B Marketing Analytics Guide | SalesforceTutorial

B2b marketing analytics is the CRM Analytics app used with Salesforce Marketing Cloud Account Engagement to analyze campaign engagement, pipeline, attribution, and revenue influence in one reporting workspace. It helps Salesforce and marketing teams move beyond single-object reports when they need Account Engagement activity and Sales Cloud data in the same dashboard.

This guide explains what B2B Marketing Analytics does, how B2BMA works with Account Engagement, how to plan a B2BMA integration, and how to avoid setup issues that cause empty dashboards or misleading metrics. The article uses the current Salesforce naming: Marketing Cloud Account Engagement is the product formerly known as Pardot, so older searches for pardot analytics usually refer to the same reporting area.

What is B2B Marketing Analytics?

B2B Marketing Analytics is a Salesforce CRM Analytics app for Account Engagement reporting. It packages selected Account Engagement and Sales Cloud data into CRM Analytics datasets, then uses those datasets in lenses and dashboards. Salesforce Help describes it as part of Analytics for Account Engagement, and Salesforce Trailhead explains that it uses the verified Salesforce-Account Engagement connector to consolidate marketing data for analysis.

In enterprise orgs, the main reason to use this app is not that it replaces every Salesforce report. The reason is that marketing engagement data often lives in a different shape from sales pipeline data. A form submission, list email click, landing page view, prospect score change, campaign member status, and opportunity stage change are not all simple rows on one Salesforce object. B2B Marketing Analytics gives admins a reporting layer where those events can be grouped, filtered, and compared without building a custom data warehouse first.

Use the official Salesforce pages when you configure the feature: Analytics for Account Engagement, Set Up B2B Marketing Analytics, and the Trailhead module Get Started with B2B Marketing Analytics for Lightning App.

How B2BMA relates to pardot analytics

B2BMA is a common shorthand for B2B Marketing Analytics. pardot analytics is an older search phrase that many admins still use because Account Engagement was previously branded as Pardot. In current Salesforce documentation, use Account Engagement for the product name and B2B Marketing Analytics for the CRM Analytics app.

The distinction matters in implementation work. Account Engagement reports inside the marketing app can answer operational questions such as email performance or form submissions. Salesforce reports can answer object-level questions such as campaign members by status. B2B Marketing Analytics is the better fit when the question crosses systems, for example: “Which campaign created the most pipeline after prospects engaged with a landing page?”

What data does B2B Marketing Analytics use?

B2B Marketing Analytics uses datasets generated from Account Engagement, Salesforce, or both. Salesforce lists dataset references for campaigns, prospects, visitors, opportunities, form activity, email activity, landing pages, and attribution-related data in the B2B Marketing Analytics dataset reference. The exact fields available in your org depend on edition, feature enablement, connector health, and historical data.

Think of a dataset as a reporting table maintained by CRM Analytics. A dashboard does not query every source object live each time a user opens a chart. Instead, the app prepares data through CRM Analytics dataflows, recipes, or managed processes depending on the template and org configuration. That preparation step is why dashboard numbers can lag behind source records until the next data refresh completes.

Common B2BMA datasets admins inspect first

SAQL example for dataset exploration

Admins usually build lenses with the CRM Analytics UI, but developers and analytics specialists may use SAQL when they need a controlled query. Replace Account_Engagement_Activity with the dataset API name from your org. Field names also vary by dataset and template version, so verify them in Data Manager before running the query.

q = load "Account_Engagement_Activity";
q = filter q by 'CampaignName' is not null;
q = filter q by date('ActivityDate_Year', 'ActivityDate_Month', 'ActivityDate_Day')
    in ["current year".."current year"];
q = group q by 'CampaignName';
q = foreach q generate
    'CampaignName' as 'CampaignName',
    count() as 'EngagementCount';
q = order q by 'EngagementCount' desc;
q = limit q 25;

This query is not a replacement for governed dashboard design. It is a diagnostic pattern: confirm that the dataset contains the expected campaign values, activity dates, and event counts before you spend time editing a dashboard. Salesforce provides SAQL and CRM Analytics developer documentation for teams that manage analytics assets through code or API.

B2B Marketing Analytics implementation guide

A practical b2b marketing analytics implementation guide starts before anyone clicks the setup button. The app can create dashboards quickly, but the dashboards only become useful when the connector, campaign structure, permission model, and source data are ready.

B2b marketing analytics implementation guide prerequisites

1. Confirm licensing. In Salesforce Setup, check Company Information and Permission Set Licenses. Do not assume a sandbox has the same license allocation as production.
2. Verify the Salesforce-Account Engagement connector. B2BMA depends on the connector between Salesforce and Account Engagement. Trailhead specifically calls out connector verification as part of setup.
3. Review Connected Campaigns. Connected Campaigns map Account Engagement campaign activity to Salesforce campaigns. Poor campaign mapping creates reporting gaps.
4. Review Campaign Influence. If leadership expects pipeline or revenue attribution, confirm the active campaign influence model and the business rule behind it.
5. Assign the right permission set licenses and permission sets. Users need access to CRM Analytics and to the B2B Marketing Analytics app assets. The integration or connector user also needs access required by the setup assistant.
6. Check field-level security and sharing. CRM Analytics can only prepare and expose useful data when the running user and integration context can read the needed fields and records.
7. Plan refresh windows. Dashboard users should know when data updates. Do not schedule executive reviews during the first refresh after a large sync change.

B2bma integration setup path

A standard b2bma integration setup follows this sequence. The menu names can shift by release, but the core path remains the same: prepare Account Engagement, enable CRM Analytics, create or update the app, validate datasets, and publish dashboards to the right audience.

1. Open Salesforce Setup and switch to the Marketing Setup area when required.
2. Search for B2B Marketing Analytics or Analytics for Account Engagement.
3. Use the setup assistant to review prerequisites and manage assignments.
4. Enable CRM Analytics if it is not already enabled in the org.
5. Create the B2B Marketing Analytics app from the available template.
6. Wait for the initial data preparation to complete.
7. Open Analytics Studio, inspect the generated app, and confirm that datasets contain current rows.
8. Validate dashboard totals against known Account Engagement assets and Salesforce campaign records.
9. Clone dashboards before editing managed templates for department-specific reporting.

In production implementations, validate one business question at a time. For example, start with “How many prospects converted from paid webinar campaigns in Q2?” and trace that number from Account Engagement activity to Salesforce Campaigns to the B2BMA dashboard. This is slower than scanning every dashboard, but it catches connector and influence problems before executives rely on the reports.

What permissions are required for B2BMA?

Permissions are a common source of setup delays. A user may be able to open Salesforce reports but still fail to open Analytics Studio. Another user may see Analytics Studio but not the B2B Marketing Analytics app. A connector or integration user may run the data preparation but miss fields needed for joined datasets.

Use least privilege, but do not under-provision the integration context. Assign CRM Analytics permissions, B2B Marketing Analytics permissions, and Account Engagement access based on the official setup assistant. Then test with three users: the admin who builds the app, a marketing manager who consumes dashboards, and a sales leader who views pipeline summaries.

Which B2B Marketing Analytics dashboards should you use first?

Salesforce documents B2B Marketing Analytics dashboards for engagement, pipeline, account-based marketing, and attribution use cases. Start with the dashboard that matches the business decision, not the one with the most charts.

Pipeline dashboard

Use the pipeline view when marketing and sales want one discussion about funnel movement. This dashboard area is useful for visitor-to-prospect movement, marketing-qualified leads, open opportunities, closed-won opportunities, and velocity. Validate opportunity stage definitions before comparing business units. If one region updates opportunity stages weekly and another does it at month-end, pipeline charts will reflect process behavior as much as campaign performance.

Engagement dashboard

Use engagement reporting to inspect list emails, forms, landing pages, and other marketing assets. This is where pardot analytics users often begin because the metrics look familiar: sends, opens, clicks, submissions, bounces, and opt-outs. The difference is that B2B Marketing Analytics can place that activity beside Salesforce campaign and opportunity context.

Marketing manager dashboard

Use the marketing manager view for a summary across campaign performance and pipeline. In enterprise orgs, clone this dashboard before making changes for each region or product line. Keep the source template intact so admins can compare custom dashboards with the Salesforce-managed version after releases.

Account-based marketing dashboard

Use account-based marketing reporting when the buying group matters more than the single lead. This is common in long sales cycles where several contacts from the same account engage with assets before an opportunity advances. The dashboard is only as reliable as account matching, contact roles, and campaign association quality.

Multi-touch attribution dashboard

Use attribution reporting when stakeholders understand the attribution model. First-touch, last-touch, and even distribution answer different questions. Do not present one model as the truth. Present the model, the business assumption behind it, and the decision it supports.

What is B2B Marketing Analytics Plus?

B2B Marketing Analytics Plus adds advanced analytics capabilities for teams that need more than descriptive dashboards. Salesforce Help states that B2B Marketing Analytics Plus availability depends on Salesforce edition, Account Engagement edition, or the relevant add-on. Some Einstein for Account Engagement capabilities also depend on prerequisites such as the verified connector, Connected Campaigns, Customizable Campaign Influence, and enough historical data.

Do not position Plus as a default upgrade for every org. First define the reporting problem. If the team needs cleaner campaign ROI reporting, fix campaign hierarchy, influence settings, and data quality before buying more features. If the team needs predictive scoring, account identification, or deeper attribution, evaluate Plus and Einstein prerequisites with Salesforce documentation and your account team.

Security and data governance for B2B Marketing Analytics

B2B Marketing Analytics sits at the intersection of marketing behavior, personal data, and sales pipeline. Treat it as governed business data. Marketing users may need campaign engagement detail, but they may not need every opportunity amount, sales note, or account segmentation field.

Field access and dataset exposure

Review field-level security for sensitive fields before adding them to custom datasets. In Apex and SOQL, developers think about CRUD and FLS enforcement at query time. In CRM Analytics, the risk appears when a dataset or dashboard exposes fields to users who should not see them. Use CRM Analytics security settings, app sharing, and dataset permissions deliberately.

Data retention and time zone considerations

Salesforce Help lists considerations for B2B Marketing Analytics, including differences that can affect reporting interpretation, such as currency and engagement data behavior. For date comparisons, document which time zone the business expects in dashboards. A campaign sent near midnight can appear in different reporting periods if source systems and users interpret dates differently.

Release and API version awareness

CRM Analytics REST API examples use Salesforce REST endpoints such as /services/data/vXX.X/wave/. Use the latest API version supported by your org and integration policy. Salesforce release notes show Winter ’26 as API version 65.0 and Spring ’26 as API version 66.0; Summer ’26 orgs expose later versioned resources depending on rollout and feature area. Avoid hardcoding old versions in new integrations.

# Example: list CRM Analytics dashboards through REST.
# Replace v66.0 with the current API version approved for your org.
curl --request GET \
  --url "https://your-domain.my.salesforce.com/services/data/v66.0/wave/dashboards" \
  --header "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  --header "Content-Type: application/json"

Use OAuth through a connected app for production integrations. Do not place access tokens in source control, build logs, or analytics recipes. If you automate dashboard inventory or dataset checks, run the integration through a named integration user and review its permissions at least once per release cycle.

How to customize B2BMA dashboards safely

Most teams eventually customize the app because the standard dashboards cannot know your campaign taxonomy, product lines, regions, or revenue model. Customization is expected, but unmanaged changes can make release upgrades and support difficult.

1. Clone first. Keep the original app and dashboards available for comparison.
2. Name assets by purpose. Use names such as EMEA Webinar Pipeline Dashboard, not Dashboard v3 final.
3. Document filters. A region filter, fiscal period filter, or campaign type filter changes the meaning of every metric.
4. Use a dashboard owner group. Avoid dashboards owned by a user who may leave the company.
5. Validate after each release. Salesforce releases can update templates and feature behavior. Compare custom assets against official documentation and a sandbox refresh.

Custom dataset checklist

Before adding Salesforce objects to a custom dataset, answer these questions:

• Which Salesforce object is the source of truth?
• Does the integration user have read access to the object and required fields?
• What join key connects the data to Account Engagement or campaign records?
• Can the join key be null, duplicated, or overwritten?
• How often must the dataset refresh?
• Who approves new fields that expose revenue, region, or personal data?

A common pattern is to add product, region, channel, or account segment fields so marketing dashboards can answer budget questions. Add only the fields needed for the decision. Large datasets with unused fields slow implementation reviews and increase governance risk.

Common errors with B2B Marketing Analytics

Most B2B Marketing Analytics issues fall into four groups: missing permissions, connector problems, data model assumptions, and dashboard interpretation errors.

Dashboards show no data

Check the data preparation job status first. If the app was just created, the first run may not have completed. Next, check connector verification, permission assignments, and whether the source Account Engagement assets have data in the selected date range. If the dashboard has filters, clear them and test again.

Pipeline numbers do not match Salesforce reports

Confirm that both reports use the same date field, opportunity stage filter, campaign influence model, currency handling, and fiscal calendar. A Salesforce report grouped by Close Date will not necessarily match an analytics dashboard grouped by campaign touch date or attribution date.

B2bma integration joins are empty

Empty joins usually mean that the left and right datasets do not share matching keys. Inspect the join fields in CRM Analytics Data Manager. Check for blank Campaign IDs, prospects that are not syncing to leads or contacts, disabled Connected Campaigns, or opportunity records without the expected contact roles.

Users can see the app but not the dashboard

Check app sharing, dashboard sharing, dataset access, permission set assignments, and permission set licenses. CRM Analytics access is layered, so opening Analytics Studio does not guarantee access to every app asset.

Best practices for B2B Marketing Analytics in production

• Start with one decision. Define the dashboard question before editing widgets.
• Keep a metric dictionary. Define MQL, influenced pipeline, campaign ROI, and engagement so marketing and sales use the same language.
• Validate with source records. Pick five campaigns and trace numbers from Account Engagement to Salesforce to B2BMA.
• Separate operational and executive dashboards. Marketers need diagnostic detail; executives need stable definitions and fewer filters.
• Review data after connector changes. Connector updates, field mapping changes, and campaign hierarchy changes can affect dashboards.
• Use sandbox testing for template changes. Do not rebuild production dashboards directly during a release window.
• Document ownership. Assign a business owner for each dashboard, not just a Salesforce admin owner.

Related SalesforceTutorial resources

Use these related guides when your B2B Marketing Analytics work touches adjacent Salesforce areas: Salesforce Pardot and Account Engagement setup, CRM Analytics in Salesforce, Salesforce reports and dashboards, Salesforce Data Cloud architecture, and Salesforce Campaign Influence setup.

Frequently Asked Questions