{"id":1728,"date":"2026-07-12T13:00:00","date_gmt":"2026-07-12T18:00:00","guid":{"rendered":"https:\/\/tolinku.com\/blog\/?p=1728"},"modified":"2026-03-07T03:50:04","modified_gmt":"2026-03-07T08:50:04","slug":"self-attributing-networks","status":"publish","type":"post","link":"https:\/\/tolinku.com\/blog\/self-attributing-networks\/","title":{"rendered":"Self-Attributing Networks: Facebook, Google, and More"},"content":{"rendered":"\n

Self-attributing networks (SANs) are ad platforms that perform their own attribution instead of relying on a third-party attribution provider. Meta (Facebook\/Instagram), Google (Search\/YouTube\/UAC), TikTok, Snapchat, X (Twitter), and Apple Search Ads all self-attribute. This means they decide whether their ads drove an install, and they report that decision to you directly.<\/p>\n\n\n\n

This creates challenges. When two SANs both claim credit for the same install, someone is wrong. This guide explains how SANs work, why they self-attribute, and how to reconcile their data. For attribution models, see last-click vs multi-touch attribution<\/a>. For build-vs-buy decisions, see MMP vs in-house attribution<\/a>.<\/p>\n\n\n\n

How Self-Attributing Networks Work<\/h2>\n\n\n\n

Standard Attribution Flow<\/h3>\n\n\n\n

With a regular ad network:<\/p>\n\n\n\n

    \n
  1. User clicks an ad. The click is redirected through the attribution provider's tracking URL.<\/li>\n
  2. User installs the app.<\/li>\n
  3. Attribution provider receives the install event from its SDK.<\/li>\n
  4. Attribution provider matches the install to the click.<\/li>\n
  5. Attribution provider assigns credit to the ad network.<\/li>\n<\/ol>\n\n\n\n

    The attribution provider controls the data and the decision.<\/p>\n\n\n\n

    SAN Attribution Flow<\/h3>\n\n\n\n

    With a self-attributing network:<\/p>\n\n\n\n

      \n
    1. User clicks an ad within the SAN's platform (e.g., a Facebook ad).<\/li>\n
    2. The click is NOT redirected through a tracking URL. Facebook tracks it internally.<\/li>\n
    3. User installs the app.<\/li>\n
    4. Attribution provider's SDK sends the install event to the attribution provider AND to Facebook's SDK.<\/li>\n
    5. Facebook checks its own click\/impression data and claims the install if it finds a match.<\/li>\n
    6. The attribution provider receives Facebook's claim and must decide whether to accept it.<\/li>\n<\/ol>\n\n\n\n

      The SAN controls its own click\/impression data and makes its own attribution decision.<\/p>\n\n\n\n

      Major Self-Attributing Networks<\/h2>\n\n\n\n
      \n\n\n\n\n\n\n\n\n\n
      Network<\/th>\nPlatforms<\/th>\nClaim Method<\/th>\n<\/tr>\n<\/thead>\n
      Meta (Facebook, Instagram)<\/td>\nFacebook, Instagram, Audience Network, Messenger<\/td>\nServer-side claim via API<\/td>\n<\/tr>\n
      Google Ads<\/td>\nSearch, YouTube, Display, UAC<\/td>\nServer-side claim via API<\/td>\n<\/tr>\n
      TikTok<\/td>\nTikTok, Pangle<\/td>\nServer-side claim via API<\/td>\n<\/tr>\n
      Snapchat<\/td>\nSnapchat<\/td>\nServer-side claim via API<\/td>\n<\/tr>\n
      Apple Search Ads<\/td>\nApp Store search<\/td>\nAdServices framework<\/a> (iOS 14.3+)<\/td>\n<\/tr>\n
      X (Twitter)<\/td>\nX\/Twitter<\/td>\nServer-side claim via API<\/td>\n<\/tr>\n
      Pinterest<\/td>\nPinterest<\/td>\nServer-side claim via API<\/td>\n<\/tr>\n<\/tbody><\/table><\/figure>\n\n\n\n

      Each SAN has its own API, its own attribution logic, and its own reporting format.<\/p>\n\n\n\n

      The Double-Counting Problem<\/h2>\n\n\n\n

      When a user sees a Meta ad, clicks a Google ad, and installs the app:<\/p>\n\n\n\n