Loading

Data Discrepancies in Account Engagement vs. B2B Marketing Analytics

Udgivelsesdato: Sep 30, 2025
Beskrivelse
If you are using B2B Marketing Analytics (B2BMA) for creating custom lenses and dashboards, you may find discrepancies between Account Engagement and B2B Marketing Analytics data. 
Løsning
These discrepancies may be caused by one of the following reasons:


Timezones

Account Engagement reflects the time zone of its primary users, this is set in account settings during initial implementation.

B2B Marketing Analytics may have differing time zone settings, depending on which datasets are being referenced. For example, all pre-built B2B Marketing Analytics dashboards use Coordinated Universal Time (UTC)–this is an Analytics platform limitation, however timezone support will be available with future releases of the Analytics platform.

Custom dashboards and datasets coming from Salesforce, on the other hand, will use the time zone set in the connected Salesforce org.*

*Note: This refers only to custom dashboards and datasets; Account-Based Marketing and Multi-Touch Attribution, will sync according to Coordinated Universal Time (UTC) just like other out-of-the-box dashboards.
 

Time & Frequency of Updates

There are also some differences in when updates occur in both Account Engagement and B2B Marketing Analytics.

Most Account Engagement data updates in real-time, meaning the numbers will be up to date after loading the page. Reports based on data sources outside of the Account Engagement application will take longer. As an example, a list email report will be updated with a page load in Account Engagement, but the Search Marketing report will update once every 24 hours.

Pre-built B2B Marketing Analytics datasets and dashboards that are pulled from Account Engagement, update once every 24 hours; they cannot be refreshed on demand. However, datasets created from Salesforce data (e.g. datasets used for Account-Based Marketing and Multi-Touch Attribution dashboards) can be manually updated, using the Dataflow Manager.*

*Note: Manual refreshes are subject to the defined Analytics Platform limitations of 40 total dataflow runs in a rolling 24-hour period.

Custom datasets created through Salesforce can be refreshed at any time, either through a manual push or by scheduling refreshes for a specific time and day.
 

Prospect Counts

Account Engagement lists and reports exclude all archived prospects–when a user runs a report or compiles a list, they are automatically seeing only prospects who are currently in their active database.

By default, B2B Marketing Analytics datasets include archived prospects; however, you can use “is_archived” in the dataset formulas to remove archived prospects.
 

Opted Out Prospects

When comparing opted-out prospects, be sure to compare the same marketing assets. For example, List emails on the Engagement Dashboard should be compared with individual list emails within Account Engagement.

Note: Based on the permission set licenses, if you have “Manage Analytics Templated Apps” permission-assigned make sure the permissions ‘Create B2B Marketing Analytics Apps’ and ‘Edit Analytics Dataflows’ permissions are checked under the system permission in permission set. However, If you have “B2B Marketing analytics” Permission set licenses, the above system permissions are already included.

Then check the dataflows after 24 hours to see if they are updating correctly.
 

Email Templates

Email Template reports in Account Engagement will show unique clicks on an email for a given timeframe. For example, if a prospect has multiple clicks and the report is for “All Time”, the prospect would display once. If the date range is on the report and the prospects had their first click during that date range, the prospect will count as a unique click for that time frame. If the filter is set for a different date range and the prospect had a second click during that time, the prospect will count as a unique click for that time frame too.

In contrast, the Email Template dataset in B2BMA will only count a prospect’s first click for an email as a unique click. So continuing with the example above, if the filter in the Engagement dashboard is set to the first date range above (where the prospect had their first click), the prospect would be counted as a unique click during that timeframe. However, if filtered for the second date range (where the prospect had their second click), the dataset would not have a unique click for the prospect during that timeframe.
 
Vidensartikelnummer

000382699

 
Indlæser
Salesforce Help | Article