Your creator made the sale. Then Safari deleted the proof.
An affiliate link is a tap from social onto a URL with a query string, the exact shape Safari caps at 24 hours. So the thirty days your program promises is really one. And the page that tap lands on has never heard of the creator who sent it.
We are looking for Shopify brands running an affiliate or creator program, to build this with.
"My skin finally calmed down and I stopped switching."
Illustrative creator and store.
Your affiliate app keeps the program. GemBoss takes the click.
We are not building an affiliate platform. Whatever you run, UpPromote, Refersion, Social Snowball or your own, keeps your creators, commission rules, payouts and tax forms. GemBoss takes the stretch from the tap to the order, which nobody currently owns.
Your affiliate app
The people, the terms and the money. None of it moves.
- Recruiting, approval and tiers
- Commission rules and payouts
- Fraud rules, statements and tax forms
GemBoss
The page that tap lands on, and everything it has to remember.
- A referral written by the server, not by a script
- A page that carries the creator who sent it
- Credit stamped onto the Shopify order
Three ways a creator's sale stops being theirs.
- The window closes early. Safari caps cookies written by script at seven days, and a tapped link with a query string from social at one. Your dashboard still says thirty.
- The page never mentions her. The shopper came for a person and lands on the page everyone gets.
- A stranger finds the code. Scraped from one post, typed at checkout, credited there.
Two of the three are documented browser behaviour. The third you can count on your own orders.
Drawn to scale. Caps as Apple documents them for Safari.
Two fixes everybody tries. Neither one holds.
Give every creator a discount code
The code is the part that leaks. It gets scraped off one post, published on a deal site and typed by strangers who were never referred. Where a code at checkout counts as the attribution, it can take credit for a sale another creator made.
Raise the cookie window in the app
The app cannot raise it. The browser applies the cap to cookies written by script, whatever your settings say, so the setting keeps saying thirty while the cookie keeps lasting one. Nothing reports the difference.
Keep the window open from the server that serves the page.
GemBoss already serves your storefront. So the referral is decided on the server before the page paints, in a genuine first-party context, and the same system draws the page, which is why the creator can be on it.
Illustrative store.
Four things move. Your app, your commissions and your checkout do not.
Your program keeps paying exactly who it paid before. GemBoss takes the stretch between the tap and the order.
Resolved on the server
The referral is written in a real first-party context, not by a script the browser already distrusts.
The creator is on it
Her sentence about the product, the things she actually uses, her picture if she approved it.
Applied by the link
No code to copy means nothing for an extension to find and nothing for a deal site to publish.
Revenue per creator
On the same funnel board as your ads and email. Which creators sell, not which creators post.
A creator's face is a permission, not a template slot.
These pages are easy to build badly: scrape the avatar, drop in the logo. We will not.
Nothing publishes on a guess
A page only shows creator assets that reached approved. Anything else falls back to your wordmark.
The same rule already runs here
A generated logo of yours already waits for a person's yes. A creator's mark gets stricter rules.
A face is not a stock photo
Every photo carries a date and a source. When a creator leaves, their face leaves that day.
What is shipped, and what is not Early access
All four parts are built and tested on test data. None of it is live on a store yet, and the missing step is a real program with real orders.
The problem is already real. Safari's cookie caps are documented by Apple, and the code leak shows up in your own orders.
Read the details
Built: the link resolved on the server, the page that carries the creator, the offer applied by the link, and revenue per creator on the board.
One thing it does not do: the discount code still exists inside Shopify. A merchant who emails it to a list has published it themselves.
To count the leak, pull the last ninety days of orders. Look for ones credited to a code that reached someone the creator never referred.
Bring us a program with creators who actually sell.
We will go through your last ninety days with you: orders credited on a code instead of a link, and Safari sales that landed outside a window that was never really thirty days. If it is neither, we will say so.