A Domo marketing dashboard is what people look for when they want marketing figures inside a business intelligence tool, next to finance and operations data. That is a reasonable goal for a company with data spread across many systems. This article answers the question a firm of 10 to 250 people should ask first: does the marketing view need a separate BI layer, or should it be built in the CRM where the contacts and revenue already sit, with BI added only if the business genuinely needs it.
What a BI tool is for
Business intelligence tools pull data from many systems into one model so analysts can join it, slice it and present it. They suit businesses whose questions cross several systems: margin by client joined to marketing source, staff utilisation joined to pipeline, stock levels joined to campaigns.
Marketing on its own rarely needs that. The core marketing questions, where leads come from, which ones book calls, which ones become clients, what it cost, can all be answered from a CRM that records source, stage and value. Adding a BI layer for those questions adds a step without adding an answer.
What to check before choosing a BI route
- Which questions cross systems the CRM cannot see?
- Who in the business can build and maintain a data model?
- How fresh does the data need to be when it reaches the BI tool?
- Will the people who need marketing figures log into the BI tool weekly?
If you cannot name a question that crosses systems and a person to maintain the model, start in the CRM.
Before you start
- Source recorded on every new contact through forms, calendars and integrations.
- A sales pipeline with values and won dates.
- Spend data from connected ad accounts or entered monthly.
- A list of three to five questions the dashboard must answer.
How to set it up
- Write the three to five marketing questions leadership asks most.
- Check which questions the CRM data alone can answer.
- Go to Dashboard, click + Add Dashboard and name it for those questions.
- Add Contacts by Source and the Lead Source Report from General.
- Add Amount Spent from Meta Ads and Total cost from Google Ads.
- Mark any question that needs data from outside the CRM.
- Export contacts and opportunities on a fixed rhythm for the BI tool.
- Keep the CRM dashboard as the reference view for marketing.
- Revisit the list of cross-system questions every six months.
What this replaces
For most firms, the CRM dashboard replaces the plan to buy a BI tool for marketing alone. It also replaces the lag that comes from waiting for a data refresh, because CRM reporting reads live data.
When a BI tool is already in place for finance, the CRM still replaces the marketing data model inside it. Send the BI tool a clean export of contacts, sources and opportunities, and let it handle the cross-system joins it is good at.
Suppose finance already runs a BI tool for margin reporting, and marketing wants to know which lead sources produce the most profitable clients. The CRM can answer lead source, booked calls and won value; margin lives in finance. One workable approach is a weekly export of won opportunities with their source and client reference, joined to margin inside the BI tool. Day-to-day marketing reporting would stay in the CRM dashboard, which the marketing team checks weekly.
Time it takes
A CRM marketing dashboard takes half a day to a day. A scheduled export to a BI tool takes another hour or two once the BI side is ready. Building a marketing data model in a BI tool from scratch can take weeks of analyst time, which is why it should be reserved for questions that need it.
The mistake most people make
Rebuilding the CRM's own reports inside the BI tool. The result is two versions of lead and pipeline numbers that drift apart, and the meeting spends its time reconciling them. Keep one source of truth for marketing figures and feed the BI tool only what it needs for cross-system questions.
When BI is the right call
A BI layer makes sense when marketing questions genuinely depend on other systems: margin, utilisation, product usage or stock. It also makes sense when a parent company or investor requires reporting in a specific tool. In those cases, design the export from the CRM carefully so source and stage definitions travel with the data.
The marketing data dashboard covers the data hygiene that both routes depend on. For diagnostic analysis inside the CRM, see the marketing analytics dashboard. For a comparison with another enterprise tool category, read the guide to marketing data aggregation tools.
Troubleshooting
CRM and BI figures differ. The BI tool is using a different date field or an older export. Agree which date each figure uses and align the export schedule.
Source values arrive inconsistent in the export. UTM spellings vary. Standardise source values in the CRM before exporting.
The export misses recently won deals. The export runs before the sales team updates stages. Move it to after the weekly pipeline review.
Nobody uses the BI dashboard for marketing. That usually confirms the CRM view is enough. Retire the duplicate.
Frequently asked questions
Can the platform send data to a BI tool automatically?
You can export contacts and opportunities, and workflows can send data to other systems through webhooks. Choose the method your BI tool accepts.
Is CRM reporting detailed enough for a marketing director?
For lead, pipeline, revenue and spend questions, yes. For questions involving margin or delivery cost, you need data from elsewhere.
Should spend live in the CRM or in finance?
Both, ideally. Connect ad accounts to the CRM so marketing sees spend weekly, and let finance hold the full cost picture.
What if leadership insists on a single BI view?
Feed the BI tool from the CRM and keep the definitions identical. One source of truth matters more than one screen.