Preparing Your Data
Please read the article Introducing the InfoSum Data Clean Room before reading this one as it provides helpful context for your collaboration project with us
Table of Contents
Learning to use the platform with mock data
Registering for the Platform
The platform does not offer self-registration.
To create your company and initial user accounts please fill in this form. Clients wishing to add or remove additional users will need to contact their InfoSum representative.
Have a preferred single sign-on (“SSO”) provider? Let your InfoSum representative know the name of your SSO provider and they will help you implement based on these SSO implementation instructions.
If there are multiple users at your company, owners can enable or restrict each user within your company by setting user roles and rights. For example, you may want to restrict the ability to delete a Dataset, or the ability to grant permissions to your Dataset with other companies, for certain users in your company.
Once you have registered for the platform, InfoSum will then enable your company’s account to create Dataset, among other features that are required to perform your desired use cases.
| Level of Complexity | Low |
| Estimated timing | <5 minutes |
| Role(s) involved | Both technical and non-technical users within your organization who require access to the InfoSum platform |
Datasets, Bunkers & Beacons
Datasets are are secure storage environments for your pseudonymized data - they can be Bunkers if they are provided by InfoSum or Beacons if they are installed on your cloud or warehouse. During data preparation you will select which data is avialable in your Dataset.
There are three types of data hosted in a Dataset that can be identified during the normalization process:
-
IDs and PII must be marked as Keys to be used for collaboration
- Map common IDs to the Global Schema to ensure standardization of data
- Attributes represent the information about your customers (non IDs) and can be used for analysis. Data is defaulted to attribute if not marked as a key.
-
Activation IDs must be marked as Export Columns for activation to third parties. Must be present for activation use cases.
- If your collaboration and activation keys are different (e.g. you are matching on email but exporting an internal ID), you will need to include both keys in the Dataset
- You will not be able to export data out of your Dataset if there are no Export Columns selected at this stage
Data Formatting Guidelines
| Important |
| Before creating your data please share a sample data schema with your InfoSum representative, so they can best advise you on a format that can support your use cases. You can provide this using the onboarding form. |
Please read this article to learn how to best format your data so it can be successfully mapped to our global schema and normalized. There are some guidelines on format for specific data types and some more general recommendations.
| Level of Complexity | Moderate |
| Estimated timing | 0.5-2 hours |
| Role(s) involved | Technical users with access to your company’s PII data, typically Operations, Technical Services or Data Engineers. Please ensure that your account admin has allocated the rights to perform this task |
| Other Relevant Article(s) | Platform Limits |
Learning to Use the Platform with the mock data
[Optional] If you’d like to test the platform before moving to the next step, InfoSum can invite you to a collaboration and add some mock data. Please ask your InfoSum representative for more information.
Read Next
Continue by Onboarding your data