Skip to content

Whitepaper · Media & Entertainment · Informatica Customer 360

Audiences, rights holders and licensees, resolved.

Audience, subscriber and fan identities, advertiser and agency accounts, talent and songwriter parties, and content, title and rights masters.

Informatica Customer 360 · PDI accelerators · 15 use cases · 14 source-system families · Updated September 23, 2026

01 · Executive summary

The short version

  • PDI delivers 15 media & entertainment use cases on Informatica Customer 360 with its accelerators. The use cases are drawn from 5 anonymized account profiles.
  • Each use case arrives pre-mapped: the 8 entities it can land on, the 14 source-system families it draws from, and the match and data-quality rules for those entities.
  • Design decisions are captured in adaptive-card workshops: 132 cards across 10 data-model workshops, so every answer becomes a configuration input.
  • The entry point is a $50,000 fixed-fee MDM implementation for any two source systems. Informatica licensing is procured separately.

02 · The master-data problem

Where the records disagree.

Media companies monetize the same people and works many times: a fan buys tickets, streams content and responds to a sponsor; a songwriter's work is licensed to venues, broadcasters and digital services. Revenue and royalty accuracy depend on resolving both the people and the works.

Audience, fan, advertiser and agency masters land on the Customer 360 core model, with talent, songwriter, publisher and licensee parties configured on it. Content, title, rights and musical-work masters are modeled as creative works, with ISWC and CISAC catalogued as public identifiers.

03 · What is prepackaged for this industry

The accelerator, before day one.

Data model in play

  • Person8 use cases
  • Organization8 use cases
  • Creative Work3 use cases
  • Legal Entity2 use cases
  • Category1 use case
  • Item1 use case
  • Product1 use case
  • Agreement1 use case

Source-to-target mappings

  • Salesforce Sales and Service CloudColumn-level mappings with page-level evidence
  • SAP ECC / S/4HANAColumn-level mappings with page-level evidence
  • CISAC ISWC / IPIElement-level mappings, confirmed per implementation
  • 11 enterprise system familiesLicensing / provisioning / billing, E-commerce / web accounts, ERP item / customer / vendor master, Ticketing / streaming / app platforms, CDP / marketing automation, Rights management / MAM, Contract / bid / co-op pricing systems, CRM…. Mapped at attribute-family level; column names confirmed from the data dictionary.

Rules and workshops

  • 11 match rulesIn the library for the entity types in play, ranked from exact keys to fuzzy name-and-address matching.
  • 35 standardization rulesAcross 23 attribute families: names, addresses, phones, emails, identifiers and more.
  • 132 adaptive cards10 data-model workshops, from party sub-types to stewardship.

04 · Use-case accelerator map

15 patterns, each with a landing.

Every pattern below is delivered on Informatica Customer 360 with PDI's accelerators. Patterns are anonymized from account profiles; a count such as 3× means the pattern recurs across profiles. Source systems are shown as system families.

Use case patternTypical source systemsLands on
Advertiser & Agency Account MDMSalesforce Sales and Service Cloud, SAP ECC / S/4HANAOrganization, Person
Advertiser & Sponsor Account MDMSalesforce Sales and Service CloudOrganization, Person
Agency / Organization Hierarchy MDMConfirmed in discoveryHierarchy relationships, Legal Entity
Audience & Subscriber 360 (federal employees & contractors)Confirmed in discoveryPerson, Organization, Agreement
Audience / Subscriber 360 (streaming + digital)Ticketing / streaming / app platforms, CDP / marketing automation, Licensing / provisioning / billingPerson, Organization
Content, Title & Rights MDMRights management / MAM, SAP ECC / S/4HANACreative Work
Fan 360Ticketing / streaming / app platforms, Contract / bid / co-op pricing systems, E-commerce / web accounts, CDP / marketing automationPerson, Organization
Licensee MDM (venues, broadcasters, digital services)Salesforce Sales and Service Cloud, Licensing / provisioning / billingOrganization
Licensee, Retailer & Distributor MDMLicensing / provisioning / billing, CRM, ERP item / customer / vendor masterOrganization
Media Rights, Content & Sponsor MDMRights management / MAM, Salesforce Sales and Service Cloud, CRM, SAP ECC / S/4HANACreative Work
Musical Works / Repertoire MDM (ISWC)CISAC ISWC / IPICreative Work
Player & Consumer 360E-commerce / web accountsPerson, Organization
Product / SKU MDM (card sets, merchandise)ERP item / customer / vendor master, PIM, E-commerce / web accountsCategory, Item, Product
Songwriter & Publisher Party MDM (IPI)Membership system / county payroll & dues files, CISAC ISWC / IPIPerson, Legal Entity
Talent / Athlete MDMContract / bid / co-op pricing systems, HCM / payrollPerson

05 · How it deploys

Five steps, each already built.

The accelerator replaces blank-page design with decisions, a drawn model and pre-built mappings.

  1. Decide

    Adaptive-card workshops capture the design. 10 data-model workshops, 132 cards. Each card asks one decision with two to four mutually exclusive options, and each answer is logged as a configuration input.

  2. Model

    The media & entertainment model is already drawn: 8 entities, with their relationships and hierarchies, selected for the use cases in this paper.

  3. Map

    The two sources arrive pre-mapped. 364 column-level mappings cover NPPES, MedPro, GLEIF, SAP, Salesforce and GS1, and 60 source-system families are catalogued in all.

  4. Match

    Match, merge and quality rules start from a library: 20 match models with 65 rules, and 35 standardization rules across 23 attribute families.

  5. Prove

    Tenant checks and acceptance. 80 documentation discrepancies are confirmed on the tenant before configuration is generated, and the acceptance measures agreed in discovery are tested.

This Customer 360 industry entry offer is distinct from the separately scoped Informatica MDM MVP.

06 · The two-source entry point

How a $50K MVP lands here.

A fixed-fee MDM implementation for two source systems. The model, the mappings, the match and data-quality rules and the workshop cards exist before the engagement starts.

Starting pattern
Audience / fan 360
Source system 1
Ticketing or streaming platform
Source system 2
Salesforce or marketing platform
Lands on
Person and Organization from the core model with Contact for reachable channels
What it proves
One fan or subscriber identity across ticketing and marketing, with consent-relevant attributes carried by source.

The $50,000 covers PDI professional services only. Informatica licensing is procured separately through Informatica. Additional sources, domains or scope changes after configuration begins are estimated separately. The example sources are illustrative; any two source systems qualify, and the pair is confirmed in discovery.

07 · Confirmed in discovery

What each engagement settles first.

  • The two source systems. 11 enterprise system families appear in this industry. Their column names are confirmed from the customer's data dictionary before mappings are finalized.
  • The tenant. 80 documentation discrepancies across the model are confirmed on the customer's tenant before configuration is generated, including field-group internal IDs that are read from tenant metadata.
  • Package order. Industry packages are imported before any customization, because importing an industry package overwrites existing Customer 360 customization.
  • Acceptance. Acceptance measures are agreed in discovery, before the fee is committed.

08 · Method

How this paper was built.

The use-case map, data model, mappings and rules come from PDI's accelerator, built on Informatica's published Customer 360 and Industry 360 documentation (April and July 2026 releases) and extended for each industry. Use cases are anonymized from 124 account profiles; no account is named. Adaptive-card counts come from PDI's Customer 360 data-model workshop set. The paper states no project durations or outcome figures; those are set as acceptance measures in discovery.

Read the full method →

Next step

Pick the two sources. We map the rest.

One discovery session confirms the two source systems, the domain, the entities it lands on and the acceptance measures.