How to keep campaign tags separate from reward attribution: a two-ledger table for partners who put UTM tags on their SourceX link

Short answer

Treat campaign tags as your own marketing measurement, and the dated introduction as the only record that matters for a reward. UTM parameters show which newsletter, post or webinar carried a visitor to SourceX; credit for a company is decided from dated records, including written introduction evidence, existing applications and preexisting relationships, and an earlier link click alone does not decide it. Keep two ledgers: an analytics ledger you may tag, remodel and reorganize, and a contract ledger of dated introductions you never edit.

Visual briefFull-size diagram
Two ledgers side by side: the analytics ledger lists tagged clicks whose credit moves from newsletter to webinar when the model changes, while the locked contract ledger holds the dated introduction of 15 September and the verified application on day 21 of 90.
Illustrative campaign timeline from this page. Tags and dates are fictional; the 90-day window is from the program terms.

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.

PropertyYour campaign dataAnalytics on SourceX's siteThe contract record
What it recordsClicks on links you sent, by tag, in your email and social toolsPages viewed and first and latest marketing touches, kept separate from referral creditYour written introduction, its portal submission and the company's verified application
Who controls itYouSourceXDated records SourceX weighs under the terms
Can it change laterYes: models, filters and settings can rewrite past creditSourceX's internal choiceNo: edits and unanswered messages do not amend the agreement
Its windowWhatever your tool's lookback is set toNot a credit window90 days forward from the recorded introduction to a verified application
Needs visitor consentDepends on your own tools and obligationsYes: analytics only after the visitor accepts, and off under Global Privacy ControlNo: your introduction email exists either way
What it identifiesA browser or a clickA browserA company and its domain
What breaks itCase mismatches, missing tags, browser privacy featuresDeclined consent, cleared storageMissing dates or an undocumented introduction
Decides a rewardNoNoIt is the evidence SourceX weighs
Best used forChoosing which channels and messages to keepSourceX's own site decisionsCredit, 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.

DateEventAnalytics ledgerContract ledger
2026-09-08The 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 linkNothing
2026-09-15After a call in which the CEO agreed, the account lead emails her a written introduction and submits it in the portal the same dayNothing: a one-to-one email carries no campaignDated introduction and portal submission naming the company, its domain, the method and the time
2026-10-01The CEO attends the partner's webinar and clicks its tagged link (campaign oct-webinar)A second click; a last-click view now credits the webinarNothing
2026-10-06The CEO applies at /apply after typing the addressNo click at allVerified 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

  1. 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.
  2. 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.
  3. Name tags consistently. Lowercase, one spelling per channel, and always source, medium and campaign, since values are case sensitive.
  4. 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.
  5. 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.
  6. 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:

  1. The company's legal name and domain, and the name and role of the CEO you introduced.
  2. Your written introduction, unedited, with its date, recipients and text.
  3. The date of the matching portal submission.
  4. 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.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Will adding UTM tags to my SourceX link change who gets credit for a company?

No. Credit is decided from dated records, including written introduction evidence, existing applications and preexisting relationships, and a link click alone does not decide it. Tags only describe which of your campaigns carried the click.

Can I see which of my campaigns led to an application?

Only partly. Your own email and social tools count clicks on the links you sent. Analytics on SourceX's site run only with the visitor's consent and belong to SourceX, recorded separately from referral credit. Your partner dashboard shows each referral's stage and reward status instead.

Should we pay our team bonuses on campaign conversions?

Not if the bonus is meant to follow the referral program. A campaign conversion can belong to a company another partner introduced first, or one SourceX already knew. Tie internal credit to dated introductions in the contract ledger, and treat campaign data as a guide to which channels to keep.

Sources

  1. refer.sourcex.si/terms
  2. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  3. refer.sourcex.si/cookie-policy
  4. refer.sourcex.si/how-it-works
  5. support.google.com/analytics/answer/10917952
  6. support.google.com/analytics/answer/10597962
  7. webkit.org/blog/15697/private-browsing-2-0

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment