MadConnect: Technical Guide
  • Platform Overview
  • Why MadConnect?
  • How does MadConnect Work?
  • Features
  • Architecture
  • Deployment Scenarios: MadConnect
    • Self-service Web Platform
      • Dashboard
      • Accounts
      • Platforms
      • Connections
      • Settings
    • Embedded API: Powered by MadConnect
    • White Labeling
  • Connectors
    • Available Connectors
  • Use Cases
  • Security
  • Cloud Platforms
  • Glossary
Powered by GitBook
On this page

Use Cases

MadConnect can be the platform of choice while planning for transfer of data between and source and a destination. MadConnect can integrate with the following data types:

  • First Party Data/CRM: Requires setting up scheduled extract of your accounts with the corresponding transactions and attributes.

  • Data Enrichment: Any data set that enriches an overall enterprise identity spine and can depend on client needs including, but not limited to:

    • Demographic

    • Entertainment

    • CPG

    • Automotive

    • Behavioral

    • Geolocation

    • Financial

  • Identity Resolution Platform Audience Activation: Requires transferring a standardized on-demand list of IDs. MadConnect can facilitate the transfer of IDs between sources:

    • 1st party PII IDs via cleanrooms that can sync to an already recognized ecosystem ID (UID 2.0, RampID, ID5, CTVID etc.). These connections allow seamless flow into (including but not limited to):

      • MVPDs

      • DSPs

      • SSPs

      • Social

  • Source and Destination Audience Refreshes and Suppression

    • To adhere to ongoing privacy legislation, MadConnect enables audience refresh at both source and destination.

    • Periodicity: While monthly is the industry standard, you can configure the cadence as required.

PreviousAvailable ConnectorsNextSecurity