A co-marketing campaign can produce shared content and broader reach, but it also creates extra handoffs. The partner may approve the message, the two teams may use different audience definitions, and new responses can arrive without a clear owner.
A short brief makes the joint work concrete before either organization publishes. It identifies what each side will deliver, how responses will be handled, and what the teams can learn after the campaign ends.
Agree on one audience and one useful outcome
Describe who the campaign is for, what problem the audience is trying to solve, and why the two organizations are contributing. Be specific about which customer or account groups are in scope and which are excluded.
Choose one primary outcome that both teams can observe, such as registrations, attended sessions, requested consultations, or qualified conversations. Keep each partner’s own commercial outcome visible, but do not let two different definitions of success appear as one shared metric.
Before choosing the format, ask whether the proposed content or event helps the shared audience. A partner logo alone does not create a useful offer. Decide what each organization contributes: expertise, distribution, customer context, production, budget, or follow-up.
Assign owners for the work and approvals
List each deliverable and the person responsible for it. Include the brief, copy, design, landing page, registration form, partner logo, speaker material, promotion, event delivery, follow-up, and report. Name who can approve the final asset at each organization and how long review is expected to take.
Agree on what happens when a partner requests a change near launch. Set a final approval date and a contact for an urgent issue. For customer logos, quotes, or outcome claims, use the same exact-asset approval record described in the customer-logo and quote approval guide.
Keep the campaign name and ID consistent across both systems. Decide whether each partner uses its own campaign record, whether a shared event ID is used, and how source and influence will be reported. The guide to separating opportunity source from marketing influence helps keep those questions distinct.
Define lead ownership before collecting responses
Agree on the moment a response becomes a handoff, the information required, who receives it, and the response expectation. The trigger might be a requested consultation, a qualified question, a form submission that meets agreed criteria, or an event participant who asks to be contacted.
Do not promise that both partners will receive a full contact list unless the agreement, disclosure, and applicable data rules support that use. Decide which organization collects the information, how the person is told about the follow-up, and whether records will be shared, matched, or routed separately. Ask qualified counsel when the data arrangement or jurisdiction requires it.
For every handoff, record the campaign, lead or contact, partner source, response status, recipient owner, sent time, and accepted or rejected outcome. Salesforce’s campaign-member fields provide one example of recording a related campaign, lead source, response state, and first response date. The field names and workflow differ across systems, so document your local mapping.
Set a fallback if a partner does not accept or respond to a handoff. Name who will follow up, when the other team will be notified, and how duplicate or out-of-scope responses will be resolved. Keep the rule aligned with the general campaign member status guide.
Keep the operating plan easy to find
Store the brief, approved creative, campaign links, audience criteria, partner contacts, and final report in one shared location with access appropriate to both teams. Include the campaign dates, publishing sequence, owner for each channel, and the time when each partner will stop promotion.
Use a short launch check before publication: test the registration path, confirm the correct partner and offer details, validate the tracking fields, confirm the thank-you message, and verify the handoff recipient. The marketing incident log can capture a live issue if a form or integration fails.
After the campaign, compare planned delivery with what each partner actually completed. Review target-audience fit, response quality, handoff timing, accepted leads, and later opportunity outcomes. Record which data is still incomplete and agree on whether the partnership should repeat, change, or stop.
A co-marketing brief
- Campaign name, shared ID, and dates: ______
- Audience, problem, and exclusions: ______
- Shared outcome and each partner’s own objective: ______
- Offer, content, and value to the audience: ______
- Deliverable, owner, and approval deadline by organization: ______
- Promotion channels and tracking conventions: ______
- Lead or response handoff trigger: ______
- Data collected, notice shown, and permitted recipient: ______
- Receiving owner, response expectation, and fallback: ______
- Campaign closeout and reporting date: ______
If partner responses are arriving without clear ownership or data terms, request a marketing diagnostic to map the shared campaign workflow.
Related reading
Read the campaign member status guide for handoff states and the partner access guide for controlled access to customer data.
Sources and scope
- Salesforce Help: Campaign Member Fields — documents example campaign-member fields, including campaign, lead source, response status, and first response date.
- HubSpot Knowledge Base: Use marketing events — describes event records and participant-status tracking for connected or imported event data.
CRM fields and partner workflows vary. Put the shared responsibilities and data terms in the agreement, and apply the privacy and consent rules that govern the organizations and contacts involved. Accessed October 8, 2026.
How did this article land?
Choose one reaction. You can change it anytime.