Implementing S2S Tracking: A No-SDK Guide

This guide explains how to implement Tenjin without using an SDK. This method works by sending server-to-server (S2S) events to Tenjin, so that Tenjin can attribute , and retrieve results by using DataVault, LiveOps Campaigns, or S2S Callbacks.

 Pre-requisites #

• You must have their own backend server setup to collect device identifiers and event data from their apps.
  
• The server must be able to make HTTPS requests to Tenjin’s event ingestion endpoints.
  
• You should generate and persist their own UUID (32-character string) to be used as the analytics_installation_id (AIID).
  

1. Start Sending Events to Tenjin #

• Install and Custom Events
  • https://track.tenjin.com/v0/event
  • The required parameters to be sent are marked in (*) in this guide here. 
• Purchase
  • https://track.tenjin.com/v0/purchase
  • The required parameters to be sent are marked in (*) in this guide here.

⚠️ Important:

• Use the same analytics_installation_id (UUID) for all subsequent events from the same user (installs, custom events, purchases, etc.).
  

2. Attribution in Tenjin via S2S #

Tenjin performs Attribution on incoming S2S events using two main methods. This method is similar to how it works t using the SDK method:

Deterministic Attribution #

• Uses device identifiers such as IDFA (if ATT consented), GAID, or Install referrer.
  
• Tenjin will perform deterministic Attribution based on the installs we receive via S2S using the advertising_id parameter for opt-in users.

Probabilistic Attribution #

• Used when IDFA/GAID is not available (e.g., iOS without ATT consent).
  
• Tenjin will perform probabilistic Attribution based on the installs we receive via S2S using the ip_address parameter for opt-out users.

3. Receive Attribution Data  #

Once events are ingested and Attribution is performed, customers can access results through:

• Raw Data Export:
  
  • Raw attributed event-level data available for export from the dashboard.
    
• LiveOps Method:
  
  • User-level Attribution info on the client side using the Tenjin SDK.
    
• S2S Callbacks:
  
  • Tenjin can send postbacks to your server endpoints when Attribution occurs.
    
  • Postbacks include campaign, channel, Ad Network, and Install details.
    

Note: If you would also like to receive raw clicks and impression data to your servers, please contact support@tenjin.com.