The trouble starts in a partner team's weekly report. A campaign dashboard shows "conversions", someone adds them to the pipeline line, and a bonus is promised on them. None of those conversions is a contract event. Some belong to companies another partner introduced first, some to companies SourceX already knew, and the one that counts may never appear in a campaign report at all because it began with an email to a CEO.
What a campaign tag is built to do
A campaign tag is a label added to a link so analytics can group the visits it produces. Google's Analytics documentation says adding utm parameters to destination links lets you see which campaigns refer traffic, and that utm_source, utm_medium and utm_campaign should always be included. Two details from the same guide matter here: values are case sensitive, so "Newsletter" and "newsletter" become two sources, and a missing parameter shows up as "(not set)". Tags are good at one thing, comparing channels, and fragile in ways that never touch a contract.
Analytics credit is also a setting, not a fact. In Google Analytics, the lookback window for acquisition events defaults to 30 days and for other key events to 90, with shorter options, and changing the reporting attribution model applies to historical and future data. One click in a settings menu can move last quarter's credit from a newsletter to a webinar. Nothing comparable can happen to a dated introduction: the partner agreement says a website update, dashboard edit or unanswered message does not amend it.
Both systems may say "90 days" and still mean different things. The analytics window looks back from a conversion to earlier touches. SourceX's window runs forward from the recorded introduction: the company must submit a verified application within 90 days of it. The attribution window explainer covers that clock on its own.
The analytics-versus-contract attribution table
Three records exist when a tagged link brings a company to SourceX, and each answers a different question.
| Property | Your campaign data | Analytics on SourceX's site | The contract record |
|---|---|---|---|
| What it records | Clicks on links you sent, by tag, in your email and social tools | Pages viewed and first and latest marketing touches, kept separate from referral credit | Your written introduction, its portal submission and the company's verified application |
| Who controls it | You | SourceX | Dated records SourceX weighs under the terms |
| Can it change later | Yes: models, filters and settings can rewrite past credit | SourceX's internal choice | No: edits and unanswered messages do not amend the agreement |
| Its window | Whatever your tool's lookback is set to | Not a credit window | 90 days forward from the recorded introduction to a verified application |
| Needs visitor consent | Depends on your own tools and obligations | Yes: analytics only after the visitor accepts, and off under Global Privacy Control | No: your introduction email exists either way |
| What it identifies | A browser or a click | A browser | A company and its domain |
| What breaks it | Case mismatches, missing tags, browser privacy features | Declined consent, cleared storage | Missing dates or an undocumented introduction |
| Decides a reward | No | No | It is the evidence SourceX weighs |
| Best used for | Choosing which channels and messages to keep | SourceX's own site decisions | Credit, duplicates and disputes |
Method note. The table compares three record types using Google's Analytics documentation, SourceX's cookie policy, the program terms (Version 2026-10-22.2, since replaced by version 2026-11-04) and the unsigned Channel Partner Agreement sample, all checked 2026-10-26. It describes what each record can show, not how often they disagree; SourceX has not published how many applications arrive tagged, untagged or through a different campaign than the one that introduced the company.
The middle column is the easiest to misread. The tags on a link to SourceX are read, if at all, by SourceX's own analytics, which run only with the visitor's consent and which SourceX records separately from referral credit. Your partner dashboard shows something else: each referral's stage and its reward status, from Estimated to Paid, with Paid shown only after an actual payout is recorded.
Rebuild one company's timeline from both ledgers (Illustrative)
Fictional partner, company, tags and dates. The partner is a 14-person IT services firm; the company is a 240-person regional engineering firm.
| Date | Event | Analytics ledger | Contract ledger |
|---|---|---|---|
| 2026-09-08 | The company's COO clicks a tagged link in the partner's newsletter (source newsletter, medium email, campaign sept-ops-briefing) | One click on the newsletter link | Nothing |
| 2026-09-15 | After a call in which the CEO agreed, the account lead emails her a written introduction and submits it in the portal the same day | Nothing: a one-to-one email carries no campaign | Dated introduction and portal submission naming the company, its domain, the method and the time |
| 2026-10-01 | The CEO attends the partner's webinar and clicks its tagged link (campaign oct-webinar) | A second click; a last-click view now credits the webinar | Nothing |
| 2026-10-06 | The CEO applies at /apply after typing the address | No click at all | Verified application on day 21 of 90; SourceX checks its own records for any earlier relationship |
The analytics ledger tells a story about two campaigns. The contract ledger tells the one that counts: an introduction on 15 September and an application 21 days later. If the partner's team had split a bonus between the newsletter and the webinar owners, it would have rewarded the two events the terms ignore.
Three campaign timelines and the term that settles each (Illustrative)
A. Campaigns everywhere, one introduction. The timeline above. The governing term is section 2 of the terms: the first valid introduction of a new company is credited when the company submits a verified application within the window. Neither campaign tag enters that decision.
B. A tagged click and an earlier introduction by someone else. A CFO clicks the partner's LinkedIn post on 3 September and applies through the tagged link on 12 September. Another partner emailed the company's CEO a written introduction on 28 August. The partner's campaign report shows a clean conversion; the decision belongs to duplicate review, which weighs dated records, and a link click alone does not decide credit. The written introduction vs link evidence timeline shows how that weighing reads.
C. A company SourceX already knew. A webinar attendee's company applies through the tagged link, but it had emailed SourceX in July. Under section 3, any earlier lead, account or email correspondence with SourceX is a relationship, and a company SourceX already knew is not credited to a later partner. The campaign still worked as marketing; it simply has no contract consequence.
Rules that keep the two ledgers apart
- Store them separately. Campaign data lives in your marketing tools. The contract ledger is a plain log with the fields the agreement asks every introduction record to carry: company, domain, partner, opportunity, introduction method and timestamps, plus the portal submission date.
- Join them by company, monthly, in one direction. Use the contract ledger to ask which channels found the companies you introduced. Never copy a campaign conversion into the contract ledger.
- Name tags consistently. Lowercase, one spelling per channel, and always source, medium and campaign, since values are case sensitive.
- Describe campaigns, never people. A tag value should never carry a company or a person's name. Links get forwarded, and Safari already strips some parameters that look like individual tracking: WebKit says Safari's Private Browsing removes parameters used for cross-site or user-level click tracking before navigation, while letting campaign-attribution parameters through.
- Test before you send. Open the tagged link in a fresh browser and confirm it lands where your untagged link does; if it does not, send the untagged link and keep the campaign label in your own send log.
- Report the two ledgers on different lines. Campaign clicks go under marketing; recorded introductions and dashboard status go under referrals; nothing from the first line is ever described as a reward.
Where SourceX's own analytics fit into this is covered in separating marketing attribution from contractual referral credit, and the link's own event trail in the referral link journey.
The minimum evidence when credit is questioned
Email hello@sourcex.si, as section 7 of the terms describes, with the referral details and four items:
- The company's legal name and domain, and the name and role of the CEO you introduced.
- Your written introduction, unedited, with its date, recipients and text.
- The date of the matching portal submission.
- Optionally, the date and channel on which you sent a tagged link, as context only.
Leave out analytics exports, screenshots of campaign dashboards and anything visitor-level: they cannot decide credit, and they may contain other people's data. Partners never receive other partners' records, and a review does not need them. The event-to-entity attribution map explains why a click never names a company in the first place.
Limits of the split
- You cannot see SourceX's analytics. They are consent-based and kept for SourceX's own purposes.
- Signed terms can differ. A signed Schedule A or addendum can change the reward terms that apply to you.
- Browser behavior shifts. Which parameters survive a click depends on browsers and settings outside your control.
- No published rates. How often campaign data and contract records point to different companies or partners has not been published; log your own.
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.
Before your next tagged campaign goes out, set up the contract ledger and send each warm company a dated written introduction: register for a partner link, check each company against who qualifies and read sections 2 and 3 of the program terms; more attribution cases are in guides.