CRM & Cloud Marketplace Integration (2026)

CRM and cloud marketplace integration connects your customer relationship management system (Salesforce, HubSpot) with your AWS, Azure, or GCP Marketplace operations. It enables deal data, co-sell referrals, and subscription status to flow between your CRM and the marketplace — so your sales team has visibility without switching between systems.

What is CRM marketplace integration?

When an enterprise buyer subscribes to your software through AWS, Azure, or GCP Marketplace, that transaction does not automatically appear in your CRM. The cloud provider's seller portal and your CRM are separate systems with no default connection. CRM marketplace integration closes that gap.

At a practical level, integration means:

• A new marketplace subscription creates or updates a deal in your CRM automatically.
• Co-sell referrals submitted to AWS, Azure, or GCP are tracked alongside your direct pipeline.
• Subscription renewal dates appear in your CRM so sales can run renewal outreach without exporting reports from each cloud portal.
• Finance sees marketplace revenue in the same system as direct sales revenue.

Without this integration, marketplace data becomes a blind spot. Sales teams cannot see which pipeline deals closed via marketplace. Revenue operations teams cannot measure marketplace ROI. Leadership cannot see the full picture of how marketplace compares to direct sales as a channel.

Why CRM integration matters for marketplace ISVs

Without integration, marketplace deals are siloed. Here is what breaks in practice:

Sales pipeline visibility

Sales reps need to see deal status, subscription start and end dates, and co-sell referral progress in one place. If a buyer subscribes via AWS Marketplace, that event should create or update an opportunity in your CRM — not require a rep to log into Seller Central and manually copy details.

Co-sell referral tracking

Co-sell referrals from AWS, Azure, and GCP need to be tracked alongside your direct pipeline. When an AWS account executive submits a co-sell referral for one of your deals, that referral and its status should be visible in your CRM — not just in AWS Partner Central. Without this, co-sell referrals fall through the gaps and response times suffer.

Renewal management

Marketplace subscriptions have structured end dates. If those dates are not in your CRM, your sales team cannot run timely renewal outreach. Missed renewals are especially costly for annual contracts where buyers have to restart procurement.

Revenue reporting

Finance needs marketplace revenue data in the same system as direct sales for accurate commission calculations, revenue recognition, and board reporting. Without CRM integration, someone has to manually reconcile marketplace disbursements against CRM deals every month.

Salesforce + AWS Marketplace: ACE integration

AWS provides a native Salesforce integration for co-sell through AWS ACE (APN Customer Engagements), the deal registration and co-sell pipeline tool inside AWS Partner Central.

What ACE integration enables

• ISVs can create co-sell referrals directly from Salesforce opportunities and submit them to AWS through the ACE pipeline manager.
• AWS sellers can view submitted referrals, accept them, and update referral status — and those status updates sync back to Salesforce.
• Sales reps can see co-sell status without leaving Salesforce: whether a referral is pending, accepted, or closed by the AWS team.
• The integration supports bidirectional referral flow: ISVs can accept inbound referrals from AWS sellers directly in Salesforce.

ACE and ISV Accelerate

The AWS ISV Accelerate program requires ACE integration for co-sell deal submission. ISVs who want the benefits of ISV Accelerate — priority co-sell support, reduced marketplace transaction fees, and co-sell credits — must register their deals through ACE. For Salesforce users, the native connector makes this straightforward. For other CRMs, deal submission requires the ACE web interface or a custom API integration with AWS's Partner Opportunity API.

Marketplace subscription data in Salesforce

The ACE integration covers co-sell referral data. For marketplace subscription data (actual transactions, subscription start/end dates, buyer account IDs), Salesforce requires an additional integration layer:

• AWS does not push subscription events directly into Salesforce by default.
• ISVs can build a custom integration that listens to AWS Marketplace webhook events and writes subscription data to Salesforce objects.
• Marketplace management platforms (like Automatum) handle this automatically as part of the managed service, pushing subscription and renewal data into Salesforce without custom development.

