How Can We Help?

Search for answers or browse our knowledge base.

Documentation | Demos | Support

On this page
Print / Download as PDF

Anonymized Signals

Table of Contents

Introduction

Anonymized Signals data is meticulously structured to cater to various business needs, ensuring precision, reliability, and compliance with privacy standards. This document serves as a guide to understanding the various data fields we offer, their significance, and how they can be utilized to drive informed decisions and strategies.

 

Data Overview

Our data is categorized into several key areas, each encompassing specific information types:

  1. Primary Identifiers: These include unique encrypted identifiers such as the Encrypted Mobile Ad Identifier (eid) and Mobile Ad Identifier (maid), essential for distinguishing and tracking mobile ad data.

  2. Geo-Location Fields: This category provides detailed geographical data points including latitude, longitude, and corresponding accuracies, crucial for location-based analytics and targeting.

  3. Advertising Fields: These fields focus on advertising metrics like ad dimensions, campaign IDs, and publisher IDs, instrumental for ad performance analysis.

  4. User Details: This section includes data on user devices, operating systems, and app IDs, offering insights into user demographics and behaviors.

  5. IP Details: Here, information related to IP addresses and ISPs are provided, aiding in network-based analysis and targeting.

  6. General Data Fields: General information such as timestamps are included here, giving context to data records.

 

Delivery Options

We provide versatile and secure data delivery options tailored to diverse requirements, including major cloud platforms like Google Cloud Platform (GCP) and Amazon Web Services (AWS), as well as custom solutions for specific needs. This ensures efficient and convenient data management for all our clients, regardless of their unique infrastructure.

AWS S3

Intuizi offers versatile data storage solutions, allowing clients to either store their data securely on their own S3 bucket or access it conveniently from Intuizi’s managed S3 bucket, ensuring flexibility and control to meet diverse data management needs.
 

Storing Data on Your S3 Bucket

For clients opting to store data in their own Amazon S3 bucket, we offer a streamlined and secure setup process. This allows clients to control their data storage directly while utilizing Intuizi’s services. The process involves the following requirements:

Client-Provided Details

For exporting data to a client’s S3 bucket, the client must provide:

  • Bucket Name: The unique identifier for their specific S3 bucket in AWS.
  • Region: The geographic location of the S3 bucket, crucial for efficient data transfer and compliance.
 
Granting Permissions to Intuizi
For Intuizi to export data to the client’s AWS S3 bucket, the client must grant certain permissions to our user ARN. This can be done by adding our ARN to their bucket policy or IAM policy. Please refer to the JSON example below.
 
Data Transfer and Security

Once the necessary credentials and permissions are in place, Intuizi will proceed with the data transfer:

  • Secure Transfer: Ensuring that all data transfers to the client’s S3 bucket are encrypted and secure.
  • Compliance and Standards: Adhering to best practices and industry standards for data security and privacy.

Accessing Data on Intuizi’s S3 Bucket

Clients choosing to store their data on Intuizi’s S3 bucket will receive a CSV file with necessary credentials. This file includes details such as S3 URL, Account ID, IAM User Name, Password, Access Key, Secret Access Key, and S3 URI, enabling access to the bucket and its data.

Access Methods

  1. Programmatic Access

    • Utilize the Access Key and Secret Access Key for automated interactions with the S3 bucket.
    • Suitable for scripting or application integration using AWS SDKs or the AWS CLI.
    • Enables automated data management tasks.
  2. UI Access

    • Access the S3 bucket through the AWS Management Console with the provided IAM User Name and Password.
    • Ideal for manual operations like uploading, downloading, or viewing data.
    • User-friendly, requiring no programming skills.

These methods ensure secure and versatile access to your data stored on Intuizi’s S3 bucket.

Google Storage

Intuizi offers flexible data storage and access solutions for clients, either through storing data on the client’s own Google Cloud Platform (GCP) storage or by providing access to data stored on Intuizi’s GCP bucket, tailored to meet diverse data management needs.

Storing Data on Your Google Storage

When opting to store data on their own Google Cloud Platform (GCP) storage, clients need to provide certain key details to facilitate the data transfer:

  • Service Account Key: Clients are required to share a JSON key file of a service account that has the necessary permissions to access Google Cloud Storage. This key is crucial for authentication and authorization.
  • Bucket Name: The specific name of the client’s Google Cloud Storage bucket where the data will be uploaded. This name helps in accurately identifying the storage location within the GCP.
  • Enabled Google Cloud Storage API: Clients must ensure that the Google Cloud Storage API is activated in their GCP project. This enables programmatic interactions with the storage buckets, essential for managing the data transfer process.

Accessing Data on Intuizi’s Google Storage

For clients who prefer to access data stored on Intuizi’s Google Cloud Platform (GCP) bucket, the following outlines our access provisions:

  • Intuizi-Managed Credentials: We provide clients with necessary credentials, ensuring secure access to the data stored in Intuizi’s GCP bucket.
  • Data Retrieval and Management: Clients can easily retrieve, manage, and analyze their data through these credentials, benefiting from the robust and scalable infrastructure of GCP.
  • Support and Assistance: Intuizi offers full support and assistance in setting up and navigating the access to our GCP bucket, ensuring a smooth and hassle-free data management experience for our clients.

Delivery Formats

In our data delivery process, we employ a meticulously structured, partitioned format to enhance both the manageability and efficiency of data usage. This approach is particularly beneficial for clients dealing with large datasets or requiring quick, specific data access.
 

