Salesforce Analytics: A Complete Guide for Marketing Data Analysts in 2026

Salesforce holds 20.7% of the global CRM market, making it the de facto system of record for sales and customer data at thousands of companies. Yet most marketing teams struggle to extract meaningful analytics from the platform — not because Salesforce lacks reporting tools, but because marketing data lives everywhere except inside Salesforce.

The challenge is structural. Your campaigns run on Meta, Google Ads, LinkedIn, TikTok. Your engagement data sits in HubSpot, Marketo, SendGrid. Your revenue attribution requires stitching together ad spend, CRM deals, product usage, and support tickets. Salesforce was built for sales pipeline visibility, not for answering "which campaign drove this cohort?" or "what's our CAC by channel by region?"

This guide walks you through exactly how marketing data analysts build analytics workflows on top of Salesforce — the tools you need, the data pipelines that make it possible, and the specific steps to turn Salesforce from a sales CRM into a marketing intelligence platform. You'll learn how to connect external marketing data sources, build attribution models, automate reporting, and avoid the common mistakes that waste weeks of engineering time.

Key Takeaways

✓ Salesforce CRM Analytics (formerly Einstein Analytics) offers built-in dashboards for sales data, but marketing teams need external connectors to unify ad platforms, web analytics, and engagement tools with CRM records.

✓ Marketing attribution in Salesforce requires custom field mapping, lead source tracking, and multi-touch models — none of which work out-of-the-box without data transformation and pipeline orchestration.

✓ Most teams hit a wall when trying to join Google Ads spend data with Salesforce Opportunities — the granularity mismatch (campaign vs. individual lead) requires a staging layer and aggregation logic.

✓ Pricing for Salesforce analytics features varies wildly: B2B Marketing Analytics capabilities are often bundled into Growth or Advanced editions at approximately $1,250–$9,000 per organization per month, while core CRM starts at $25/user/month.

✓ Common integration approaches include Salesforce native connectors (limited to a handful of platforms), third-party iPaaS tools (require ongoing maintenance), or reverse-ETL platforms that centralize transformation logic before pushing data into Salesforce.

✓ Real-world implementations take weeks to months when built manually — the bottleneck is always schema mapping, historical data backfill, and maintaining pipelines as APIs change.

What Is Salesforce Analytics and Why It Matters for Marketing Teams

Salesforce Analytics is an umbrella term covering several products: CRM Analytics (the rebranded Einstein Analytics platform for building dashboards and predictive models), Reports and Dashboards (the classic reporting interface inside Sales Cloud), and Marketing Cloud Intelligence (formerly Datorama, designed specifically for media and campaign analytics). For marketing data analysts, the distinction matters because each product solves a different problem.

CRM Analytics works best when your data already lives inside Salesforce — Accounts, Contacts, Opportunities, custom objects. It provides a drag-and-drop interface for building visualizations, pre-built dashboards for sales KPIs, and SAQL (Salesforce Analytics Query Language) for advanced users. But it doesn't natively pull data from Facebook Ads, Google Analytics, or your email service provider. You need to get that data into Salesforce first.

This is why most marketing teams end up building a hybrid stack: external data sources → transformation layer → Salesforce CRM → analytics layer (CRM Analytics, Tableau, Looker, or Power BI). The transformation layer is where the real work happens — normalizing campaign IDs, mapping UTM parameters to Salesforce Campaigns, attributing revenue to touchpoints, and ensuring data refreshes reliably.

Why this matters: 75% of marketers report using AI in their workflows as of 2026, but AI models are only as good as the data they train on. If your Salesforce instance contains sales data but not marketing performance data, you're building attribution models on half the picture. The cost is compounding — bad attribution leads to budget misallocation, which leads to wasted spend, which leads to missed revenue targets.

Step 1: Audit Your Marketing Data Sources and Define What Belongs in Salesforce

Before connecting anything, map every system that holds marketing data. Most B2B marketing teams work with 8–15 platforms:

