
Co-Marketing Agreements
Integration partnership marketing
An integration partnership is worth promoting when two products make a customer task easier together. Start with the task, the data or action crossing between …
Promote an integration partnership when two products make a customer task easier together. Start with the task, the data or action crossing between products, and the limits of the connection. Two logos and a launch announcement are not a customer benefit.
Most integration marketing runs through an app marketplace such as HubSpot’s App Marketplace or the Atlassian Marketplace. Atlassian notes that most customers find apps through Marketplace search, so the listing is the first thing to get right.
Agree on the joint promise
Write one use case that both vendors can demonstrate. State which customer needs which accounts, permissions or subscription levels, what setup is required, and what happens if a sync fails.
Product and support teams verify the claims before marketing writes copy. If the connection only transfers selected fields, do not call it a complete two-way sync.
Test the install path and refine listing copy for clarity. Treat a clear app listing as a central discovery asset. HubSpot points to Demodesk, whose listing uses every content type available, and to Aircall, which publishes its listing in English, French, German and Spanish; localised listings appear first for users with that default language.
If customer data crosses between the products, the written agreement should record who handles it and how. In Australia, the Privacy Act 1988 covers organisations with an annual turnover of more than $3 million and some others, and its principles cover use or disclosure (APP 6) and the steps needed before disclosure overseas (APP 8).
Select a distribution route
Partnership marketing can extend beyond the two vendors' own channels. On the Atlassian Marketplace, engaging solution partners for distribution sits alongside app discount programs, sales promotions and trial-to-paid conversion as customer-acquisition strategies.
Treat partner distribution as a defined workstream. Decide which partner can make an introduction, agree what material they can use and where it will appear, and choose channels each partner can genuinely support.
Agree responsibilities in advance so promotion does not depend on one partner doing all the work. Do not assume both vendors have the same reach or capacity. Each partner should also feature the integration on its own website, integration directory or in-app; Typeform recorded an all-time high in new HubSpot integration installs in the month it placed that integration first in its own marketplace.
Build a joint content mix
Use more than an announcement to make a partnership visible. Create launch materials such as a press release, blog posts, case studies and social media content.
Choose content both teams can contribute to and approve. A joint blog post gives each partner a role in explaining the collaboration. A case study shows how the partnership has been put into practice. Keep claims, screenshots and compatibility details consistent with what both product teams have verified.
Plan how each partner will distribute the content, not just who will write it. A listing alone will not drive traffic; use external content to support discoverability and credibility.
Partners can coordinate their own blog and social activity around shared material, without relying on identical posts or audiences. Certification can add weight: QuotaPath reported roughly twice the quantity and quality of opportunities from HubSpot after its app gained the HubSpot Certified App flag.
Use partner promotions carefully
Promotions can be part of the acquisition plan, but choose an offer both partners can support. Options include app discount programs, sales promotions and campaigns. Before promoting an offer, agree which product or service it covers, how it will be presented and which partner keeps the details current.
A promotion is not the only way to support adoption. Trial-to-paid conversion optimisation is another lever.
Treat this as shared commercial activity: agree how each partner will support prospective customers during evaluation. Ensure the messages and hand-offs are consistent across the partners' channels. If paid search ads use the marketplace owner's brand, check its trademark policy first; Atlassian asks app partners to review its AdWords trademark policy.
A discount or paid channel should have a clear role in the plan, not be added simply because it is available.
Make participation practical
Give each partner a manageable contribution. Agree how much time each team can commit and which partner has the final call on wording, so joint activity does not stall between teams.
Prepare partners to respond when promotion generates interest. Monitor early uptake and usage, and be ready for support enquiries after launch.
For a partnership campaign, agree how questions will be routed to the right partner. Agree how either team can flag an issue that needs a response.
Keep processes for ongoing updates, editions and support running alongside acquisition activity such as partner distribution and promotions. Review the activity when the offer or integration changes, and update shared materials that are no longer accurate.
Divide the work
Workstream / Joint decision
- Product proof
- Which real workflow can both teams reproduce?
- Claim approval
- Who signs off screenshots, compatibility and limitations?
- Distribution
- Which audience and channel can each partner reach legitimately?
- Support
- Who owns installation, data mapping and incidents?
Agree a process for pausing inaccurate material if the integration changes. Include who can call a pause and how quickly the other partner is notified.
In this guide
- Explaining the customer benefit of a product integrationAn integration description should show what a customer can do after connecting two products. “Seamless integration” says little. Replace it with a concrete flow …
- Planning an integration launch with another vendorAn integration launch has two dependencies: the connection must work, and both partners must describe it the same way. Agree on a launch owner on each side before …
- Creating an accurate joint solution pageA joint solution page should let a customer decide whether two products work together for their use case. Lead with the task and outcome, then explain the …
- Measuring enquiries tied to an integration use caseA joint launch may produce listing views, partner referrals, enquiries and actual integration use. These are different events. Define one qualified enquiry before …



