Page tree
Skip to end of metadata
Go to start of metadata

Overview

Once cookie synchronisation with ID5 has been implemented, we are able to start delivering user mappings to other platforms. We can deliver these mappings to you via file-based transfers, streaming transfers, or a web service API.

  • Streaming TransferPreconfigured Match Partner UIDs are automatically pushed to you at regular time intervals
  • File-based UID MatchingID5 will match a set of your UIDs provided via an uploaded file to one or more preconfigured Match Partners and return them via file upload.
  • Web Service APIYou will make requests to an ID5 endpoint to request user matches to/from a preconfigured set of Match Partners for a set of users with near-realtime responses

Cloud Storage

Streaming and Matching methods rely on an AWS (Amazon Web Service) S3 bucket to exchange data; the S3 Bucket can be provided by ID5 or by you. If you need us to use a different cloud platform, let us know and we'll work with you to find a solution that works.

To comply with the General Data Protection Regulation (GDPR), the AWS S3 bucket must be physically located in a European datacentre (Paris, Dublin or Frankfurt) if it has to handle data related to European users. ID5’s UID match service follows a privacy-by-design principle ensuring that data is protected and that no other piece of information is transferred alongside UIDs.

As ID5 is simply Processor of user personal data, it is recommended that you own the AWS S3 bucket in which pseudonymized UIDs are exchanged. To share the bucket with ID5, you will need to provide ID5 permission via our AWS canonical ID (Bucket and permission can be manually set from https://s3.console.aws.amazon.com/ or using aws-cli).

ID5 AWS Canonical ID

b90fe88135ddb53ec153d1501c68b85f631bcaf82e579b3ba58a960cee8e4911
  • No labels