A1
Referral token
A stable code used to attribute completed storefront purchases back to your partner record.
This page now follows the same editorial shell as the storefront because partners should feel like they are extending the same offer system, not landing on a separate campaign. The current lead offer is the SEO Audit Report: easy to explain, low-friction to buy, and naturally connected to implementation and recurring support.
The workflow is intentionally narrow. You apply once, the system returns your referral token, and every hero-offer sale tied to that token can be inspected through the matching partner summary view.
A stable code used to attribute completed storefront purchases back to your partner record.
A ready-to-use hero-offer URL that points prospects at the same storefront experience everyone else sees.
A summary endpoint meant for reviewing views, completed orders, cash collected, and pending commission state.
The response includes ready-to-send outreach text so the partner does not need to write the initial pitch from scratch.
The partner page should reinforce the same commercial story the storefront already tells. This is not a different product. It is the exact same entry engagement packaged for third-party traffic.
If your record already exists, the system will return the existing token and summary path instead of creating a duplicate.
This works best when you frame the audit as a fast way to surface revenue leaks before a buyer spends more on traffic, content, or implementation.
Lead with the promise: a teardown of the page closest to revenue, tied to prioritized fixes and next moves.
The referral experience should inherit the same design, pricing, trust cues, and follow-on offers already live on the site.
Use the returned summary path to inspect partner-attributed demand and pending commission state without manual reconciliation.
Do not create a custom partner funnel for every audience. The point is to prove one loop works end to end.