Applications

One live profile across every brand, site, and subscription.

Resolve customer context across brands, sites and subscriptions without migrating every tool. EngageMKTG connects identity, consent, events and marketing state while keeping the relationships and permissions that make each proposed action eligible.

Updated

Discuss portfolio unification

Who this is for

Portfolio companies. One person appears as unrelated records in several systems, leading to duplicate journeys and inconsistent reporting. Review identity and the original source relationships together.

Publishers and subscription businesses. A reader can subscribe to one publication and decline another. A unified profile should retain that difference rather than flatten every relationship into one global marketing flag.

Agencies with multi-brand clients. Repeated audience assembly can create fragmentation and contact pressure. Build a reviewable portfolio view while keeping each client and brand permission boundary explicit.

A decision in context

A person subscribes to two brands and unsubscribes from one. Identity unification can recognize the person while preserving the distinct subscriptions and suppressions. A campaign for the first brand must use the first brand relationship; the existence of the second subscription does not repair an opt-out. This is the distinction between reusable context and unrestricted activation.

How it works

The decision waterfall applies the existing profile, consent, status, frequency, selection and execution sequence. The relevant sources and rules are reviewed for this application before a pilot.

  1. Profile validation. Review the source identifiers and how records are resolved into a profile. Keep source references so a surprising match can be investigated.

  2. Consent. Check permission by brand, domain and purpose. Shared ownership of two brands is not evidence that a person consented to both marketing programs.

  3. Status. Read subscriptions, suppressions and current marketing state in the relevant relationship. Preserve a more restrictive state rather than overwrite it with an active record from elsewhere.

  4. Frequency. Evaluate contact pressure and timing for the proposed use case. A portfolio view should help operators see overlap rather than make duplicate messages harder to detect.

  5. Selection. Build a reviewed audience using the profile and event context appropriate to that brand. Segment reuse still needs an eligible purpose and current data.

  6. Send or suppress. Return the selected action or suppression and its reason to the agreed system. Keep the relationship context available in reporting so teams can explain the result.

Test the flow before expanding

Start with a known set of source records and review identity matches, subscription differences and suppression conflicts. Test both same-person and different-person cases. Then assess audience assembly and reporting against the defined baseline. Fewer records alone does not prove better identity quality; a mistaken merge can also make a database smaller.

Keep one owner for the pilot decision and the evidence it needs. An allowed action, a provider acceptance and a business outcome are separate observations. If an input is missing or a rule fails, record that limitation and choose the next bounded test. Do not fill a reporting gap with an assumed uplift or keep expanding a workflow simply because the integration has been written.

The published platform modules provide the profile graph, live marketing status, event-centric timeline, planners and Decision API behind this approach. Their value in a particular account depends on the reviewed mapping and operating rules. Define the first application clearly enough that your team can inspect both the selected actions and the people deliberately excluded.

FAQ

No permission is created by resolving identity. Retain consent and suppression by the relevant brand, domain and purpose.

Do we migrate every platform?

The published approach connects context without requiring every tool to move. The first implementation still needs reviewed mappings and available interfaces.

How should conflicting records be handled?

Make the source and meaning of each state explicit. Test restrictive consent and suppression cases before activating reusable segments.

Can agencies use the same audience for different clients?

A portfolio view does not establish cross-client sending permission. Each proposed action needs its own reviewed relationship and eligibility.

Read before you start