Skip to main content

​
Get Started

This document is intended for Data Partners to understand the different stages involved in the process of transferring third-party data to Zeotap. Once a contract is signed between Zeotap and the Data Partner, the data transfer process works in the following order:
  1. Step 1 - Initial Discussion Regarding the Data Category – From Zeotap’s end, we initiate a detailed discussion with you regarding the data categories that you wish to send.
  2. Step 2 - Choose a Data Transfer Method – Next, we introduce the data transfer methods we offer, allowing you to select a method for your data transfer.
  3. Step 3 - Understand the Hashing Guidelines – To prioritise data security and privacy, we introduce our hashing guidelines, which help protect sensitive information during the transfer process.
  4. Step 4 - Upload a Sample File – Before proceeding with the full data transfer, we take a sample file for testing and validation purposes. This step ensures a smooth and error-free process.
  5. Step 5 - Start Uploading Your Data – Once all the above steps are completed and we have successfully tested the sample file, you can proceed with the secure transfer of the complete dataset from your end to Zeotap.

​
Step 1 - Initial Discussion Regarding the Data Category

The data transfer process begins with an initial discussion between you and Zeotap. This involves going over the data categories that you intend to send to Zeotap. This includes Profile (Demographic, Interests, Intent), Devices and Contracts, Travel, Apps and more. In addition, the frequency of data transfer such as daily, weekly, monthly, bi-weekly and more is agreed upon in this phase.

​
Step 2 - Choose a Data Transfer Method

Zeotap offers different data transfer methods to partners for sharing their data. Note that the data transfer can be conducted through either or both of the following methods:
  • Flat Files (CSV and JSON): This method allows you to transmit your data in flat file formats like CSV (Comma-Separated Values) and JSON (JavaScript Object Notation). It provides a straightforward way to structure and organise the data for transfer. Note that you must have a GSuite account and a linked Google Cloud Storage bucket to use this method. If you do not have a GSuite account, then we can create a service account for you and provide you with a JSON key, ensuring secure access to the bucket. For more information about transferring data through Flat Files, refer to the Flat Files documentation.
  • Pixel Integration: This method allows you to place a pixel provided by Zeotap on the client’s website. When visitors interact with the website, the pixel collects relevant data and sends it securely to Zeotap. This method allows for real-time data transfer and is commonly used for tracking and gathering specific user interactions. Note that it is important to adhere to GDPR regulations by obtaining user consent, while working with Pixel integration. If you are working with a TCFv2.0 compatible CMP (Consent Management Platform), then ensure that you list Zeotap as a vendor within your CMP. In turn, Zeotap includes the relevant GDPR parameters in the pixel to enable you to pass the consent flag and consent string to the pixel calls.

​
Step 3 - Understand the Hashing Guidelines

As a Data Partner, ensure that you follow these hashing guidelines before sending the data to Zeotap:

​
For Email Addresses

The following are the hashing guidelines for email IDs:
  1. Note that you have to provide hashed email IDs only.
  2. Remove all leading and trailing spaces from the email IDs before hashing.
  3. Convert the email IDs into both lower and upper cases like name@ and NAME@.
  4. Apply SHA-256 hashes to the raw email IDs in both lowercase and uppercase formats, creating the following two sets:
    • SHA256 (lowercase)
    • SHA256 (uppercase)
  5. If you already have hashed versions of the email IDs, then simply provide them as hashed to SHA256. Also, indicate whether these hashed email IDs are in lowercase or uppercase.

​
For Phone Numbers

The following are the hashing guidelines for Phone Numbers:
  1. Note that you have to provide hashed phone numbers only.
  2. Remove all special characters, including (), +, and -, from the phone numbers before hashing.
  3. Divide the phone numbers with country code and without country code into two separate fields. For example, if the number is from Spain, then provide the following two formats:
    • With country code: 34679594499
    • Without country code: 679594499
  4. Apply SHA256 hash to the raw phone number in both formats, creating the following two sets:
    • SHA256 (with country code)
    • SHA256 (without country code)
  5. If you already have hashed versions of the phone numbers, then simply provide them as hashed to SHA256. Also, indicate whether these hashed phone numbers are with or without the country code.