HubSpot + cloud marketplace integration

HubSpot does not have a native integration with AWS, Azure, or GCP Marketplace. This is a significant operational gap for ISVs who use HubSpot as their primary CRM — and it is one of the most common integration challenges we see when onboarding marketplace-stage ISVs.

Options for HubSpot-based ISVs

Option 1: Middleware tools (Zapier, Make)

HubSpot users can use middleware platforms like Zapier or Make to pull marketplace events into HubSpot. The general pattern:

1. Configure a webhook endpoint to receive marketplace subscription events (subscribe, unsubscribe, renew) from the cloud provider.
2. A Zapier or Make workflow listens to those webhooks and creates or updates HubSpot deals based on the event payload.
3. Custom HubSpot properties store marketplace-specific fields: subscription ID, buyer account, subscription end date, private offer ID.

This approach works but requires maintenance as marketplace API schemas change. It also does not cover co-sell referral tracking for Azure or GCP, which have no published webhook or Zapier connector.

Option 2: Marketplace management platform

A marketplace management platform handles the integration layer. Automatum, for example, pushes subscription data into HubSpot properties as part of the managed service — so ISVs get marketplace → HubSpot sync without building or maintaining custom integrations. This covers subscription status, renewal dates, and private offer tracking.

AWS co-sell from HubSpot

For co-sell deal submission to AWS ACE from HubSpot, options are more limited than Salesforce:

• HubSpot users can submit co-sell referrals via CSV upload to AWS Partner Central. This is manual and requires discipline to keep data in sync.
• AWS has published a Partner Opportunity API that allows programmatic referral submission. HubSpot-based ISVs can build a custom workflow that submits ACE referrals via API when a deal reaches a defined stage in HubSpot.
• Some marketplace management platforms handle ACE submission for HubSpot users as part of their co-sell workflow tooling.

Azure Marketplace + CRM integration

Microsoft's co-sell program and Azure Marketplace operate through Microsoft Partner Center. There is no native Salesforce or HubSpot connector for Partner Center co-sell published by Microsoft for the general partner community (Microsoft has Dynamics 365 co-sell connectors, but these target partners who use Dynamics, not Salesforce or HubSpot).

Tracking Azure co-sell in Salesforce or HubSpot

ISVs handling Azure co-sell in Salesforce or HubSpot typically:

• Create custom Salesforce or HubSpot fields to track Azure co-sell referral IDs, Partner Center status, and referral dates.
• Update these fields manually after checking Partner Center, or via a custom webhook integration that calls the Microsoft Partner Center API.
• Use the Microsoft Partner Center Referrals API to programmatically read and write co-sell referral data — this requires custom development but enables real-time sync.

Azure subscription data in CRM

Azure Marketplace subscription events are available through the Azure Marketplace SaaS Fulfillment APIs. ISVs can build webhook listeners for subscription lifecycle events (subscribe, unsubscribe, renew, update) and route that data into their CRM. As with AWS, a marketplace management platform handles this automatically without custom development.

GCP Marketplace + CRM integration

Google Cloud Partner Advantage is the co-sell platform for GCP. Like Azure, there is no published native Salesforce or HubSpot connector for Google's co-sell infrastructure. ISVs submit co-sell referrals through the Partner Advantage portal directly.

GCP subscription data in CRM

GCP Marketplace subscription events flow through Google Cloud Pub/Sub. ISVs that build their own GCP Marketplace integration receive subscription events via Pub/Sub and can route them into their CRM. The integration requires a Cloud Run or App Engine service to consume Pub/Sub messages and write to Salesforce or HubSpot via their respective APIs.

This is more complex than AWS and Azure subscription integration. Most ISVs rely on a marketplace management platform to handle GCP subscription → CRM sync rather than building it themselves.

Key data to sync from marketplace to CRM

Regardless of cloud provider or CRM, these are the fields every ISV should capture in their CRM from marketplace transactions:

Frequently asked questions