Philippines staffing research · Updated September 28, 2026

Do marketing suppression requests reach every approved sending system?

A propagation study of opt-out requests, identity matching, system scope, suppression events, exceptions, and later sends.

Decision in scope. This protocol is for a buyer considering marketing operations support. It tests whether suppression administration can be delegated without delegating consent, legal interpretation, identity exceptions, campaign purpose, or remediation decisions. It does not publish an industry benchmark, promise a result, or score individual workers. The output is a documented account of one buyer's queue and the conditions that would make a limited handoff reviewable.

Research question. For marketing opt-out requests received through approved channels, what proportion can be traced to the correct identities, required sending systems, suppression events, and any later-send investigation? Freeze that question before the first record is coded. If the team changes the question after seeing the data, keep the new analysis separate and label it exploratory. That discipline matters because a convenient metric can answer a different question from the one that drove the staffing decision.

Sources and their role. This protocol uses primary guidance checked on September 28, 2026. The 2025 GAO Green Book informs authorization, documentation, control design, monitoring, and response to change. NIST SP 800-53 supplies audit, accountability, access-control, and privacy-control concepts. FTC guidance supports collecting only needed data, limiting retention, and controlling access. The Philippine Data Privacy Act supplies the local privacy context. AAPOR's disclosure elements inform the methods record. These sources shape the protocol. They do not supply observations or outcomes for the buyer.

Population and window. Include all marketing opt-out requests first received during twelve consecutive weeks, including one-click events, replies, preference-center changes, duplicate identities, bounced addresses, and disputed later sends. Register the start and end dates, working timezone, eligible channels, source systems, cutoff rule, and terminal events before export. Keep a screening log that counts included units, test records, out-of-window events, missing identifiers, duplicates, and records withheld because the reviewer lacked permission.

Unit of analysis. Count one suppression request for one reachable address or registered identity and stated scope, linked across systems under a stable request identifier. Messages, reminders, edits, exports, system checks, and status changes are events attached to that unit. They are not extra units. This prevents busy cases from inflating the denominator and keeps the result tied to completed or unresolved work rather than activity volume.

Field dictionary. Collect only what the question requires: request ID, source channel and time, address or pseudonymous identity, requested scope, identity matches, exception flag, system inventory version, required destinations, suppression events, propagation checks, later sends, investigation owner, correction, notice, and terminal state. Define each field, allowed values, controlling source, timestamp meaning, timezone, change behavior, and missing-value code. Keep direct identifiers in the approved operating system. Use stable pseudonymous identifiers in the analysis file whenever the review does not need a person's identity.

Controlling evidence. Treat the attributable request, approved identity-matching rule, current sending-system inventory, platform suppression events, and authorized exception decision; a spreadsheet flag does not prove that every sender stopped. If two permitted sources disagree, preserve both values, effective times, and the conflict. Apply only the source-precedence rule approved by the buyer. An analyst must not choose the more convenient source simply because it makes the record look complete.

Outcome coding. Use these registered classes: fully propagated, identity ambiguous, scope ambiguous, destination missing, suppression pending, exception review required, later send observed, test message excluded, corrected, notice pending, duplicate request, and unresolved. The codebook should state which conditions can coexist, which class takes priority, and what evidence moves a unit to a terminal state. Keep an unresolved class. Forced success and failure labels hide uncertainty and make later correction harder.

Measures. Show counts and denominators before percentages. The primary output is the distribution of registered outcome classes. Secondary measures are request counts, identity-match coverage, destination coverage, propagation time, ambiguous scope, exception reviews, later-send frequency, correction time, notices, and unresolved age. For elapsed time, report medians and selected percentiles rather than a mean alone. Put missingness, exclusions, and censored units beside every affected measure.

Event order. Reconstruct creation, first action, each material transition, owner request, response, correction, and terminal event in the site's UTC timezone while retaining original offsets. Write a deterministic rule for events with the same timestamp. Separate active preparation from owner wait, scheduled delay, system delay, and unknown time when the records allow it.

Review quality. Two reviewers independently trace every later-send and exception-review case plus a random sample classified as fully propagated against the frozen system inventory. Both reviewers use the same frozen codebook. Record disagreements before discussion, then publish agreement counts for the reviewed sample and list any rule changed during reconciliation. A material rule change requires recoding the affected population or separating the later analysis.