Available Formats

  • Parquet (Default): Our preferred choice, Parquet is a columnar storage format offering excellent data compression and fast query performance. Available compression values for Parquet include uncompressed, snappy, gzip, and lzo, allowing for tailored data optimization.
  • CSV – GZIP: A widely accepted and compressed format, perfect for simple and efficient data exchanges, compatible with standard CSV import tools.
  • ORC: Ideal for clients engaged in extensive data analysis, ORC format is optimized for high-speed reading and efficient data processing.
  • AVRO: Best suited for complex datasets requiring schema evolution, AVRO is a row-based format that excels in data serialization.
  • Other Formats: We also provide a range of other formats to ensure maximum flexibility and customization based on unique client needs.

Partitioning Details

Our use of Hive Parquet for data partitioning is strategically chosen to ensure efficient storage and enhanced query performance, especially beneficial in handling large-scale data environments.

  • Day: Data is partitioned by day, following the format ‘day=YYYY-MM-DD’. This allows for easy retrieval of data based on specific dates, making time-sensitive analyses more straightforward.
  • Country: We also partition data by country, using the format ‘country=USA’. This is especially useful for clients who need to perform region-specific analyses or who are focusing on geographic trends and patterns.

    We offer flexible custom partitioning options to accommodate unique client requirements, allowing for tailored data organization and access based on specific timeframes, geographic regions, or other criteria.

Data Format

Primary Identifiers

Key Description Value Data Type
eid Encrypted Mobile Ad Identifier AE9CDA2D92E101159308BEBAXXXXXXXX String(32)
maid Mobile Ad Identifier 3f097372-f01e-4b64-984c-395axxxxxxxx String(32)

 Geo-Location Fields

Key Description Value Data Type
latitude Latitude of the location with up to 8 digits precision 25.271812 Double
longitude Longitude of the location with up to 8 digits precision 51.525530 Double
latitudeacc Latitude decimal degrees accuracy 6 Integer
longitudeacc Longitude decimal degrees accuracy 6 Integer
precision Indicates the precision of a data point in meters (N/S or E/W at equator) 0.111 Double
locationtype Source of location data (GPS coordinates). Refer to List 2 to see options 0 Integer(1)
country Country code (ISO 3166-1 alpha-3) USA String(3)

 Advertising Fields

Key Description Value Data Type
adwidth Numeric Ad Width in Pixels 320 Integer
adheight Numeric Ad Height in Pixels 480 Integer
campaignid Alpha Numeric Campaign Identifier xxxxlor-fans-5786xxxxx String(255)
bannerid Alpha Numeric Banner Identifier 1099f1a8-39c9-4e07-964c-275ff0749360 String(255)
pubid The assigned ID of a specific publisher grouping (apps or sites) 174052030 String(255)
invtype Display, Video or Banner Display String(255)
bid Assigned Business Identifier 65d06ab137516e1f4af098baxxxxxxxx String(255)

 User Details

Key Description Value Data Type
useragent The User-Agent (UA) string is contained in the HTTP headers and is intended to identify devices requesting online content. Mozilla/5.0 (iPad; CPU OS 15_7_6 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 String(255)
devicetype The general type of device. Refer to List 1 1 Integer(1)
deviceos Identifies the operating system of the user’s device, such as iOS or Android. iOS String(255)
devicemake Specifies the manufacturer or brand of the device, like Apple or Samsung. Apple String(255)
devicemodel Denotes the specific model or version of the user’s device, such as iPhone 12. 13 Pro Max String(255)
appid Unique identifier for an application installed on the device 352683833 String(255)

 IP Details

Key Description Value Data Type
ip The IP address (IPv4) of the record 37.208.XXX.XX String(15)
isp The name of the ISP (internet service provider) associated with the IP address. AT&T String(255)
connectiontype Connection Type. Options are: Cable/DSL, Cellular, Corporate, Satellite Cellular String(15)

 Privacy Details

Key Description Value Data Type
consent_ccpa Consent field for US Privacy string.  Further documentation can be found here. 1YNN String(4)
consent_gdpr Consent field for General Data Protection Regulation (GDPR). Vendor Consent String Format can be found here. BOEFEAyOEFEAyAHABDENAI4AAAB9vABAASA String

General Data Fields

Key Description Value Data Type
datetimeutc This is the date of the record in Y-M-D H:i:s format 2023-12-10 00:15:37 DateTime

 Specifications

 1. Device Type

The following table lists the type of device from which the impression originated.

Value Description
1 Mobile
2 Tablet
3 Personal Computer (PC)
4 Connected TV
0 Unknown

 2. Location Type

The following table lists the options to indicate how the geographic information was determined.

Value Description
0 IP Address 
1 GPS/Location Services
2 User provided (e.g., registration data)

JSON Examples

Bucket Policy

The ARN client’s policy is a JSON configuration granting specific permissions to Intuizi’s user within a client’s AWS environment. It allows Intuizi’s ARN, to perform actions such as reading, writing, and deleting objects in a specified S3 bucket. This configuration is essential for enabling Intuizi to access and manage data within the client’s S3 bucket while maintaining appropriate security measures.

				
					{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "intuiziaccess",
            "Effect": "Allow",
            "Principal": {
                "AWS": "arn:aws:iam::128297264883:user/service-data-delivery"
            },
            "Action": [
                "s3:ListBucket",
                "s3:GetObject",
                "s3:PutObject",
                "s3:DeleteObject"
            ],
            "Resource": [
                "arn:aws:s3:::example_bucket",
                "arn:aws:s3:::example_bucket/*"
            ]
        }
    ]
}
				
			
Was this article helpful?
3 out of 5 stars

4 ratings

5 Stars 50%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 50%
Please Share Your Feedback
How Can We Improve This Article?