• Advertising platforms (Google Ads, Meta, LinkedIn, TikTok, programmatic DSPs)

• Marketing automation (HubSpot, Marketo, Pardot)

• Web analytics (Google Analytics, Adobe Analytics, Mixpanel, Amplitude)

• Email and engagement (SendGrid, Iterable, Braze)

• Attribution and BI tools (custom data warehouses, Looker, Tableau)

• Event tracking (Segment, Rudderstack, mParticle)

• Call tracking and conversational analytics (Gong, CallRail)

• Product analytics (Pendo, Heap, PostHog)

Not all of this data needs to live inside Salesforce. The CRM is optimized for object-level records — Leads, Contacts, Accounts, Opportunities — not for storing time-series event logs or raw clickstream data. Your goal is to push aggregated, attribution-ready data into Salesforce fields and Campaign Members, then keep the granular logs in a data warehouse for deeper analysis.

What to Sync into Salesforce

• Campaign performance metrics (impressions, clicks, spend, conversions) aggregated to the Campaign object

• Lead source and UTM parameters stored on Lead and Contact records

• Multi-touch attribution weights written to Campaign Influence custom objects

• Engagement scores and lifecycle stage data from marketing automation

• Product usage signals for product-led growth motions (free trial activity, feature adoption)

What to Keep in Your Data Warehouse

• Raw event logs (page views, button clicks, session replays)

• Hourly or minute-level ad performance data (too granular for CRM storage limits)

• Historical creative-level data (ad copy, image URLs, A/B test variants)

• Call transcripts, email body content, and unstructured data

The decision tree: if a downstream team (sales, customer success, account management) needs to act on the data inside Salesforce, sync it. If it's only used for retrospective analysis or training ML models, keep it in your warehouse and query it from BI tools.

Document this in a shared schema map. For each data source, list: platform name, API endpoint or connector type, refresh frequency (real-time, hourly, daily), destination Salesforce object, field mappings, and owner (who gets paged if the pipeline breaks).

Step 2: Choose Your Integration Architecture

There are four common patterns for getting marketing data into Salesforce. Each has tradeoffs in cost, maintenance overhead, and flexibility.

Option A: Salesforce Native Connectors

Salesforce offers built-in connectors for a handful of platforms — primarily Google Ads (via Marketing Cloud) and a few CRM-adjacent tools. These work well for simple use cases: syncing Google Ads campaigns to Salesforce Campaigns, mapping LinkedIn Lead Gen Forms to Leads.

Pros: No third-party vendor, no additional cost beyond Salesforce licenses, relatively stable.

Cons: Limited to a small set of platforms, no transformation layer (data arrives in raw API format), breaks when platform APIs change, difficult to customize field mappings.

Best for: Teams with fewer than 5 data sources, minimal attribution needs, and existing Salesforce Marketing Cloud licenses.

Option B: iPaaS Tools (Zapier, Workato, Tray.io, Mulesoft)

Integration Platform as a Service tools provide visual workflow builders for moving data between systems. You create "recipes" or "zaps" that trigger on events (new lead in Facebook, new opportunity in Salesforce) and execute actions (create record, update field, send webhook).

Pros: Large connector library (hundreds of pre-built integrations), point-and-click configuration, faster initial setup than custom code.

Cons: Expensive at scale (pricing tiers based on task volume, often $500–$5,000/month for marketing workloads), brittle when APIs change, limited transformation logic (no SQL, no complex aggregations), requires ongoing maintenance as schemas drift.

Best for: Teams with budget for integration tooling, straightforward field mappings, and dedicated ops resources to monitor workflows.

Option C: Custom ETL Scripts

Many engineering-heavy teams build their own data pipelines using Python, Airflow, or dbt. Scripts pull data from platform APIs, transform it in a staging database, then push it to Salesforce via the Bulk API or REST API.

Pros: Full control over transformation logic, no per-row pricing, can optimize for performance and cost, integrates with existing data infrastructure.

