Signals: File Based Delivery
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.
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 Uncompressed CSV File – Click Here
|Encrypted Android Advertising ID or Encrypted Apple IDFA
|Latitude with up to 7 digits precision
|Longitude with up to 7 digits precision
|URL Encoded USER AGENT of device
|Numeric Ad Width in Pixels
|Numeric Ad Height in Pixels
|Alpha Numeric Campaign Identifier
|Alpha Numeric Banner Identifier
|The assigned ID of a specific publisher grouping (apps or sites)
|Display or Video
|The numeric ID for the type of device.
|The ISO 3166 code for the country (Alpha-3 code)
|Assigned Business Identifier
|Gender. (M = male, F = Female, O = Other or unknown)
|Numeric age of the user
|IP address (IPv4/IPv6) of the record
|Date of the record in Y-M-D H:i:s format
|Source app Identifier of the signal
|Source domain of the signal
|Web page URL of the source signal
|Signal’s referrer’s web page URL
|App source category based on IAB Categories. (Example: IAB7,IAB17)
|Geographical location type based on oRTB API Specification.
|Physical height of the screen in pixels
|Physical width of the screen in pixels