Main Documentation Tracking S2S tracking

S2S tracking

Important project data may be left outside of the digital space. If your statistics are only based on app and website events, you miss offline data such as services activated at sales offices, registrations for a test drive, product delivery, etc.

MyTracker allows you to upload any project details via the S2S API.

How it works

Data is transmitted via an HTTPS protocol. Each API request should include a device or user ID along with the event. This could be a special S2S ID instanceId and lvid, user identifier customUserId or device id gaid, androidId, idfa, iosVendorId. MyTracker needs only one of the listed identifiers to synchronize information and update your project stats.

Where to start

  1. Get S2S identifiers for iOS, Android, Unity, and Web. SDK automatically generates IDs to link uploaded data to the MyTracker base.
  2. If you cannot gather S2S device ID, use the following instead:
    • User IDs customUserId. In this case, S2S data will form stats only on project users, but not on devices. You can fix it for Android and iOS platforms by providing at least one of the following device IDs.
    • Mobile device IDs: gaid and androidId for Android projects, idfa and iosVendorId for iOS.
  3. Request access to the S2S API:
    • In MyTracker, open the account, for which you want to upload data.
    • Press the Create key button in the S2S API key line. You will see the access key in the same line.
  4. Send HTTPS request to upload data to MyTracker. Each request should have an S2S API key, app ID idApp, and device or user ID.
  5. To send HTTPS requests use PHP SDK. This open-source library facilitates S2S API integration.
    Alternatively, add a mytracker/s2s-api library as a dependency, if you use Composer.

S2S data

Using the S2S API, you can upload data on custom events such as offline orders, visits to sales offices, etc. You can provide the following parameters together with the event name:

  • event time;
  • device information (connection type, Bluetooth state);
  • user information (ID, gender, age);
  • mobile app parameters (ad ID, tracking permission);
  • web app parameters (ad blocker, user-agent).

We are currently working to enhance the API capability, with new methods for uploading historical data, payments, and more coming soon.