A joint campaign here means one piece of outreach with two names on it: an accounting firm and a trade association co-hosting a webinar, a consultancy and a software reseller sharing a newsletter feature, two advisory firms splitting a conference session. It has two audiences, two brands and, unless someone decides otherwise, two referral links. The program behind it has one credit per company. Each question below closes the gap between those facts before the first email goes out.
Why shared-credit habits do not carry over
Most marketing teams arrive with an attribution model in mind. In PartnerStack and Wynter's State of Partnerships in GTM 2026 survey of 100 senior leaders at B2B SaaS companies, 42% reported multi-touch attribution, 31% first-touch, 19% last-touch and 8% other methods or no tracking at all. A co-host from that world may expect the campaign's credit to be shared, or to follow the last click. The referral program does neither. Credit is a company event decided from dated records, and SourceX's home page says attribution locks when the application is submitted.
| What a co-host may assume | What the program does | Governing text |
|---|---|---|
| Both hosts share the credit | One partner is credited per company | Terms, section 2 |
| The last link clicked wins | An earlier link click alone does not decide credit; dated records do | Terms, section 2 |
| The campaign date starts one clock for everyone | Each company's credit turns on its own dated introduction and a verified application within the 90-day window | Terms, section 2; home page |
| Every attendee is a fresh lead | A company with an earlier application, relationship or valid introduction with SourceX is a duplicate, credited to no later partner | Terms, section 3 |
| The second host will see progress | Partners never receive access to other partners' records or applicant documents | Terms, section 7 |
The general difference between marketing attribution and contractual credit is set out in separating marketing attribution from referral credit. This page applies it to two hosts at once.
The campaign's dated events, and who holds each record
Lay the timeline out before launch. In a dispute you can only use records that already exist.
| Event | The date it carries | Who holds the record |
|---|---|---|
| The submitting host signs the SourceX Channel Partner Agreement | Signature date | That host and SourceX |
| Both hosts sign the campaign rules sheet | Approval date | Both hosts |
| The webinar runs or the email is sent | Send date | The sending host |
| A company opens the partner link | Visit date, which SourceX records | SourceX |
| A host writes to a named CEO with an introduction | Email date | The introducing host |
| The company submits its application | Submission date; attribution locks | SourceX |
| SourceX verifies the application | Verification date | SourceX |
| Review, agreement, dataset handoff and Acquisition Partner acceptance | Several later dates | SourceX |
| A reward becomes payable, if every condition is met | Within 60 calendar days after the second of two dates: completed handoff and the Acquisition Partner's final written acceptance | SourceX |
SourceX may also communicate directly with a referred company, and under the terms that does not affect valid attribution. Neither host needs to sit in every thread to protect credit.
The pre-campaign rules checklist
Twelve questions, each with what happens if it is left blank. Answer every row and have both hosts sign the sheet before anything is published.
| # | Question to settle | If you leave it blank | Governing text |
|---|---|---|---|
| 1 | Which host is the partner of record for the campaign? | Credit follows whichever host's records a company happens to touch first | Terms, section 2 |
| 2 | Has the partner of record signed the SourceX Channel Partner Agreement? | No introduction can be submitted until it has | Terms, section 1 |
| 3 | Will the campaign carry one link or two? | A company that opens both creates two claims and a duplicate review | Terms, sections 2 and 3 |
| 4 | How will the hosts share anything that follows? | Nothing is shared: the terms credit one partner and describe no split | Terms, section 2, plus your own agreement |
| 5 | Does either host have a signed Schedule A or addendum? | The published default reward applies to the partner of record | Terms, section 8 |
| 6 | Which companies does each host already hold a dated written introduction for? | A later argument over whether the campaign or the earlier note came first | Terms, section 2 |
| 7 | What will attendees that SourceX already knows be told? | The hosts imply a credit nobody can deliver | Terms, section 3 |
| 8 | Who follows up with interested companies, and is it the CEO? | Follow-up reaches whoever registered, often someone who cannot authorize | Who qualifies page |
| 9 | What does the campaign disclose about referral interest, and where? | Readers cannot tell that either host may be paid | FTC endorsement guidance |
| 10 | If the email is joint, who is the designated sender? | Both hosts may carry sender duties under US law | FTC CAN-SPAM guide |
| 11 | What evidence will each host keep, and for how long? | Records that cannot be dated when they are needed | Terms, sections 2 and 7 |
| 12 | Who raises a dispute, and what will the other host accept in advance? | Two hosts filing against each other | Terms, section 7 |
Five rows need more than a sentence.
Row 4, sharing. The published terms credit one partner per company and say nothing about dividing a reward between co-hosts, so any sharing is a private agreement between the hosts. It should cover three things: the split, what happens if the reward is later reduced (the terms reduce a reward proportionately when the supplier payout is reduced or reversed), and that the second host looks to the partner of record for its share, not to SourceX.
Row 6, earlier introductions. A host that wrote to a company's CEO in September already holds a dated record that may predate the campaign. List those companies by name only, and only where the client relationship allows it, then agree that the campaign leaves them with the host that introduced them.
Row 7, companies SourceX already knows. Under the terms, a company already has a relationship with SourceX if there was any earlier lead, account or email correspondence between them, however it began, and SourceX checks its own records before inviting an introduced company. Neither host can see those records. So the campaign cannot promise any attendee that an introduction "counts"; it can only invite companies to apply.
Row 9, disclosure. The FTC's endorsement FAQ, written for US advertising, says a relationship like this should be disclosed clearly and conspicuously where readers see it with the link, and that a label such as "commissionable link" is probably not clear. A plain line works better: "[Firm] and [Association] may receive a referral reward from SourceX if a company we introduce completes a qualifying paid licensing deal." Name both hosts even when only one is the partner of record, because a private split is a connection too. The FTC disclosure examples offer more wording.
Row 10, the sender. The FTC's CAN-SPAM compliance guide lets several marketers in one email designate a single sender, but that sender must meet the Act's definition and appear in the "from" line, and if it fails to comply, every marketer in the message can be held liable as a sender. Decide which host it is, use that host's list rules and opt-out process, and remember that lists outside the US carry their own consent rules.
Four companies from one co-hosted webinar (Illustrative)
Illustrative: invented firms and companies; the dates show how the rules apply, not real outcomes.
A 40-person accounting firm, a registered partner whose Channel Partner Agreement was signed on 1 October 2026, co-hosts a webinar on 12 November 2026 with a regional manufacturers' association that is not registered. The signed rules sheet names the firm as partner of record, uses one link and records a written split of anything that follows.
| Company | Dated events | Result | Governing text |
|---|---|---|---|
| 160-person precision machining company | CEO opens the campaign link on 12 November; the company applies on 3 December, day 21 | Credited to the firm if the application is verified and SourceX holds no earlier record; the association's share comes from the rules sheet | Terms, section 2; home page |
| 420-person plastics molder | COO emailed SourceX in June after reading an article; CEO attends the webinar; the company applies through the link on 20 November | Duplicate: SourceX already had email correspondence with the company, so no host is credited | Terms, section 3 |
| 95-person tool-and-die shop | Owner opens the link on 12 November; no further contact; the company applies directly on 1 March 2027, day 109 | Do not claim it: the only dated record is more than 90 days old; ask for review only if another dated record exists | Terms, section 2 |
| 230-person foundry | The association's director registers as a partner on his own, against the rules sheet, and emails the CEO an introduction with his link on 30 October; the CEO opens the firm's link on 12 November and applies through it on 25 November | Unresolved: two partners hold dated records, and duplicate review decides | Terms, sections 2, 3 and 7 |
The fourth row is the one the rules sheet exists to prevent. One host registering separately mid-campaign turns a shared project into a credit dispute between two partners, and only SourceX can settle it.
What to send when a case goes to review
For disputes, the terms ask partners to write to SourceX with the referral details and supporting evidence; SourceX then reviews the case and tells them its decision. Keep the file short:
- the company's legal name and website, and the partner account that claims it;
- each dated record you hold: the written introduction with its date and the recipient's role, and any link visit your dashboard shows;
- the campaign's send date and channel, with a copy of the message as sent;
- for a dispute between two hosts who are both registered, the signed rules sheet.
Leave out attendee lists beyond the company in question, anything from the company's own systems and anything about another partner. Partners never receive access to other partners' records, so there is no point asking.
What the published terms leave to the hosts
The terms do not address co-branded material, use of SourceX's name in a campaign, paid promotion or how co-hosts divide a reward. Ask SourceX in writing before launch about anything that carries its name, and file the answer with the rules sheet. For the single-host version of this work, see preparing a referral link for an association newsletter and the industry association email templates. When two partners have already collided, what happens if two partners introduce the same company explains duplicate review, and when a company registers twice covers one company filing two applications.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
Once both hosts have signed the rules sheet, the partner of record can register for a partner link, check target companies against who qualifies and keep the program terms open while the campaign copy is written.