{"id":169,"count":0,"description":"","link":"https:\/\/tenjin.com\/zh\/glossary\/server-to-server-s2s\/","name":"\u670d\u52a1\u5668\u5230\u670d\u52a1\u5668\uff08S2S\uff09","slug":"server-to-server-s2s","taxonomy":"glossaries","parent":0,"meta":{"status":["1","1"],"order":["0","0"],"glossary_term_description":["
\r\n\r\nDefinition:<\/b>\r\n\r\nS2S (server-to-server) is a communication model where two servers exchange data directly with each other, bypassing the client layer entirely. In mobile marketing, it refers to sending app event data directly from your own servers to a mobile measurement partner like Tenjin, without requiring an attribution SDK embedded in your app.<\/span>\r\n\r\n<\/div>\r\n

<\/h2>\r\n

What is S2S?<\/strong><\/h2>\r\nIn most mobile attribution setups, an SDK lives inside your app and handles the job of capturing and sending event data to your measurement partner. S2S flips that model entirely.<\/span>\r\n\r\nWith server-to-server tracking, your own backend infrastructure takes on that responsibility. When a user installs your app or completes an in-app event, your server captures that data and sends it directly to Tenjin's server via API. No SDK sitting inside your app. No client-side dependencies to manage. Just a clean, direct connection between two backends.<\/span>\r\n\r\nIt is a more technical setup, but for the right teams it offers meaningful advantages in flexibility, control, and data quality.<\/span>\r\n

How S2S Works in Mobile Apps<\/strong><\/h2>\r\nThe S2S flow is straightforward once the infrastructure is in place. Here is what happens when a user interacts with your app:<\/span>\r\n
    \r\n \t
  1. User Action<\/b><\/li>\r\n<\/ol>\r\nA user installs your app or completes a tracked in-app event.<\/span>\r\n
      \r\n \t
    1. Your Server Captures The Event<\/b><\/li>\r\n<\/ol>\r\nYour backend logs the event along with all relevant parameters, such as device information, event type, and timestamp.<\/span>\r\n
        \r\n \t
      1. Direct Server Communication<\/b><\/li>\r\n<\/ol>\r\nYour server sends that event data directly to Tenjin's server via API call, in real time.<\/span>\r\n
          \r\n \t
        1. Attribution Matching<\/b><\/li>\r\n<\/ol>\r\nTenjin's attribution engine receives the event and matches it back to the original ad click or impression that preceded it.<\/span>\r\n
            \r\n \t
          1. Campaign Insights<\/b><\/li>\r\n<\/ol>\r\nThe matched data flows into your Tenjin dashboard, giving you the same campaign performance visibility you would get through a standard SDK integration.<\/span>\r\n\r\nThe result is pure server-to-server communication with no app-level SDK required.<\/span>\r\n

            \u00a0S2S vs. SDK Integration: What Is the Difference?<\/strong><\/h2>\r\nBoth approaches get event data to Tenjin. The difference is in how and where that data is collected and sent.<\/span>\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n
            <\/td>\r\nSDK Integration<\/b><\/td>\r\nS2S Integration<\/b><\/td>\r\n<\/tr>\r\n
            Where data is collected<\/b><\/td>\r\nInside the app, client-side<\/span><\/td>\r\nOn your backend server<\/span><\/td>\r\n<\/tr>\r\n
            What handles the sending<\/b><\/td>\r\nEmbedded attribution SDK<\/span><\/td>\r\nYour own server via API<\/span><\/td>\r\n<\/tr>\r\n
            App code impact<\/b><\/td>\r\nSDK adds weight to the app<\/span><\/td>\r\nNo SDK required in the app<\/span><\/td>\r\n<\/tr>\r\n
            Setup complexity<\/b><\/td>\r\nLower, SDK handles most of it<\/span><\/td>\r\nHigher, requires backend infrastructure<\/span><\/td>\r\n<\/tr>\r\n
            Control over data<\/b><\/td>\r\nSDK manages collection<\/span><\/td>\r\nYou control everything<\/span><\/td>\r\n<\/tr>\r\n
            Speed<\/b><\/td>\r\nStandard<\/span><\/td>\r\nFaster, more direct<\/span><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\nFor teams with strong backend infrastructure and engineering resources, S2S offers a level of control and cleanliness that SDK-based tracking cannot match. For smaller teams or those without dedicated backend resources, a standard SDK integration is typically the more practical starting point.<\/span>\r\n

            Why Choose S2S Tracking?<\/strong><\/h2>\r\n

            Full Control Over Your Data<\/b><\/h4>\r\nWith S2S, your backend handles all event collection and transmission. You own the entire data pipeline, which means you can apply your own validation, enrichment, and formatting before anything reaches Tenjin.<\/span>\r\n

            No SDK Overhead in Your App<\/b><\/h4>\r\nEvery SDK you embed in your app adds weight. S2S removes that dependency entirely, keeping your app lighter and reducing the risk of conflicts between multiple SDKs.<\/span>\r\n

            Faster and More Direct<\/b><\/h4>\r\nServer-to-server communication cuts out the client layer, making data transmission more direct and typically faster than client-side SDK calls.<\/span>\r\n

            Better Suited to Certain App Architectures<\/b><\/h4>\r\nSome app types, particularly those with complex backend logic or server-authoritative architectures, are a natural fit for S2S. If your server already knows about every meaningful user action, sending that data directly to Tenjin is a logical extension of what you are already doing.<\/span>\r\n

            What to Consider Before Moving to S2S<\/strong><\/h2>\r\nS2S is a powerful approach but it is not the right fit for every team. A few things worth evaluating before committing:<\/span>\r\n

            Backend Infrastructure<\/b><\/h4>\r\nS2S requires a reliable, scalable server infrastructure capable of capturing events and making API calls in real time. If that foundation is not already in place, the setup cost is significant.<\/span>\r\n

            Engineering Resources<\/b><\/h4>\r\nUnlike an SDK integration where much of the heavy lifting is handled for you, S2S requires your engineering team to build and maintain the data pipeline. Make sure that capacity exists.<\/span>\r\n

            Measurement Requirements<\/b><\/h4>\r\nConsider what you need to measure and whether S2S covers all of it. Some attribution scenarios, particularly those that rely on client-side signals, may be easier to handle with a hybrid approach.<\/span>\r\n\r\nIf you are considering S2S for your app and want to understand whether it fits your setup, the Tenjin team is happy to help. Reach out at support@tenjin.com<\/a> for documentation and guidance.<\/span>\r\n\r\nPlease note that S2S integration is available on all paid plans.<\/span>\r\n\r\n
            \r\n\r\n

            Related Terms<\/strong><\/h2>\r\n