Cons: Requires engineering headcount, slow to add new connectors (each API is different), maintenance burden when platforms deprecate endpoints, difficult to hand off to non-technical stakeholders.

Best for: Companies with data engineering teams, complex attribution models, or unique data sources without off-the-shelf connectors.

Option D: Reverse ETL and Marketing Data Platforms

Platforms like Improvado, Hightouch, Census, and Fivetran focus specifically on marketing data integration. The architecture is: sources → centralized warehouse → transformation (dbt, SQL models) → destination (Salesforce). This pattern is called "reverse ETL" because data flows from the warehouse back into operational tools.

Pros: Pre-built connectors for 500–1,000+ marketing platforms, automated schema mapping, handles API rate limits and pagination, maintains 2-year historical data even when platforms deprecate old API versions, built-in data quality rules (deduplication, validation, null-handling).

Cons: Additional vendor in the stack, custom pricing (typically based on data volume and connector count), requires a data warehouse (Snowflake, BigQuery, Redshift) as the staging layer.

Best for: Marketing teams at scale (10+ data sources), attribution-heavy use cases, organizations already using a data warehouse for analytics.

Step 3: Map Your Marketing Schema to Salesforce Objects

Salesforce's data model is rigid by design. You can't dump arbitrary JSON blobs into the CRM — every field must be defined, typed, and mapped to a standard or custom object. This is where most implementations stall. Marketing data doesn't naturally fit into Lead → Contact → Opportunity hierarchies.

Field Mapping Rules

• Use standard fields wherever possible (Lead Source, Campaign Name, Owner). Custom fields cost storage and complicate reporting.

• Prefix custom field names with a namespace (e.g., MKT_Channel__c, MKT_Last_Touch_Campaign__c) to avoid conflicts with other teams' customizations.

• Store UTM parameters in dedicated fields, not concatenated strings. You'll need to filter and group by them.

• Create lookup relationships between custom objects and standard objects (e.g., Ad Performance → Campaign) so reports can join across them.

• Document every custom field in Salesforce's built-in field descriptions. Six months from now, no one will remember what MKT_LTV_Cohort_Q1__c means.

Historical Data Backfill

Most connectors only sync forward from the day you turn them on. If you need historical data (last quarter's campaigns, previous year's attribution), you must backfill manually. Salesforce's Bulk API supports batch uploads of up to 10,000 records per file, but you'll hit rate limits if you try to load millions of rows in one go.

Best practice: load the most recent 90 days of data first (enough to validate your pipelines and field mappings), then backfill older data in nightly batches. Monitor Salesforce storage usage — most orgs have a storage limit based on license count, and historical marketing data can consume it quickly.

Step 4: Build Your Attribution Models Inside Salesforce

Attribution is the process of assigning credit to marketing touchpoints that influenced a conversion. Salesforce doesn't provide attribution logic out of the box — you must build it using Campaign Members, Campaign Influence, or custom objects.

Three Attribution Approaches in Salesforce

First-Touch Attribution: Credit the first campaign a lead interacted with. Simple to implement — store the first Campaign ID on the Lead record when it's created, then report on Opportunities grouped by that field. Works for top-of-funnel analysis but ignores nurture and late-stage touchpoints.

Last-Touch Attribution: Credit the final campaign before conversion. Common in sales-led orgs where the "request demo" or "contact sales" campaign gets full credit. Easy to query (just look at the most recent Campaign Member record), but ignores awareness and consideration.

Multi-Touch Attribution: Distribute credit across all touchpoints. Requires custom logic to weight campaigns by position (linear, time-decay, U-shaped, W-shaped, custom algorithmic). Most teams implement this using a custom Attribution object with fields for Opportunity ID, Campaign ID, Touch Position, and Attribution Weight. A nightly batch job recalculates weights whenever Opportunities or Campaign Members are updated.

Using Campaign Influence (Standard Feature)

