SERVER TO SERVER INTEGRATION GUIDE


Quadrant offers an alternative method (for mobile applications) to share location data via a S2S (Server-to-Server) integration. This integration (option) utilizes the publisher’s established server-side infrastructure to exchange location data signals and events. This guide details the steps for successful S2S integration.

JUMP TO SECTION

STEP 1 - GETTING STARTED

STEP 2 - DATA PREPARATION

STEP 3 - SERVER INTEGRATION

STEP 4 - DATA FEED

CONTACT A MONETIZATION EXPERT


STEP 1 - GETTING STARTED

To get started please communicate with your account manager to assess the feasibility of the integration. 

Download and submit this attribute questionnaire form. Quadrant will review and accept the feasibility of Server to Server integration. Please note that Quadrant does not accept any data via websites/mobile website scraping, bidstream, or Ad SDKs.

Please adhere to the following guidelines strictly.

STEP 2 - DATA PREPARATION

CSV Headers and Schema

The first line must contain the header. You must include all mandatory fields as well as any additional fields you can find in the addendum at the bottom of this document.

Click here to download a sample file.

Data Encoding

If there is no data for a given field on a given record please leave it empty, i.e. no space between the commas (,,).

Data Type and Sample

Data Field

Data Type

Sample

Description

MAID – Device ID

String

8d1437b1-0e2c-462b-a4e8- 41bf581beb5a

Unique advertising identifier from the device (un-hashed)

User Consent – option 1

String

 

IAB TCF v2

User Consent – option 2

String

 

IAB CCPA

User Consent – option 3

String

 

Toggle (0/1) plus consent screen shots by Publisher ID

Connection Type

String

GPS or WIFI

Wi-Fi, LTE, etc.

ID Type

String

ADID

Advertising ID type: IDFA (iOS) and ADID (Android)

Latitude

Double

18.864864

Latitude of the event

Longitude

Double

76.39176

Longitude of the event

Horizontal Accuracy

Double

19.45

GPS accuracy in meters as reported by the device OS

Vertical Accuracy

Double

10.67

GPS accuracy in meters as reported by the device OS

Altitude

Double

35.4

Altitude in meters as reported by the device OS

Bearing or Heading

String

178.64798

Decimal degrees from north, clockwise 0 to 360 degrees

Speed

Double

0.19

Speed of movement as reported in meters/second

Timestamp

long

1564623910000

Unix timestamp of the event (milliseconds) since “the epoch”

IP Address

String

157.33.161.132

IP address of the event generated from the device

IP v4

String

116.206.9.28

IPv4 Address

IP v6

String

2406:3003:2001:1c0a:4d38:6787:e1d4:7512

IPv6 Address

Wi-Fi SSID

String

HW1-E5172-7E74

Wi-Fi network name

Wi-Fi BSSID

String

1c:8e:5c:fa:7e:74

Wi-Fi network hardware address

Device OS

String

Android

Operating system of the device: "iOS" or "android"

Device OS Version

String

9

Version of the device operating system

User Agent

String

Mozilla/5.0 (Linux; Android 9; SM-J600G Build/PPR1.180610.011; wv) AppleWebKit/537.36 (KHTML like Gecko) Version/4.0 Chrome/74.0.3729.136 Mobile Safari/537.36

Web browser version and operating system

Device Make

String

Samsung

Manufacturer name

Device Model

String

SM-J600G

Device model name

Device Type

String

Smartphone

Smartphone or Tablet

Carrier Name

String

Verizon

Service provider name

Cell ID

String

25

Base Transceiver Station (BTS) number

MCC

String

US

Mobile Country Code

MNC

String

44010

 Mobile Network Code

Country Code

String

US

ISO2 2-digit alpha country code for the event

Publisher ID

String

ebd8eceafe1479f86f75e2f54d6 aac7

Unique developer identifier

App ID

String

2bfef19b8fdbfe3b5bf0cd388831d0df

Unique application identifier

App Category

String

life style

App store or IAB category name

Location Context

String

0

0 = foreground, event captured when the app is open

Location Context

String

1

1 = background, event captured when the app is not open

Geohash

String

teq7664zc1d5

Unique alphanumeric string to express a location

IoT / Beacons

String

2792c5ca-­b8fa-­11e2-­99a7-­14109fd63bf9

Base64 encoded JSON string; captures IoT/Beacons

UUID

String

00000000-4f59-7b28-4f57-7b2300000000

Universally Unique Identifier

Major

Long

123

Numbers assigned to iBeacons

Minor

Long

456

Numbers assigned to iBeacons

RSSI

String

-10

Beacon Signal Strength

STEP 3 - Server Integration

Bucket Access Guidelines

If you are using AWS S3
Email us with your AWS Account & User ID, and Quadrant will create the IAM Bucket name for you

Other Cloud Storage Guideline
Quadrant will create a unique IAM user and Bucket name for you.

Folder Structure Guidelines

Your bucket name is provided as:
S3://quadrant-<suppliername>/

Your subfolders as given. Upload your files in the given format as given.
/year=<yyyy>/month=<mm>/day=<dd>/hour=<hh>

As an example, if today is the 10th of April 2022, at 14:59, you will send it in this format
S3://quadrant-<suppliername>/year=<2022>/month=<04>/day=<10>/hour=<1400>

*All other folder structures will be rejected. Do contact your account manager and engineering support for any clarifications before sending data.

STEP 4 - SEND Data Feed

File Format Guidelines

Supplier data files should be compressed or g-zipped delivered in the following formats
- CSV
- Parquet

File Size Guidelines

  • File size must not exceed 400 MB per file.

Sending a Test File

Once the set-up as described above is completed, provide one sample file of size no larger than 5MB with the agreed Data Columns, Data Values, in the described Folder and File Structure.

Notify your account manager once you have shared the file and Quadrant will review the sample and respond within 24 hours.

(Recommended) Hourly Delivery Cut Off Time

All data must be sent within the Next Hour. If you have missed delivery for an hour, you can send it in the following hour. All data must be sent within the Date. For example, 1st April, UTC 2359H of specified date delivery.

Hour of Data Feed

Deadline to Deliver Data to Quadrant

1st April 2022, UTC 0100

1st April 2022, UTC 0200

If missed 1st April 2022, UTC 0100

1st April 2022, UTC 0300 (Includes 0100 & 0200)

Daily Delivery Cut Off Time

All data must be sent within 24 Hours. Quadrant will not accept any delivery that is sent after that. 

Day of Data Feed

Deadline to Deliver Data to Quadrant

1st April 2022

2nd April 2022 UTC 0100

2nd April 2022

3rd April 2022, UTC 0100

 

Ready to add an ethical, hassle-free revenue stream to your business?

Add Quadrant Location SDK to your app today