Connect SharpSpring
In the client’s workspace, open Sources, add SharpSpring and choose the account to sync. If you don’t have access to the account, send the client a connect link where the platform supports one.
CRM & marketing automation integration
Turn SharpSpring pipeline, leads, and email marketing into governed revenue reporting your clients can trust.
What you can do with SharpSpring in Maven
Maven connects SharpSpring and models opportunities, deal stages, leads, campaigns, and email into governed CRM and marketing-automation metrics. Track pipeline value, weighted pipeline, win rate, and average days to close alongside the full lead funnel — MQL rate, SQL rate, and lead conversion rate — then break every result down by stage, pipeline, owner, lead source, or lifecycle stage. Report SharpSpring email engagement — sends, unique opens, click rate, and attributed revenue — beside the pipeline it drives, and tie closed deals back to the Google Ads and Facebook campaigns that sourced them.
What you can measure
Maven keeps SharpSpring numbers consistent across dashboards, reports, and answers so the team is not debating which spreadsheet is right.
Average number of days open deals have remained in their current pipeline stage
Average days from creation to close
Average CRM deal amount calculated from deal amount divided by deal count
Average CRM forecast probability across deals that provide a forecast probability
Average age of currently-open deals in days (creation to today)
Average pipeline-stage probability across represented CRM deals
CRM deals whose stage outcome is won or lost
CRM deal-to-account associations where native account IDs are available
CRM deal association rows or summary counts, summed per deal
CRM deal-to-contact associations where native contact IDs are available
CRM deal amount for monetary CRM opportunities; FranConnect lead rows have no amount
CRM deals or franchise-sales leads at deal grain
Pipeline amount weighted by stage probability
Closed-won deals divided by all closed deals
Deals marked closed-won at the CRM stage outcome
CRM deal-to-account associations where native account IDs are available
CRM deal association rows or summary counts, summed per deal
CRM deal-to-contact associations where native contact IDs are available
Average native lead score across CRM leads that provide a score
CRM leads or contacts marked converted by native or inferred lifecycle evidence
CRM leads or contacts that resolve to ecommerce customer identity
Converted CRM leads divided by all CRM leads
CRM leads or contacts at lead/contact grain
CRM leads matched to ecommerce customers divided by all CRM leads
Qualified CRM leads divided by all CRM leads
CRM leads or contacts whose conformed lifecycle stage is marketing-qualified lead
Marketing-qualified CRM leads divided by all CRM leads
CRM leads or contacts marked qualified by native or inferred lifecycle evidence
CRM leads or contacts whose conformed lifecycle stage is sales-qualified lead
Sales-qualified CRM leads divided by all CRM leads
Current-stage snapshot observations in the CRM stage history surface
CRM stage/property history events plus current-stage observations
Cumulative closed deal amount as of the snapshot date.
Deals in the stage as of the snapshot date.
Cumulative closed-lost deals as of each snapshot date
Open deal amount in the pipeline as of each snapshot date
Open deals in the pipeline as of each snapshot date
Probability-weighted open pipeline value as of each snapshot date
Cumulative closed-won deals as of each snapshot date
Closed CRM deals with deterministic campaign attribution matched to paid delivery
CRM deals with deterministic campaign attribution matched to paid delivery
Won CRM deals with deterministic campaign attribution matched to paid delivery
Paid-media clicks represented in the paid-to-CRM surface
Paid spend divided by attributed CRM deals
Paid spend divided by attributed won CRM deals
Attributed deals backed by a deterministic identity match
Paid-media impressions represented in the paid-to-CRM surface
Paid-media spend on campaign-day rows with CRM attribution coverage; group or filter by spend_currency
Closed CRM deals with deterministic campaign attribution matched to paid delivery
CRM deals with deterministic campaign attribution matched to paid delivery
Won CRM deals with deterministic campaign attribution matched to paid delivery
Attributed deals backed by a deterministic identity match
Orders attributed to the send by the email platform.
Revenue attributed to the send by the email platform.
Bounced emails from connected email send performance rows
Unique clicks divided by emails delivered
Email clicks including repeat clicks at send grain
Unique opens divided by emails delivered
Email opens including repeat opens at send grain
Replies received from connected email send performance rows.
Spam or abuse reports from connected email send performance rows.
Unique recipients or profiles that clicked at send grain
Unique recipients or profiles that opened at send grain
Unsubscribes from connected email send performance rows
Emails delivered by connected email platforms at send grain
Emails sent by connected email platforms at send grain
Conversions reported by Iterable
Message bounces reported by Iterable
Message clicks reported by Iterable
Message opens reported by Iterable
Messages sent by Iterable
Revenue attributed by Iterable
SMS bounces reported by Iterable
Unsubscribes reported by Iterable
Push bounces across connected messaging platforms
Push opens across connected messaging platforms
Push messages sent across connected messaging platforms
SMS messages received across connected messaging platforms
SMS messages sent across connected messaging platforms
Orders attributed to SMS sends
Revenue attributed to SMS sends
SMS message bounces across connected messaging platforms
SMS message clicks across connected messaging platforms
SMS messages delivered across connected messaging platforms
SMS unsubscribes across connected messaging platforms
Orders attributed to the send by the messaging platform. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. Email and SMS platforms report attributed ecommerce orders; Iterable rows use Iterable purchases.
Revenue attributed to the send by the messaging platform. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider.
Bounced messages at send grain across email, SMS and push. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider.
Clicks including repeat clicks at send grain across email, SMS and push. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider.
Conversions reported by the messaging platform. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. Definitions differ by provider: Iterable email rows carry Iterable custom conversion events, while email-platform and SMS-platform rows carry attributed orders (equal to message_attributed_orders). Filter platform = iterable for Iterable conversions.
Opens including repeat opens at send grain. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. Email opens are pixel opens (inflated by privacy proxies such as Apple MPP); push opens are app opens from a notification; SMS rows carry no opens. Do not compare open counts across channels; filter channel = email for email opens.
Replies received from connected send performance rows. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. Only email-platform rows populate replies.
Spam or abuse reports (complaints) from connected send performance rows. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. Iterable complaints are reported as spam reports; SMS and push rows carry none.
Unique recipients or profiles that clicked at send grain. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. SMS-platform rows report no unique clicks and carry total clicks instead (unique_clicks = clicks), and Iterable rows are 0; filter channel = email for true email unique clicks.
Unique recipients or profiles that opened at send grain. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. Only email-platform rows populate unique opens (Iterable, SMS and push rows are 0), so the total equals email unique opens.
Unsubscribes attributed to sends across email, SMS and push. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. Counts unsubscribers, not unsubscribe events (see message_unsubscribe_event_count).
Messages delivered at send grain across email, SMS and push. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. Email-platform and SMS-platform rows report native delivered counts; Iterable email, SMS and push rows derive delivered as sent minus bounces.
Inbound SMS messages received across connected messaging platforms. Only SMS rows populate this measure. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider.
Messages sent at send grain across email, SMS and push. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. Filter channel = email for emails sent.
Fractional conversion credit under the first-touch model by conversion touchpoint
Fractional conversion credit under the last-touch model by conversion touchpoint
Fractional conversion credit under the linear model by conversion touchpoint
Fractional conversion credit under the data-driven Markov removal-effect model by conversion touchpoint
Fractional conversion credit under the position-based model by conversion touchpoint
Fractional conversion credit under the data-driven Shapley-value model by conversion touchpoint
Fractional conversion credit under the time-decay model by conversion touchpoint
Canonical conversion/lead events counted through normalized last-touch weights
Source-neutral interactions that were answered
Average duration in seconds among answered interactions
Average session duration in seconds with each session counted once
Touchpoints that opened a session
Share of represented interactions that were answered
Source-neutral interactions represented as attribution touchpoints
Touchpoints that closed a session
Phone interactions that were neither answered nor sent to voicemail
Total interaction duration in seconds
Journey touchpoint events recorded before conversion credit allocation
Source-neutral interactions that reached voicemail
Questions you can ask
Maven’s agent answers in plain language with the right metric definitions applied automatically. These are real, verified questions it can run today.
What is our deal pipeline value by stage for deals created in the last 90 days?
Show closed deals by stage
Show average days to close by owner
Show average open deal age by owner
Show open pipeline by stage
Show won and lost deals in the latest pipeline snapshot by stage
Show closed amount by pipeline in the latest pipeline snapshot
How many ServiceTitan bookings did we get in the last 30 days?
Connection and sync
You connect SharpSpring with account ID and secret key from the SharpSpring account. Maven stores them encrypted. Each SharpSpring sync takes a fresh copy of the current records, so the workspace always reflects what is in SharpSpring now.
Fields: account name, custom fields
Fields: account name, custom fields
Fields: account name, custom fields
Fields: account name, custom fields
Fields: account name, custom fields
Fields: account name, custom fields
Fields: account name, custom fields
Fields: account name, custom fields
Fields: account name, custom fields
Fields: account name, custom fields
Fields: account name, custom fields
Fields: account name, entity type
Fields: account name, custom fields
Fields: account name, custom fields
Fields: account name, custom fields
Fields: account name, custom fields
How it works
No SQL or warehouse setup. Connect the source, then build the client’s report by asking Claude or ChatGPT.
In the client’s workspace, open Sources, add SharpSpring and choose the account to sync. If you don’t have access to the account, send the client a connect link where the platform supports one.
Maven pulls the client’s SharpSpring data (15 objects) and models it into documented tables. No SQL, warehouse or pipeline setup.
Build the client’s report or deck by asking Claude or ChatGPT through the MCP, set alerts on what matters, and publish to the client’s portal once you approve it.
Works well with
FAQ
Maven exposes 129 governed SharpSpring metrics, including Average Days in Current Stage, Avg Days to Close, Avg Deal Size, Average Forecast Probability, Avg Open Deal Age and Average Stage Probability — each defined once so it means the same thing in every report.
You can break SharpSpring metrics down by Deal Name, Pipeline, Deal stage, Stage Probability, Stage outcome, Source Timezone, Close date and Forecast Probability, and more.
Yes. SharpSpring sits in the same client workspace as sources like Google Ads, Facebook Ads, Google Analytics 4, Google Search Console and Shopify, so one report or question can use them together.
Maven syncs SharpSpring automatically: a fast first source pull after connecting, then scheduled refreshes that keep reports current. The last successful sync time is always visible, so you know the source data is fresh before it feeds a trusted reporting workflow.
Yes. Maven models SharpSpring opportunities, deal stages, and lead funnel alongside email sends and engagement, so the same workspace can answer pipeline questions — value, win rate, and days to close by stage or owner — and email-performance questions like open rate, click rate, and attributed revenue by campaign.
Yes. Maven encrypts integration credentials and tokens, scopes access to the workspace, and uses the connection only to sync the reporting data needed for governed analytics.
Set up your first client, build their report by asking Claude or ChatGPT, and publish it to their portal.
Nothing is charged unless you subscribe.