Signals: File Based Delivery

Introduction

Our Signals system ingests event-level data and associates it with your account analysis. The Signals ingestion is based on a valid compressed (gzip) CSV file. It is important that the CSV file be in the right order with blank fields (empty strings) representing fields that are not available for analysis.

Delivery

If you would like to use your own S3 bucket on AWS you may provide either encrypted (md5) device Identifiers or plain text identifiers that will be encrypted in transit before reaching the Intuizi cloud for analysis.

If you would like to deliver to an assigned S3 bucket within the Intuizi cloud, we require that all device identifiers be encrypted (md5) before it is uploaded. The MD5 must be in UPPER case and if not encrypted the system will NOT return any results.

Intuizi can assist with the encryption process if necessary.

Example File

Example Uncompressed CSV File – Click Here

CSV Fields

Key	Value	Data Type
deviceifa*	Android Advertising ID or Apple IDFA	String(255)
latitude*	Latitude with up to 7 digits precision	Float
longitude*	Longitude with up to 7 digits precision	Float
userAgent	URL Encoded USER AGENT of device	String(255)
adwidth	Numeric Ad Width in Pixels	Integer
adheight	Numeric Ad Height in Pixels	Integer
campaignID	Alpha Numeric Campaign Identifier	String(255)
bannerID	Alpha Numeric Banner Identifier	String(255)
pubid	The assigned ID of a specific publisher grouping (apps or sites)	String(255)
invType	Display or Video	String(255)
deviceType	The numeric ID for the type of device.	Integer
country	The ISO code for the country	String(3)
bid	Assigned Business Identifier	String(255)
gender	M = male, F = Female, O = Other or unknown	String(1)
age	The numeric age of the user	Integer
ip	The IP4 ip address of the record	Integer
d*	This is the date of the record in Y-M-D H:i:s format	DateTime
auctionID	unique/randomized identifier	String(255)
bundleID	app source of signal	String(255)