Salesforce's built-in Campaign Influence feature lets you associate multiple Campaigns with a single Opportunity and assign a percentage of credit to each. It works by creating Campaign Influence records (a junction object between Campaign and Opportunity) and splitting the Opportunity Amount across them.

To enable Campaign Influence:

• Navigate to Setup → Feature Settings → Marketing → Campaign Influence.

• Enable "Campaign Influence" and choose between "Campaign Influence 1.0" (basic) or "Customizable Campaign Influence" (supports multiple models).

• Define influence timeframes (how long after a campaign interaction can it receive credit).

• Create custom influence models (linear, first-touch, last-touch, positional) if using Customizable Campaign Influence.

Limitations: Campaign Influence only works with closed Opportunities. It doesn't attribute to pipeline creation or open Opportunities. If you need real-time attribution reporting, you'll need a custom solution.

Mapping UTM Parameters to Salesforce Campaigns

Most web forms capture UTM parameters (utm_source, utm_medium, utm_campaign) when a visitor converts. These need to map to Salesforce Campaigns for attribution to work. Two approaches:

Manual Mapping: Create a lookup table (spreadsheet or custom object) that maps UTM campaign strings to Salesforce Campaign IDs. When a lead is created, a workflow rule or Apex trigger reads the UTM fields and sets the Campaign Member relationship. Pros: full control. Cons: breaks when campaign naming conventions change.

Automated Mapping: Use naming conventions (e.g., utm_campaign=Q1-2026-Google-Brand) and parse the string to find or create the matching Salesforce Campaign. Requires custom code (Apex, Flow, or middleware) to handle fuzzy matching and campaign creation. Pros: scales with hundreds of campaigns. Cons: garbage-in-garbage-out if marketers use inconsistent naming.

Step 5: Automate Reports and Dashboards

Salesforce's native reporting tools (Reports, Dashboards, CRM Analytics) are sufficient for many use cases, but they require manual setup and don't scale well for complex marketing analytics.

Salesforce Reports

The classic reporting interface lets you create tabular, summary, matrix, or joined reports. For marketing, common report types include:

• Campaigns with Influenced Opportunities (shows which campaigns contributed to pipeline)

• Leads with Campaign History (shows all touchpoints for a lead)

• Campaign ROI (compares Campaign Actual Cost to influenced Opportunity Amount)

To build a report:

• Go to the Reports tab → New Report.

• Select a report type (e.g., "Campaigns with Opportunities").

• Add filters (date range, campaign type, lead source).

• Group rows (by campaign, by month, by channel).

• Add formula fields for calculated metrics (CPA, ROI, conversion rate).

• Save and schedule email delivery (daily, weekly, monthly).

Reports are easy to create but limited in visualization options. For executive dashboards, use Salesforce Dashboards (which display multiple reports as charts on one page) or export to a BI tool.

CRM Analytics (Einstein Analytics)

CRM Analytics provides a more powerful interface for exploratory analysis. You can build interactive dashboards with drill-downs, filters, and predictive models. It requires a separate license ($75–$150/user/month depending on edition) and works best when your data is already inside Salesforce.

To use CRM Analytics for marketing:

• Create a dataset by syncing Salesforce objects (Campaigns, Leads, Opportunities) into the analytics engine.

• Build a dashboard using the drag-and-drop interface or SAQL (Salesforce Analytics Query Language) for advanced queries.

• Add filters for date range, campaign type, region, product line.

• Share dashboards with stakeholders via Salesforce or public embed links.

CRM Analytics shines when you need to slice data by multiple dimensions (channel × region × product) or build predictive models (lead scoring, churn risk). It's overkill for simple campaign performance reports.

External BI Tools (Looker, Tableau, Power BI)

Many marketing teams prefer to build dashboards outside Salesforce, using BI tools that connect to their data warehouse. This approach gives you more flexibility (join marketing data with product analytics, customer support tickets, financial data) and better performance for large datasets.

The architecture is: Salesforce → ETL tool → data warehouse → BI tool. You extract Salesforce data nightly, join it with other sources, and build dashboards in Looker or Tableau. This is the most common pattern at companies with dedicated analytics engineering teams.

