Multi-target activation with missing identifiers and consent lag
A subscription box company has a 620K-member win-back segment. It activates to Marketing Cloud Engagement for email and to Google Ads Customer Match for display. 140K members have no email contact point; 55K have an email but the latest consent record is opt-out or unknown; 30K have a phone but no email. Marketing Cloud's data action requires Contact Key and Email; Google Ads requires a hashed email. The team currently uses one activation with both targets, runs it hourly, and sees duplicate sends and Google rejecting rows. Marketing Cloud's unsubscribe list is maintained in Marketing Cloud, not in Data Cloud. Legal requires that opt-outs are suppressed within 15 minutes.
1. Why is a single activation to both Marketing Cloud and Google Ads producing duplicates and rejects? Recommend the target architecture.
Read the worked answer
The two targets have different identifier requirements and different send semantics. Marketing Cloud needs a Contact Key and Email; Google Ads needs a hashed email. A single activation cannot apply the right filter and field mapping for both. Google rejects rows that lack a usable hashed email, and the hourly refresh can re-send records to Marketing Cloud without an idempotent contact key, producing duplicates.
Split into separate activations per target, and possibly per channel. For Marketing Cloud, use a data action that maps a stable Contact Key and Email and excludes records without both. For Google Ads, use a separate activation filtered to records with a normalized, consented email; let the Google target handle hashing, and validate the normalized email before activation. Each activation should have its own schedule and monitoring. Do not use one activation as a shared pipe for channels with different identity rules.
2. How would you handle members without email, and members with opt-out or unknown consent, for each target?
Read the worked answer
Treat missing identifiers and consent as separate gates. For Marketing Cloud email, exclude the 140K with no email and the 55K with opt-out or unknown consent. The 30K phone-only members are not email candidates; route them to an SMS activation only if SMS consent exists and the channel is approved. For Google Ads, exclude anyone without email and anyone without advertising consent; do not attempt to send phone-only records to a target that expects email.
Unknown consent should be treated as no consent unless legal says otherwise. Build the segment or activation filters so each target receives only eligible records, and document the counts by exclusion reason. That prevents the team from optimizing the segment size while silently sending ineligible records to a target that cannot suppress them.
3. Legal requires opt-outs suppressed within 15 minutes. What data flow and activation cadence would you design?
Read the worked answer
Bring Marketing Cloud unsubscribe and consent events back into Data Cloud as close to real time as the connector or Ingestion API allows, and map them to the contact point consent DMO linked to the unified individual. The activation eligibility filter must read that consent state, not just the original segment membership. Run the Marketing Cloud activation frequently enough to meet 15 minutes, and keep Marketing Cloud's own suppression active as a send-time backstop for email.
For Google Ads, recognize the constraint: there is no send-time suppression after the audience is uploaded. Use the most frequent refresh the target allows, filter out opt-outs before each run, and document the residual gap if the target cannot refresh within 15 minutes. If legal cannot accept that gap for advertising, exclude Google from the near-real-time requirement or use a channel where send-time suppression is enforceable. The design should state where the 15-minute guarantee is met and where it is not.