If you have ever compared your affiliate dashboard to your actual mobile sales and found the numbers do not match, this is usually why: cookies, the thing most tracking quietly depends on, work worse on mobile than almost anywhere else. Safari and Firefox block third-party cookies by default, in-app browsers frequently strip them entirely, and a visitor who researches on their phone and buys later on a laptop breaks a cookie-based chain even when everything technically “worked.”
This guide walks through setting up tracking that does not have that weak point, using Post Affiliate Pro’s server-to-server (S2S) tracking, and is honest about the one thing it will not do for you. It assumes you are running the program rather than promoting as an affiliate, if you are on the affiliate side wondering whether mobile is even worth your time, our mobile affiliate marketing guide is the better starting point.
What mobile tracking actually needs to survive
A mobile-friendly tracking setup needs to survive three things a desktop-only setup rarely has to deal with: a browser that blocks third-party cookies outright, an app that opens content in its own in-app browser rather than a normal one, and a customer journey that jumps between a phone and a different device before it ends in a sale. Cookie tracking alone survives none of these reliably. That is the specific gap S2S tracking closes.
Step 1: Turn on server-to-server tracking
In Post Affiliate Pro, S2S tracking works by generating a unique identifier the moment someone clicks an affiliate link, rather than storing that identifier in a cookie on their device. Your own server holds onto that ID, and Post Affiliate Pro’s tracking server never needs the visitor’s browser to remember anything at all (S2S tracking ). This is the same mechanism that makes the method work even inside an app’s built-in browser, since there is no cookie to lose in the first place.
Launch your affiliate program today
Set up advanced tracking in minutes. No credit card required.
Step 2: Set up your callback URL
The other half of S2S tracking is telling Post Affiliate Pro when a conversion actually happens. You define a Callback URL in the merchant panel, and Post Affiliate Pro calls it after every recorded transaction (tracking methods ). In practice, that means your server, the one that already knows a purchase, signup, or install just happened, sends that unique ID back to Post Affiliate Pro at the moment of conversion, closing the loop without ever touching the browser.
Step 3: Decide what counts as a conversion
Not every mobile campaign is selling something directly. Post Affiliate Pro’s action commissions let you define the commissionable event yourself, a sale, a signup, a completed form, or a download, rather than being locked into “purchase” as the only option (action commissions ). This is configured per campaign under Campaigns, then Campaign Manager, then Edit Campaign, in the commission settings. If your mobile offer pays out for something other than a sale, for example a free trial signup from an app landing page, this is where you define that.
This is also the piece that matters most if you are running the kind of mobile-specific offers covered in our mobile affiliate marketing guide , app install offers and pay-per-action promotions rather than straightforward sales. An install is not a sale, so it needs to be defined as its own action here rather than forced into a sale-shaped commission rule, or it will simply never trigger a payout no matter how well the S2S tracking itself is working.
Join our newsletter
Be the first to know about new features and product updates.
Step 4: Have a fallback for when even S2S can’t get an ID through
S2S handles the common case, but Post Affiliate Pro also supports a fallback chain for edge cases: HTML5 local storage, then IP address matching, then IP plus user agent matching, in roughly that order of reliability (tracking methods ). You will not need to configure this yourself in most setups, but knowing it exists explains why a small number of conversions still get attributed correctly even when the primary method has nothing to work with.
Step 5: Test the whole path before you send real traffic
Click an affiliate link from an actual phone, on both Wi-Fi and mobile data, and complete a real conversion the way a customer would. Confirm the click registers, then confirm the conversion shows up against the correct affiliate once your server calls the callback URL. This catches the two most common setup mistakes: a callback that fires before your server actually has the information it needs, and a mobile landing page that redirects in a way that drops the tracking parameter before the click is even recorded.
Migrating an existing program instead of starting fresh
If you already have a program running on cookie tracking and are switching to S2S rather than setting up mobile tracking from zero, do it as a parallel run rather than a hard cutover. Turn on S2S alongside your existing cookie tracking for a couple of weeks, and compare the two side by side rather than immediately trusting the new numbers. A brand-new tracking method that suddenly shows more mobile conversions than before is a sign it is working, not a bug, but you want to see that trend before you switch affiliates over to reporting from the new numbers, so nobody’s dashboard changes overnight without an explanation. Once the two methods agree closely enough that you trust the gap is explained by what cookie tracking was missing, you can retire the cookie-only setup for mobile traffic specifically and keep it for desktop if it is still serving you there.
A note on privacy compliance
Cookieless tracking has a second advantage worth knowing about beyond solving the mobile cookie problem: it sidesteps a fair amount of the cookie-consent complexity that GDPR and similar regulations introduced, since there is no cookie being set on the visitor’s device in the first place. That does not mean privacy compliance disappears entirely, you are still processing personal data and need a lawful basis for doing so, but it does remove one specific, common compliance headache. Our breakdown of GDPR compliance and cookieless tracking covers this in more depth if privacy compliance is a live concern for your program.
What this setup does not cover
Being direct about the limits here matters more than it might seem. Server-to-server tracking solves the cookie problem, but it does not give you app-store-level deep link attribution on its own, the kind of thing that tells you a specific install came from a specific ad creative inside the App Store or Play Store’s own attribution system. If that level of detail matters for your program, for example you are running paid app-install campaigns across several ad networks and need to reconcile them against store-level data, you will likely still want a dedicated mobile measurement partner alongside your affiliate tracking, not instead of it. For most affiliate-driven mobile traffic, sales, signups, and app opens that convert to a tracked action, S2S tracking is enough on its own.
Where this fits into your broader mobile strategy
Getting the tracking right is the foundation, not the finish line. If your mobile conversion numbers are already accurate but still lower than you would like, the more likely culprit is somewhere else in the funnel, a slow mobile landing page, a checkout that was never tested on a phone, or affiliates sending links that were never actually opened on the device type they were built for. Our breakdown of why mobile affiliate traffic doesn’t convert goes through the rest of that list once tracking itself is no longer the question.
