Partner program and EdgeVisor referral attribution
EdgeVisor connects editorial context to a decision surface. Partners can use embeds, deep links, and brand-safe CTAs.
This page describes who can send traffic, where links may go (EdgeVisor, Preddy, or your own execution layer),
and how EdgeVisor’s own attribution relates to platform-native programs such as
Polymarket’s referral program
— they are not the same contract.
Polymarket vs EdgeVisor.
Polymarket runs a separate referral scheme for activity on their product.
EdgeVisor may track visits, signups, and qualifying actions that start on EdgeVisor-tagged partner links for our rewards and analytics.
A user can be in both systems, neither, or one only — the rules and payouts are defined separately.
Who can participate
Prediction-market newsletters and Substacks
Crypto, macro, and politics publishers
Research communities and curated groups
Sites building an EMD or topical ring around EdgeVisor
Affiliates who respect disclosure and honest framing (no guaranteed returns)
Where traffic may go
EdgeVisor — /, /tool, /docs, /dashboard, calculators, and embed hosts
Preddy.trade — when the CTA is explicitly a partner execution path we document for a given campaign
Your properties — landing pages, paid communities, or broker-style flows you own (we do not control those accounts)
Polymarket — via outbound links from cards or user clicks; Polymarket’s own referral terms apply on their side
Our accounts vs yours
When the destination is “ours”: the reader uses EdgeVisor-hosted flows (signup, dashboard, billing, tagged deep links).
Attribution and rewards, when offered, are tied to EdgeVisor identity and qualifying actions we define in the partner agreement.
When the destination is “yours”: you may send readers to wallets, communities, or execution surfaces you operate.
EdgeVisor does not custody funds on your behalf and cannot see trades inside accounts we do not integrate with.
Partner reporting in that mode is limited to upstream funnel events we can observe (e.g. embed impressions and outbound clicks from our widgets).
CTAs, widgets, and links
Embeddable cards — iframe or script-based snippets; include partner key when we issue one
Deep links — URL parameters or path prefixes we document for a campaign (e.g. ?ref= / dedicated partner slugs)
Text CTAs — “Open in dashboard”, “Read the pick”, “Try the fair-value tool” pointing to EdgeVisor
Co-branded assets — by arrangement only; must not imply guaranteed edge or licensed advisory
Exact parameter names and allowed domains are shared when a partner slot is approved — do not invent tracking tokens.
What we track and how rewards work
EdgeVisor’s own attribution stack is designed for a simple lifecycle:
Click or view on a partner-tagged surface (embed impression, referral link)
Anonymous visit with first-party cookie or session correlation where allowed
Signup or login linked to the same visitor when technically possible
First qualifying action (e.g. paid conversion or usage milestone — defined per program)
Reward state: pending, approved, or denied under fraud and policy checks
Card-level card_impressions / card_clicks capture embed funnel health; referral lifecycle events use separate tables
so partner reporting stays auditable. Not every program pays on every step — terms are explicit in the agreement.
Operating rule
The bottleneck is trust. Partner surfaces should explain context and route readers to the correct next step.
EdgeVisor is where the structured workflow lives; EMD and topical sites stay informative and differentiated without over-claiming execution outcomes.