Partner operations managers live with dashboards that count clicks. This page is for the gap between that count and the number that matters, the companies credited to you.
Why a click never names a company
Start with what a click actually records. SourceX's privacy page says it records referral link visits using a first-party identifier and stores a hashed network address for fraud prevention. Browser documentation explains where an identifier like that lives: a cookie is a small piece of data a server sends to a user's web browser, which keeps it and returns it to the same site on later requests. Put together, a visit identifies one browser, on one device, on one network. It says nothing about who was at the keyboard or which company they speak for.
A company first appears when it applies. The company applies itself at /apply, and the referral home page says attribution is locked when the application is submitted. SourceX then verifies the application and checks its own records. Only after that is one partner paired with one company.
| Question | Answered by a click? | Answered by what |
|---|---|---|
| Was my link opened? | Yes | The visit record |
| Who opened it? | No | Your written introduction, which names the person |
| Which company did they act for? | No | The application, and your introduction record |
| Was the company new to SourceX? | No | SourceX's duplicate check of its own records |
| Whose introduction counts? | No | Dated records, judged under the terms |
The event-to-entity attribution map
Eight events, in the order they usually occur. The third column is the point: each event identifies a different kind of thing, and only the last two reach the company that gets credited.
| # | Event | The entity it actually identifies | What it cannot tell you | Role in credit |
|---|---|---|---|---|
| 1 | Link opened | One browser on one device | Who was at the keyboard, or for which company | A visit, nothing more |
| 2 | Visit recorded | A first-party identifier and a hashed network address | Whether two visits were one person | Fraud checks |
| 3 | Written introduction | A named person at a named company, from a named partner, on a date | Whether the company is new to SourceX | The introduction record |
| 4 | Portal submission | Partner, company, domain and timestamp | Whether the company will apply | The introduction record |
| 5 | Application at /apply | The company as the applicant names it | Whether that name is the legal entity or a group member | Attribution locks here |
| 6 | Verification | A verified applicant | Who else claims it | Confirms there is a real company |
| 7 | Duplicate check | The company, set against SourceX's own records | Anything about payment | Decides whether the company is new |
| 8 | Credit | One partner paired with one company | Whether a reward will become payable | The attributed company |
Events 3 and 4 are yours to create, and they carry the most weight before the application exists. The partner agreement says every introduction record must identify the company, its domain, the partner, the opportunity, the introduction method and timestamps. A click carries none of that except, at best, a timestamp. The referral link explainer follows the link's own trail; this map follows the entity.
Five rungs between a browser and a credited company
Every mismatch between clicks and credit happens on one of these rungs. Record the right-hand column and most disputes never start.
| Rung | Typical mismatch | What to record |
|---|---|---|
| 1. Browser to person | A shared laptop, an assistant opening mail, a forwarded link | The name and role of the person you introduced |
| 2. Person to organization | An advisor, investor or board member clicks; one executive sits on two boards | Which company the person spoke for in your conversation |
| 3. Organization to domain | Brand domains, regional domains, a founder using personal email | The company's primary web domain |
| 4. Domain to legal entity | A trade name that differs from the registered name | The registered legal name and a public identifier |
| 5. Legal entity to group | A holding company introduced, an operating subsidiary applies | Both entities and how they relate |
Rung 4 is where finance already has a model. The Legal Entity Identifier, a 20-character code under the ISO 17442 standard, is unique to one legal entity, and GLEIF's reference data records ownership structure alongside it. Most private companies a partner introduces will not have one; a state or national registration number does the same job on your record. The principle carries over: the thing that gets credited is a legal entity with an owner, not a brand or a website.
Rung 5 has one settled rule. For the USD 50,000 floor, which applies once per referred company, and for the 12-month Repeat Window, a parent and every subsidiary it owns are counted as a single company. Which introduction is credited when separate entities in one group arrive by different routes is a question for review, not for the dashboard. Renamed companies need a fixed identifier across the change, as the rebrand evidence worksheet shows.
Above all five rungs sits the check no partner can run: whether the company was new to SourceX. Any earlier application, lead, account or email correspondence between SourceX and the company makes it a duplicate, and SourceX does not credit a company it already knew.
Four timelines where the click and the company part (Illustrative)
Illustrative: invented companies and dates, set in 2027 under the current terms.
| Timeline | What the click record shows | The entity question | Governing term | Likely result |
|---|---|---|---|---|
| A. A newsletter link draws 140 visits over three weeks; nobody applies | 140 visits | No company ever named itself | Terms, section 2: credit needs a verified application | No attributed company |
| B. A holding company's CFO opens the link on 3 Mar; on 22 Mar its 300-person operating subsidiary applies under its own name and domain, typed directly | One visit, at the parent | Is the applicant the company introduced? | Partner agreement 3.3 and terms, section 2: dated records naming company and domain | Review, with an identity note linking the two entities |
| C. A partner introduces the CEO by email on 8 Feb and submits in the portal; on 1 Mar the CEO's chief of staff applies by typing the site address | No visit at all | None: the introduction named the company | Terms, section 2: dated records decide, a click is not required | Credit can follow from the dated introduction |
| D. A COO opens the link on 12 Apr; the company held a SourceX account from 2026 | One visit | Was the company new to SourceX? | Terms, section 3: an earlier account is a relationship | Not new, so no partner is credited |
Timeline A is the one partners misread most. A newsletter or post can produce real interest, and the association newsletter guide shows how to run one. But a visit count is a marketing number. Timeline C is the reverse: no click and a sound claim, because the dated introduction names the company. Written introduction versus referral link attribution works through how that evidence is weighed.
Keep three numbers apart
A partner operations team that reports one blended "referrals" figure will mislead itself. Track three counts, each with its own definition:
- Link visits. Visits recorded on your link. Useful for testing channels; it counts browsers, not companies, and the marketing attribution guide explains why it decides nothing.
- Companies introduced in writing. Distinct legal entities you introduced to an authorized contact, with a dated record holding company, domain, method and timestamp. Count entities, not emails.
- Companies credited. Companies SourceX attributed to you after a verified application and the duplicate check, visible in your dashboard with reward status shown as Estimated, Eligible, Approved or Paid.
The ratio worth watching is credited companies over companies introduced, not credited companies over visits. SourceX has not published typical ratios between these counts, so measure your own, with dates. Payment is a fourth track again, with its own clock: once the complete, validated dataset has both been handed off and received the Acquisition Partner's final written acceptance, the terms allow 60 calendar days from whichever of those came later, provided the other payment conditions are met. The attribution window explainer covers the timing between counts 2 and 3.
When the company that applied is not the one you introduced
Send SourceX the minimum that lets a reviewer connect the two, by email to hello@sourcex.si, the dispute address in the terms and Schedule A:
- Your introduction, unedited, with its date, recipients and text.
- Your portal submission reference and timestamp.
- A one-paragraph identity note: the name as introduced and as applied, both registered legal names, both domains, the relationship between them (parent and subsidiary, trade name, rename) and a public identifier for each.
Leave out analytics screenshots, which describe browsers, and anything from inside the company. Partners never handle client records, and SourceX's review does not need them to match two names.
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.
Count companies, not clicks: sign the SourceX Channel Partner Agreement before introducing anyone, then register for a partner link, confirm each entity against who qualifies and read the attribution sections of the program terms. The guides hub collects the other attribution cases.