Worked classification. A contact opts out by reply while the CRM and webinar platform hold different addresses for the same person. Apply only the approved matching rule, suppress the confirmed address, and route the possible link; the coordinator cannot merge identities by intuition. The example tests whether the rule is understandable. It is not an observed result and should never appear in the findings table. Actual records may show a different pattern, and the reviewer should preserve that result even when it makes the proposed handoff less attractive.

Operating boundary. A Philippines-based specialist may collect permitted records, link identifiers, apply the codebook, maintain the screening log, flag conflicts, and prepare an exception packet. Consent validity, statutory interpretation, identity resolution exceptions, transactional-message classification, campaign purpose, remediation, legal notice, and risk acceptance remain with authorized owners. A deadline, absent owner, or familiar precedent does not transfer that authority to the coordinator.

Privacy and security. Use named accounts, least privilege, approved export methods, encrypted storage and transfer, and a written retention period. Do not copy an unrestricted inbox or an entire personnel, customer, or transaction history when a bounded event table answers the question. Delete working copies under the buyer's approved rule and report access or data-quality incidents through its existing route.

Bias and alternatives. Treat the findings as a description of the registered queue. Differences may come from work mix, source quality, system design, policy changes, shift coverage, owner availability, or missing events. They do not by themselves show that a coordinator, provider, or location caused the outcome. Use only preregistered subgroups, show small groups as counts, and suppress cells when privacy or instability requires it.

Limitations. Sending tools can sync slowly, aliases may hide identity links, transactional and marketing messages can share infrastructure, system inventories can be incomplete, and delivery logs may lag. One buyer and one operating window do not establish causality or external validity. The records cannot prove what a person knew or why an event occurred. Document any change in system, policy, staffing, volume, or access that overlaps the study so a reader can judge comparability.

Decision rule. Before collection, state the evidence needed to start a narrow pilot, repair records and measure again, keep the queue internal, or request specialist review. Include evidence coverage, unresolved risk, owner capacity, and reversibility. Speed is not enough. A quick queue with missing authority or source records is not ready to hand off.

Pilot. If the evidence supports a test, open one bounded queue with a named internal owner and backup. Record permitted actions, stop conditions, review sample, escalation time, and rollback path. Compare the pilot with the registered baseline using the same units and classes. Version any scope change instead of folding new tasks into the original measure.

Conclusion for this niche. Delegate suppression operations only when the request, identity rule, system scope, platform events, later-send checks, and exception authority remain connected. OutsourcedCompany.com readers are choosing which company function to hand off first. The process must become observable before the staffing decision: sources stay attributable, exceptions stay visible, and consequential decisions stay with the buyer's named owners.

Suppression-specific system map. Freeze the inventory of campaign platforms, CRM automations, webinar tools, uploaded audience destinations, agency senders, and manual lists that can originate marketing messages. For each destination record the identity key, scope semantics, normal propagation method, expected latency, evidence event, and accountable owner. Test the map with synthetic identities where policy permits. A platform appearing in the inventory is not evidence of successful suppression; the study needs an attributable destination event or a documented exception. Likewise, a global CRM flag is insufficient when a downstream tool can continue sending from an older audience export.

Identity and scope analysis. Treat exact-address matches, approved alias links, customer-record links, and inferred household or company relationships as different classes. Apply broader suppression only when the buyer has approved that rule. Preserve the request wording so reviewers can distinguish one newsletter, a brand, a channel, or all marketing. Record transactional-message exceptions without deciding them, and test whether the platform represents those scopes accurately. Report ambiguous identities and scopes in the denominator instead of silently choosing the broadest or narrowest interpretation. This protects both the requester and the integrity of the measurement.

Later-send investigation. Join post-request delivery events using message purpose, campaign, sender, destination, queued time, send time, and suppression-check time. A message queued before the request, a permitted transactional notice, a test, and a marketing send after confirmed propagation are materially different events. Preserve the classification rule and owner decision for each candidate. Measure time from receipt to each required destination and show the slowest unresolved destination rather than only an average. The staffing question is whether a specialist can maintain this evidence and surface failures quickly; legal conclusions, remediation, and contact decisions stay outside the delegated queue.