Step 6: Maintain Data Quality and Governance

Data quality degrades over time. Campaign names drift from naming conventions. Leads get created without UTM parameters. Duplicates accumulate. Without governance, your Salesforce analytics becomes unreliable within months.

Validation Rules

Salesforce validation rules prevent bad data from being saved. Use them to enforce:

• Required fields (every Lead must have a Lead Source)

• Format constraints (utm_campaign must follow naming pattern YYYY-QN-Channel-Tactic)

• Range checks (Campaign Budget must be greater than zero)

• Dependency logic (if Lead Source is "Paid Search", utm_source must be populated)

To create a validation rule: Setup → Object Manager → select object (Lead, Campaign, etc.) → Validation Rules → New Rule. Write a formula that returns TRUE when data is invalid, and provide an error message.

Be careful not to over-constrain. If your validation rules are too strict, sales and marketing teams will find workarounds (dummy values, manual overrides) that pollute data in different ways.

Deduplication

Duplicate leads and contacts break attribution. If the same person exists as three separate Lead records, each with different Campaign Members, your reports will show inflated reach and broken funnel metrics.

Salesforce offers built-in duplicate management (Setup → Duplicate Management), but it only flags potential duplicates — it doesn't auto-merge. Most teams use third-party tools (Cloudingo, DemandTools, Dedupely) or custom Apex batch jobs to merge records weekly.

Attribution implications: when merging records, ensure Campaign Member history is preserved. The standard merge logic keeps the oldest record's Campaigns — if you need to preserve all touchpoints, you'll need custom merge logic.

Data Governance Committee

Establish a recurring meeting (monthly or quarterly) with stakeholders from marketing, sales, ops, and analytics. Review:

• Field usage (are custom fields being populated? Which fields are always null?)

• Naming conventions (are campaign names consistent? Do they map to reporting segments?)

• Data quality metrics (duplicate rate, null rate, lead-to-account match rate)

• Pipeline health (are new connectors breaking? Are transformations still correct after platform API changes?)

Document decisions in a shared wiki. When someone asks "why do we have both Lead Source and Lead Source Detail fields?" the answer should be written down, not tribal knowledge.

Common Mistakes to Avoid

Mistake 1: Storing time-series data in Salesforce fields. Campaigns change daily (spend increases, impressions grow). If you store cumulative metrics in Campaign fields, historical reporting becomes impossible. Instead, use a custom "Campaign Daily Snapshot" object with date, campaign ID, and daily metrics. Query these records to build time-series charts.

Mistake 2: Ignoring Salesforce storage limits. Every org has a data storage limit (typically 10 GB baseline + 20 MB per user license). Marketing data — especially event logs and creative-level performance — can consume this quickly. Monitor usage in Setup → System Overview → Data Storage. If you're near the limit, archive old records or move granular data to a warehouse.

Mistake 3: Building attribution models before cleaning lead sources. If 30% of your leads have null or generic lead sources ("Website", "Other", "Unknown"), your attribution reports will be meaningless. Fix lead source tracking first (web form hidden fields, UTM passthrough, CRM integration testing), then build attribution models.

Mistake 4: Using Salesforce as your source of truth for marketing data. Salesforce is designed for operational workflows (assign leads, track opportunities, log activities), not for analytics. If you delete a Campaign in Salesforce, you lose historical performance data. Keep the source of truth in your data warehouse; treat Salesforce as a destination for operationally relevant fields only.

