Mantle Migration Attribution Checklist

Migrating an affiliate program is where attribution quietly breaks if you are not careful. The two things that matter most are that your partners' existing links keep working, and that revenue from migrated stores still ties back to the right affiliate. Get those right and the move is invisible to partners.

Keep existing links working

Your partners have already shared links with their audiences, and those links carry their original code. The migration has to preserve each partner's original referral code exactly, so a link they posted a year ago still resolves to them. If a migration reassigns codes, every previously shared link breaks silently. Preserve the code, and the old links keep attributing.

Carry the code through the install

A migrated link only attributes if the code survives into the install. The reliable setup is the same as for any app: the tracked link carries the code, and either your install flow forwards it or the click cookie is read at install. Whether the code arrives as ref, mref, or utm_source, it should resolve to the same partner. Confirm this works on a test install before you tell partners the move is done.

Do not lose the store identifier

The most common migration failure is imported referrals that have no store identifier. Without the store's myshopify domain on each referral, revenue coming from the Partner API has nothing to attach to, and the partner's earnings read as zero even though the install is there. The store identifier usually lives in the customers export, so that file has to be joined in during migration, not skipped.

Verify before you announce

• •Spot-check several migrated partners: their code, their links, and at least one attributed store with revenue.
• •Run a test install through a migrated link and confirm it attributes exactly.
• •Confirm revenue is flowing from the Partner API onto migrated referrals, not sitting unattributed.