​
Step 4 - Upload a Sample File

For Flat Files, we recommend that you provide a sample file to analyse the quality of the data you are planning to ingest into Zeotap. The sample file serves as a representative subset of your complete dataset. For example, say, one million records from the top EU countries. To share the sample file with us, you can simply upload it to the Google Cloud Storage bucket associated with your GSuite account. If you do not have a GSuite account, then we can create a service account for you and provide you with a JSON key, ensuring secure access to the bucket. However, if you are using Pixel Integration, there is no need to upload a sample file as the data is streamed to the Zeotap system on a real-time basis.
Ensure that you upload the flat file in the designated directory path on the Google Cloud Storage bucket or the Service Account. The generic directory path for uploading the file is:
While uploading data of a particular data category such as Profile, Travel, Apps and so on, ensure that you create a designated root folder with the data category name. This data category is added as a prefix to the directory path. In the below example, a root folder for the data category Profile is created with the folder name PROFILE_SAMPLE, to upload a sample file. Therefore, the prefix PROFILE_SAMPLE is added to the directory path:

​
Step 5 - Start Uploading Your Data

Once the sample file is successfully evaluated by Zeotap, you can start uploading the data at the agreed frequency to the designated directory path.
Ensure that you create folders in the directory path with the name of the data category that you plan to upload as explained above.
After the upload is complete, Zeotap allows a buffer time of 7 days and then performs the following steps to process the ingestion:
  1. After the buffer time, Zeotap pulls the data from the data sources and analyses it on its end. This helps identify the attributes that have been sent.
  2. Zeotap initiates the mapping process with the internal taxonomy to organise and categorise the data.
  3. During the mapping process, Zeotap identifies and performs the pre-processing of the data if required. This ensures that the data is in the appropriate format.
  4. Once the mapping process is complete, Zeotap initiates the data ingestion process, where the processed data is stored and made available for further analysis and use.

​
Revenue Reporting

Revenue Reporting refers to the process through which Zeotap compiles, analyses and shares financial information derived from the monetisation of various segments. Once Zeotap receives revenue reports for all segments that were monetised in the previous month, Zeotap processes them and splits the revenue among the involved parties. Your revenue share depends on your contribution to each segment that was monetised and your contract terms. Note that the revenue reports are processed around the 18th to 25th of every month. Once processed, Zeotap’s finance team sends a Credit Note to you through email. You have to then raise an invoice for the exact amount along with the date and share it back to Zeotap at InvoicesEU@zeotap.com. Ensure to include the following information in the email:
  • Zeotap’s Billing Address: zeotap GmbH c/o WeWork Stressemannstraße 123, 10963 Berlin, Germany
  • VAT: DE295498059
  • Your VAT number
  • Your complete address
  • Billing period
  • Currency
  • Net Terms as per contract
  • Banking details: Beneficiary Name, Bank Name, Bank Address, Bank Account Number, BIC/SWIFT Code

​
Opt-Out Process for Data Partners

This opt-out information can come from different sources and is categorised as follows:
  1. From Data Partners: As a Data Partner, you play a crucial role in providing opt-out information to Zeotap. Ensure that you send the opted-out users list as per the agreed frequency. Subsequently, Zeotap can target these users for suppression in the later stage.
  2. GDPR Compliance: This includes user data from individuals who opt out of the processing and storage of their information for GDPR compliance.
Zeotap takes responsibility for maintaining its opt-out database, which stores all the gathered opt-out information related to user IDs from the mentioned sources. This database serves as the central repository, ensuring that all opt-out information is duly deleted. Note that your collaboration in providing opt-out information is vital to uphold user privacy and preferences.

​
Format and Frequency of the Opt-Out Information

As a Data Partner, you can send opt-out requests to Zeotap using either API connection (pixel integration) or flat file transfer. These requests can be sent on a daily, weekly or monthly basis. Note that for Flat Files, you have to send the opt-out information in the following format:

​
Data to be Deleted

Based on whether the opt-out information comes in from you or the user directly, the following are the data that is deleted:
Last modified on September 24, 2026