Home
Offers & Tracking
Advanced Tracking Options
Understanding Server-Side Clicks
Understanding Server-Side Clicks

SERIES:

Understanding Server-Side Clicks

Learn how to enable and utilize Everflow's server-side clicks to bypass redirects for faster loading and improved click tracking, particularly crucial with iOS 14+ and SKAdNetwork, while also noting considerations for Offers with multiple redirects.

Overview

Server-side clicks allow users to skip redirects and go directly to your landing page (base destination URL), while click tracking happens behind the scenes. This reduces friction, improves loading speed, and ensures fewer dropped clicks — a key advantage as platforms like iOS shift how they handle attribution.

Heads up With Apple’s iOS 14+ and the use of SKAdNetwork, server-side clicks are the recommended setup. They eliminate redirects, which are no longer supported in many cases.

What Are Server-Side Clicks?

Normally, a click goes through a redirect to track attribution before landing on the destination page. With server-side clicks, the tracking request is triggered separately (in the backend), and the user is sent immediately to the destination URL.

Benefits:
  • Faster page load time for the user
  • Fewer dropped clicks
Heads up Using this feature if your offer includes multiple redirects (common with re-brokered offers), will increase the risk of broken links or tracking issues.

How To Enable Server-Side Clicks

1 Enable It in the Offer Settings Go to Offers → Manage Click on the Offer name Open the Attribution tab Toggle Server-Side Clicks to ON 2 Set the Advertiser's Destination URL In the Attribution tab, input the advertiser’s destination URL and make sure to include any necessary macros. For SKAdNetwork attribution, include: {user_ip} – Passes the user's IP address {user_agent} – Passes the user's device/browser info Replace mmp_ip and mmp_ua with the exact parameter names required by your app/MMP.
3 Set the Final Landing Page In the General tab, set the Default Landing Page — this is the actual page where users should land. Targeting rules and caps do not apply when using server-side clicks.