The external send
A campaign to a live audience is a data-egress event at scale. Wrong segment, unsuppressed list, unapproved claim, wrong region — all irreversible the moment it leaves.
Marketing authority
Approval is not release.
Your review process decides what may go out. Nothing between that decision and the send enforces it — least of all when the sender is a workflow, an automation, or an agent holding a platform credential. A send cannot be recalled.
What is actually at stake
Three marketing actions you cannot take back.
The audience export
Pushing a segment to an ad platform discloses personal data to a third party. It is routine, it is rarely treated as a disclosure, and it is exactly what a transfer obligation attaches to.
The reviewed asset
Material that cleared review is approved as a specific version, for a specific channel and audience, until a specific date. What ships is frequently not that.
The boundary that matters
Draft freely. Sending is the governed act.
Composition is not the consequence. An agent, an automation, or a person may draft, iterate and stage without any gate at all — and then the send, the export, or the publication is evaluated against who holds authority for it, what was approved, and whether that approval still stands. Holding an API token for the marketing platform is not authority to release.
A permit is bound to the exact recipient set and the exact content authorized. Change either after approval and the permit no longer verifies — the release fails closed rather than going out under an approval that no longer describes it.
Acceptance pattern
Prove an authorized action can proceed, an unauthorized action is refused, missing approval is refused, and changed or replayed work is refused. Evidence should show exactly which stage was established.
Regulated promotional release
Your review system approved the asset. It did not send it.
In regulated promotion the approval is already mandatory and already rigorous — medical, legal and regulatory sign-off, an approval record, a scoped channel and audience, an expiry. That review is not the gap.
The gap is everything after it: an approved asset modified in the campaign builder, an expired approval used one more time, an asset cleared for one channel deployed in another, a variant that never went back through review. The review system is the system of record for what was approved. It does not hold the send.
AtlaSent sits at that release boundary and consumes the approval as a trusted assertion — binding the permit to the approved version, channel, audience and expiry, so a release that no longer matches its approval does not go out.
Consumed, not replaced
Your promotional review platform stays the system of record for approval, and your marketing platform stays the system that sends. AtlaSent adds the decision between them and the evidence afterwards. Any specific platform integration is engagement work, scoped with you — not a capability to assume from this page.
What this is not
We do not review your copy.
AtlaSent performs no brand-safety scanning, no tone or sentiment checking, no claims-language review, no output filtering, and no campaign analytics or attribution. Those are content and observability problems, served by other vendors, and doing them badly would not help you.
The distinction is deliberate and it is the reason this control holds: a content check is a probabilistic opinion about words. An authorization decision is a deterministic answer about a consequence — and it stays correct whether the copy was written by your best strategist or generated at three in the morning by an agent. We do not make the copy safe. We make the release withholdable, and we leave evidence of who authorized it.