At the Adobe Summit this week several core services (much better construct than 'shared services') were introduced. While not terribly sexy, they do go to the continuing evolution of an enterprise platform. One of the new elements is "Master Marketing Profile" described as a single identifier or a 'ring to rule them all.'
Conceptually I'm intrigued since we have a need to look at audiences from the perspective of a publisher as well as a marketing services firm. And as with any new service the gap between the idea described in the opening session on a 50' screen and the explanation of it on a monitor at the booth was quite noticeable. We had questions and it felt like the answer was "I know a guy who knows a guy" who wasn't around at the moment.
So I thought I'd post my questions. And to provide context, let's start with the following scenario. I want to access an audience based on the following:
- Activity on our owned and operated sites using only content about a category of interest
- Traffic and events on the networks we represent that fit an 'audience extension model'
- Email and print subscription information for that category from a related line of business
- Loyalty and transaction based information from a retailer who promotes items in the category
- Social graph and interests from an advertiser's customer base that has expressed interest in a brand in the category
- Is the identifier built bottom up, e.g. a cookie, or from top down, e.g. total business?
- Is this the commercialization of the 'universal ID' concept that existed in professional services?
- If it is the master, is it safe to assume the existing identifiers are slaves and still remain active?
- Is there one or minimum set of IDs required to build the master?
- Must all child identifiers be an existing Adobe ID?
- As a core service, can I use it without analytics?
- Can I define the master to be the data management platform ID or even a client or advertiser's identifier?
- How are conflicts of information handled when dealing with multiple touch points?
- What is the logic sequence for aligning the above sources into a master?
- How will we know whether the process works or not?
- What percent of a given source can we expect to be mapped?
- How do we ensure orphans remain viable entities over time if they are not in the 'audience library'?
- How do we know which sources were used in a given profile or segment?
- Is there a probability of belonging associated with each source of contribution?
- How does the mapping process impact the creation of downstream business rules and event triggers?
- If a map is built with incomplete information, how do we avoid garbage in gospel out?
- Is membership in a segment based on this identifier a "Yes" "No" proposition, or "Maybe"? (What is the likelihood that this identifier really does represent what we think we want?)
- Is this a precursor to another consumer pool and compete with Axciom, KBM and Liveramp for matching services?
- What information is in the payload when shipping segments?
- Does the process provide an audit trail of the mapping such that it can be defended?
- Where is PII used and then masked in the process?
- How are cookies, digital fingerprints, and device ID's utilized in the process?
- How confident should we be we won't piss off consumers because of a technical black box?
No comments:
Post a Comment