Mistake 5: Hard-coding campaign IDs in integrations. When you map "Google Ads Campaign XYZ" to Salesforce Campaign ID 701XX000000abcd, that mapping breaks if someone deletes and recreates the Salesforce Campaign. Use external IDs (a custom field on Campaign that stores the platform's campaign ID) and match on that field instead.

Mistake 6: Giving every user full access to CRM Analytics. CRM Analytics licenses are expensive ($75–$150/user/month). Most marketing team members don't need interactive exploration — they need scheduled reports delivered to email or Slack. Reserve CRM Analytics for analysts and dashboard builders; use standard Reports and Dashboards for everyone else.

Tools That Help with Salesforce Marketing Analytics

The table below compares platforms commonly used to integrate marketing data with Salesforce. Pricing reflects typical mid-market implementations (10–50 data sources, daily sync frequency, 500,000–5 million monthly records).

Improvado specializes in marketing data integration and provides pre-built connectors for advertising platforms, analytics tools, and CRMs. The platform handles schema normalization automatically (e.g., mapping Facebook Ads "Campaign Name" to Salesforce "Campaign"), maintains 2-year historical data even when platform APIs deprecate old endpoints, and includes 250+ built-in data quality rules to catch duplicates, null values, and schema drift before data reaches Salesforce.

Implementation time is typically days, not months — the platform's connector library covers most marketing use cases out of the box, and custom connectors are built within a week when needed. Improvado is compatible with any BI tool (Looker, Tableau, Power BI, or custom dashboards) and provides full SQL access for advanced users alongside a no-code interface for marketers.

Conclusion

Salesforce is the system of record for sales and customer data at most B2B companies, but it wasn't designed to be a marketing analytics platform. To answer questions like "which campaigns drive the highest LTV customers?" or "what's our CAC by channel?" you need to bring external marketing data into Salesforce, map it to CRM objects, build attribution models, and automate reporting.

The work is structural, not cosmetic. You're bridging two different data paradigms — event-driven marketing platforms (clicks, impressions, sessions) and object-driven CRM systems (leads, contacts, opportunities). Most teams underestimate the time required for schema mapping, historical backfill, and ongoing pipeline maintenance.

The path forward: start with a data source audit, choose an integration architecture that matches your team's technical capacity, map your schema carefully, build attribution models incrementally (first-touch first, then multi-touch), and establish data governance processes before data quality degrades. Teams that follow this sequence ship reliable marketing analytics within weeks. Teams that skip steps spend months debugging broken pipelines.

If you're building Salesforce marketing analytics for the first time, focus on getting three things right: clean lead source tracking, reliable campaign-to-opportunity attribution, and automated daily reporting. Everything else — predictive scoring, advanced segmentation, real-time dashboards — can come later once the foundation is solid.

FAQ

What is the difference between Salesforce Reports and CRM Analytics?

Salesforce Reports is the built-in reporting interface available in all Salesforce editions. It lets you create tabular, summary, and matrix reports using a point-and-click interface, but it's limited to the data already inside Salesforce objects and doesn't support advanced visualizations or predictive models. CRM Analytics (formerly Einstein Analytics) is a separate product that requires additional licensing, starting around $75/user/month. It provides a more powerful analytics engine with interactive dashboards, drill-down capabilities, SAQL query language for complex analysis, and machine learning features for lead scoring and forecasting. CRM Analytics is best for teams that need exploratory analysis or predictive insights; standard Reports are sufficient for operational dashboards and scheduled metric tracking.

How do I connect Google Ads data to Salesforce?

There are three common approaches. First, Salesforce Marketing Cloud offers a native Google Ads connector that syncs campaign performance data directly into Salesforce Campaigns, but this requires a Marketing Cloud license and only works if you're using Marketing Cloud for campaign management. Second, you can use a third-party integration platform like Improvado, Fivetran, or Zapier to pull Google Ads data via API and push it into Salesforce Campaign fields or custom objects — this approach gives you more control over field mapping and transformation logic. Third, you can build a custom integration using Google Ads API and Salesforce Bulk API, which is the most flexible but requires engineering resources to build and maintain. Most marketing teams use the second approach because it balances flexibility with maintenance overhead.

Can Salesforce do multi-touch attribution out of the box?

Not fully. Salesforce provides Campaign Influence, a standard feature that lets you associate multiple Campaigns with a single Opportunity and assign percentage credit to each campaign. You can enable this in Setup under Marketing → Campaign Influence, and it supports basic attribution models like first-touch, last-touch, and linear (equal credit to all touchpoints). However, Campaign Influence only works with closed Opportunities — it doesn't attribute to pipeline creation or open deals. It also doesn't support advanced models like time-decay, position-based (U-shaped or W-shaped), or algorithmic attribution. For those use cases, you need to build a custom Attribution object with fields for Opportunity ID, Campaign ID, Touch Position, Attribution Weight, and Influenced Amount, then write Apex code or use a middleware tool to calculate and update weights nightly.

How much does Salesforce CRM Analytics cost?

CRM Analytics pricing depends on your Salesforce edition and deployment model. As of 2026, standalone CRM Analytics licenses start at approximately $75 per user per month for the Growth edition (billed annually), which includes basic dashboards and up to 25 million rows of data per month. The Plus edition costs around $150 per user per month and adds predictive AI features, SAQL query access, and higher data volume limits. Enterprise contracts often bundle CRM Analytics with Sales Cloud or Service Cloud at discounted rates. Salesforce also offers CRM Analytics for Marketing, which is typically bundled into Marketing Cloud Advanced or Growth editions at $1,250–$9,000 per organization per month (not per user), but pricing varies significantly based on data volume, connector count, and contract negotiations. Contact Salesforce sales for exact pricing based on your org's needs.

How do I pass UTM parameters from web forms into Salesforce?

When a visitor lands on your website with UTM parameters in the URL (e.g., ?utm_source=google&utm_medium=cpc&utm_campaign=Q1-Brand), those values need to be captured by your form tool and passed to Salesforce as hidden fields. Most form platforms (Marketo, HubSpot, Pardot, Unbounce, Webflow) support hidden fields that auto-populate from URL parameters. You create hidden fields on your form with names matching your UTM parameters (utm_source, utm_medium, utm_campaign, utm_content, utm_term), then map those form fields to corresponding custom fields on the Salesforce Lead or Contact object. When the form submits, the UTM values are written to the CRM record. Best practice: also capture the first-touch UTM values (the first campaign that brought the visitor to your site) and last-touch UTM values (the campaign that directly led to form submission), which requires client-side JavaScript to read cookies or localStorage and populate additional hidden fields.

What is the best way to calculate campaign ROI in Salesforce?

Campaign ROI in Salesforce is calculated using the formula: (Total Opportunity Amount - Total Campaign Cost) / Total Campaign Cost × 100. Salesforce has standard fields on the Campaign object for this: Actual Cost (what you spent) and Total Value of Won Opportunities (sum of Amount from all influenced Opportunities that closed-won). To see ROI, create a report of type "Campaigns with Influenced Opportunities," filter for Status = Closed Won, group by Campaign, and add a formula field for ROI calculation. The challenge is attribution — you need to decide whether to give each campaign full credit (first-touch or last-touch attribution) or split credit across touchpoints (multi-touch attribution). For multi-touch, use Campaign Influence or a custom Attribution object to assign percentage weights, then multiply the Opportunity Amount by the attribution weight before summing. Without proper attribution, ROI reports will either overcount (if every campaign claims full credit) or undercount (if only one campaign per deal is credited).

Can I build real-time marketing dashboards in Salesforce?

Salesforce dashboards refresh on a schedule — typically hourly for standard Dashboards and as frequently as every 15 minutes for CRM Analytics dashboards (depending on license tier). True real-time updates (sub-second latency) aren't supported because Salesforce is an operational CRM, not a real-time analytics platform. If you need real-time visibility into ad spend, website traffic, or conversion events, use a dedicated BI tool (Looker, Tableau, Power BI) connected to your data warehouse, or use platform-native dashboards (Google Ads UI, Meta Ads Manager, Google Analytics). The better question is whether you need real-time data — for most marketing use cases, hourly or daily refreshes are sufficient because budget and campaign decisions happen at day or week intervals, not minute-by-minute.