When you create a custom B2B Marketing Analytics dashboard or lens and the output is much lower than expected, it's sometimes due to differences in how the app organizes raw data vs. dashboard data. When configured incorrectly, customizations can show statistics from a single day instead of many.
In the raw data, one row represents an email's engagement statistics for a single day. However, in the default dashboard, the data is shown grouped by the email name.
For example, the default Engagement dashboard includes a List Email Engagement section that uses the Email Viz Data component. This component is built on the Account Engagement Email Dataset, which includes the Stats Date field. The SAQL for this component includes:
q = group q by email_name
Note: This grouping difference appears in any Account Engagement dataset that uses the Stats Date field to organize data, such as Landing Pages and Visitors datasets.
In a B2B Marketing Analytics dashboard, to make sure your data appears as expected, you can use the Query Builder to build your custom dashboard or lens off the Account Engagement Emails dataset. Under Bars, group by the field Name (email_name) or Email ID (email_id).
Or
Open Query Mode, and edit the SAQL to include q = group q by email_name.
In this example, foreach does a sum of the desired metric. By using group q by email_name and the sum('metric'), you aggregate the metrics in your custom lens or dashboard by each asset.
q = load "pdEmail";
q = group q by email_name;
q = foreach q generate sum('delivered') as 'delivered', sum('unique_html_opens') as 'unique_html_opens', 'email_name' as 'email_name';
q = limit q 100;
More information: Queries and Custom Queries, Create a Query with the Explorer
Note: Account Engagement Support will not assist with building and/or modifying queries used in custom dashboards.
000389423

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.