Existing referrals come first
When HonorCart recognizes an eligible affiliate referral, it marks the session protected before any monetized action can occur.
Public standard · Version 1.0
How HonorCart handles attribution.
This is the operating policy we expect shoppers, creators, merchants, and networks to hold us to.
HonorCart stands down
A protected session cannot activate or overwrite attribution for HonorCart. If safe coupon testing is uncertain, the extension does nothing.
Controls live on the server
Global, network, and merchant kill switches can disable monetization without waiting for an extension release. A local fail-safe defaults to standing down.
Creators see defensible counts
A protected-referral count means HonorCart recognized a registered identifier and did not monetize that session. It does not prove a later sale or commission.
Money is qualified
Checkout value is displayed only when observable. Potential commission uses a disclosed rate assumption and is labeled estimated unless a network confirms the conversion.
Changes leave a record
Material policy and methodology changes are dated in Updates. The active ruleset version is attached to future events.
Decision order
Protection is the default path.
- Check global and merchant kill switches
- Look for supported referral signals
- Match a registered creator identifier
- Lock the session as protected
- Allow only non-attributing coupon behavior
- Record a privacy-minimized protection event
What we cannot claim
Standing down is not the same as confirming a commission.
HonorCart generally cannot see whether the shopper completed a purchase, whether the network credited it, whether a return occurred, or what the creator ultimately earned.
That is why the dashboard distinguishes protected referrals, observed checkout value, estimated potential commission, and network-confirmed outcomes.
View policy updates →