ServicesSalesforce consultingArchitectureImplementationOrg health checkDevelopmentIntegrations and APIsData migrationTesting and QAManaged supportSpecialist supportMarketing Cloud auditDeliverability
SolutionsMarketing Cloud EngagementMarketing Cloud NextSalesforce + BrazeAccount EngagementData Cloud (Data 360)Identity resolutionInsights and segmentsAgentforce and AIMCP integrationsSales and Service CloudReal-time personalisationIntegration solutionsEnterprise AI integrationBy industry
ArchitectureSalesforce CRMData 360Salesforce + BrazeAgentforceCustomer 360API-led integrationEvent-drivenMCP host, client and serverIdentity and consentMCP securityData governanceCI/CD and releasesOur public MCP server
ResourcesEngineering journalDecision guidesSolution blueprintsSalesforce productsProjects and achievementsSales ROI calculatorWhere we workChecklists and templatesPlanning toolsReadiness assessmentGlossaryAbout GeekMidstOur approachOur expertiseContact
CompanyAbout GeekMidstOur approachDelivery methodologyTrust and evidenceProjectsAchievementsBook a consultationContactWhere we workSecurity and data
Book a Consultation

Marketing Analytics and Reporting

Reporting that answers real questions. We define KPIs, build reliable engagement datasets from Marketing Cloud and CRM, and set up measurement you can defend.

Analyst lays three printed charts on a tall table on a rooftop terrace and turns a fourth one face down

Most marketing teams have plenty of numbers and little agreement on what they mean. Opens are inflated by mail client privacy features, click rates are calculated three different ways, and revenue attribution depends on which spreadsheet you open. Reporting becomes a monthly argument instead of a tool for deciding what to do next.

GeekMidst helps teams using Marketing Cloud Engagement, Account Engagement and Salesforce CRM build reporting that is consistent, explainable and tied to decisions. We define the measures, build the datasets behind them and set up dashboards in the tools you already have.

Who this is for

  • Marketing leaders who need a clear view of programme performance and what is actually driving pipeline or revenue.
  • Marketing operations teams spending too much time exporting tracking data and rebuilding the same reports by hand.
  • Analysts and data teams who need clean, well-documented engagement data from Marketing Cloud for their own models.

Workflow diagram

Explore how the pieces fit together. Select a step to read what happens there.

Customer journey

Campaign performance monitoring

Open full size
Campaign performance monitoringSends and journeys produce tracking data, which a daily SQL activity copies from data views into reporting data extensions. Dashboards refresh from those tables, the team reviews results against targets, and anything off target is adjusted and fed into the next sends.Campaign performance monitoringMarketing CloudAutomationStudioReportingMarketing teamYesNoNext sendsCampaigns run: Email, SMS, push. Every send and journey step produces tracking. Consistent naming of journeys, emails and campaigns makes the later reporting far easier.Campaigns runEmail, SMS, pushTracking data: Sends, clicks, bounces, unsubs. Marketing Cloud records sends, opens, clicks, bounces, unsubscribes and complaints by job and subscriber. Opens are inflated by mail privacy features.Tracking dataSends, clicks,bounces, unsubsData view queries: Daily SQL activity. A daily SQL query reads system data views such as _Sent, _Click and _Bounce and appends the new rows to reporting tables.Data view queriesDaily SQL activityReporting DEs: Long-term history. Data views hold only a limited history, so daily archiving keeps long-term trends. A date key with append mode avoids duplicate rows.Reporting DEsLong-term historyDashboards: Reports or BI tool. Reports or a BI tool read the reporting tables and show the agreed measures by campaign, journey and segment, with the same definitions every week.DashboardsReports or BI toolWithin targets?. The team reviews results against targets set before launch. Watching bounce, complaint and unsubscribe rates next to clicks and revenue catches problems early.Within targets?Keep the plan: Until next review. Results are on track, so the campaign continues unchanged until the next scheduled review.Keep the planUntil next reviewAdjust and test: Content, audience or timing. The team changes one thing at a time, such as subject line, segment or send time, ideally as a test, and records what changed and why.Adjust and testContent, audience ortimingStartDataProcess stepSystem or platformDecisionEnd or outcomePerson or teamOriginal GeekMidst explanatory diagram, not an official Salesforce reference.

Select any step in the diagram, or use Step through, to see what happens at that point and why.

Text version: every step in order
  1. Campaigns run Marketing CloudEmail, SMS, push

    Every send and journey step produces tracking. Consistent naming of journeys, emails and campaigns makes the later reporting far easier.

    Next: Tracking data

  2. Tracking data Marketing CloudSends, clicks, bounces, unsubs

    Marketing Cloud records sends, opens, clicks, bounces, unsubscribes and complaints by job and subscriber. Opens are inflated by mail privacy features.

    Next: Data view queries

  3. Data view queries Automation StudioDaily SQL activity

    A daily SQL query reads system data views such as _Sent, _Click and _Bounce and appends the new rows to reporting tables.

    Next: Reporting DEs

  4. Reporting DEs Automation StudioLong-term history

    Data views hold only a limited history, so daily archiving keeps long-term trends. A date key with append mode avoids duplicate rows.

    Next: Dashboards

  5. Dashboards ReportingReports or BI tool

    Reports or a BI tool read the reporting tables and show the agreed measures by campaign, journey and segment, with the same definitions every week.

    Next: Within targets?

  6. Within targets? Reporting

    The team reviews results against targets set before launch. Watching bounce, complaint and unsubscribe rates next to clicks and revenue catches problems early.

    Next: Yes: Keep the plan; No: Adjust and test

  7. Adjust and test Marketing teamContent, audience or timing

    The team changes one thing at a time, such as subject line, segment or send time, ideally as a test, and records what changed and why.

    Next: Next sends: Campaigns run

  8. Keep the plan ReportingUntil next review

    Results are on track, so the campaign continues unchanged until the next scheduled review.

    End of the flow.

Sends and journeys produce tracking data, which a daily SQL activity copies from data views into reporting data extensions. Dashboards refresh from those tables, the team reviews results against targets, and anything off target is adjusted and fed into the next sends. Original GeekMidst explanatory diagram; not an official Salesforce reference architecture.

Questions we help you answer

QuestionTypical measuresUsual data source
Are our emails reaching people?Delivery, bounce and complaint rates by domainMarketing Cloud data views and tracking
Which programmes engage?Unique clicks, click-to-send rate, unsubscribes per sendData views joined to journey and send metadata
Are journeys working as designed?Entry, exit and goal counts per pathJourney and send data, plus journey analytics
Does marketing influence pipeline?Campaign influence and conversion by stageCRM campaigns and opportunities
What would have happened anyway?Lift against a holdout groupControlled test design plus outcome data
Marketing team reviewing a performance dashboard on a wall screen in a meeting

What we do

Example: a 30-day send performance dataset

The query below runs as a Query Activity in Automation Studio and writes to an assumed target data extension Email_Performance_30d_DE with JobID as primary key. It aggregates each data view in a subquery before joining, which avoids the row multiplication you get from joining raw event tables. Data views keep only a limited history, so check the current retention period in Salesforce Help and schedule the query accordingly. Treat it as a starting point, not production code.

sql
SELECT
  j.JobID,
  j.EmailName,
  s.Sends,
  ISNULL(c.UniqueClickers, 0) AS UniqueClickers,
  ISNULL(u.Unsubscribes, 0) AS Unsubscribes
FROM _Job j
INNER JOIN (
  SELECT JobID, COUNT(*) AS Sends
  FROM _Sent
  WHERE EventDate >= DATEADD(day, -30, GETDATE())
  GROUP BY JobID
) s ON s.JobID = j.JobID
LEFT JOIN (
  SELECT JobID, COUNT(DISTINCT SubscriberKey) AS UniqueClickers
  FROM _Click
  WHERE EventDate >= DATEADD(day, -30, GETDATE())
  GROUP BY JobID
) c ON c.JobID = j.JobID
LEFT JOIN (
  SELECT JobID, COUNT(DISTINCT SubscriberKey) AS Unsubscribes
  FROM _Unsubscribe
  WHERE EventDate >= DATEADD(day, -30, GETDATE())
  GROUP BY JobID
) u ON u.JobID = j.JobID
Sample Query Activity: sends, unique clickers and unsubscribes per job

How an engagement runs

  1. 01

    Agree the questions

    Start with the decisions reporting should support, then pick the few measures that inform them. Vanity metrics are dropped early.

  2. 02

    Audit current reporting

    Review existing reports, tracking settings, campaign structures and the data available, and note where numbers disagree and why.

  3. 03

    Build the data layer

    Create the queries, data extensions, CRM fields and campaign structures needed, with retention and refresh schedules documented.

  4. 04

    Build dashboards

    Produce dashboards for each audience, from executive summaries to operational views for the marketing operations team.

  5. 05

    Reconcile and hand over

    Check figures against source systems, document definitions and walk your team through maintaining and extending the reports.

Dependencies and honest limits

Good reporting relies on consistent naming, correct campaign associations and tracking that is switched on and tested. Where those are missing we will say so and fix them first. Some things cannot be measured precisely: open data is unreliable for many recipients, and multi-touch attribution models are assumptions, not facts. For questions about incremental impact, a holdout group usually tells you more than any attribution model. If your deliverability numbers look wrong, our email deliverability consulting is often the better first step.

Questions we hear

Should we still report open rates?
Treat opens as a rough directional signal at best, because privacy features in some mail clients register opens that never happened. Clicks, conversions and unsubscribes are more dependable.
Do we need a separate BI tool?
Not always. Salesforce reports and dashboards cover many needs. A BI tool or CRM Analytics makes sense when you need to combine several sources or keep long history.
How do we keep tracking history beyond data view retention?
Copy the data you need into your own data extensions or an external store on a schedule, before it ages out of the data views.
Can you build attribution for us?
We can set up campaign influence and attribution reporting, and we will be clear about its assumptions. For causal questions we recommend holdout tests alongside it.

Want reporting your team agrees on?

Tell us what you report today and which decisions it should support, and we will suggest where to start.

Talk to a Salesforce expert →

Next step: Marketing Analytics and Reporting

  1. We read it A practitioner reads your message and replies by email.
  2. Short call We confirm goals, constraints and what success looks like.
  3. Written scope You get a scope and estimate before any work starts.

Tell us what you are trying to fix.

Share your Salesforce setup, goals and constraints. A practitioner reads every message and replies with questions, first thoughts or an honest view of whether you need outside help at all.

Talk to a Salesforce Expert
Book a Consultation