An Adobe Campaign SMS integration, or one for any enterprise marketing automation suite, comes down to a connector. The suite decides who gets a message and when. A texting API delivers it, receives the replies and reports what happened. The hard part isn't the send. It's keeping consent and opt-outs identical on both sides.

This guide is for developers and platform teams who own that connector. We'll describe the pattern in general terms, since the exact screens and options differ by product version and edition, and check your vendor's current documentation for those.

The general pattern for an external SMS connector

Enterprise campaign tools usually model SMS as a delivery channel with a connection to an outside provider. You define the connection, map message content and recipient fields to it, and let the tool run its normal targeting and scheduling. Many suites also let you point that channel at a custom HTTP endpoint instead of a built-in provider connector. If yours does, it's often the quickest route. If it doesn't, an automation layer or a small middleware service sits between the suite and the API.

Either way, the shape is the same:

  1. The suite builds a delivery: a list of recipients, a message body and a send time.
  2. Your connector turns each recipient into one API request.
  3. The API responds with an accepted or refused result per recipient.
  4. Delivery reports and replies come back to your connector, which writes them to the suite's logs and profiles.

Ready has no native Adobe Campaign connector, so the connector is yours to build. The texting side is a plain REST API with webhooks, which keeps that build small.

What the connector sends

For one recipient, the send is one request:

POST https://api.tryready.com/v1/messages
X-API-Key: <key>
Idempotency-Key: <delivery ID plus recipient ID>
{"to": "+12125550199", "body": "Acme: your plan renews Friday. Manage it any time in your account. Reply STOP to opt out.", "consent_attested": true}

For many recipients in one delivery, POST /v1/messages/bulk takes up to 100 numbers per call with a shared body, so split a larger delivery into batches. If each message is personalized, one request per recipient is simpler.

Build the Idempotency-Key from the delivery and the recipient so a retried batch never sends twice. That's the single most useful habit for any suite that re-runs failed deliveries. See SMS API idempotency and duplicate texts for the details.

Set consent_attested to true only when your suite's own consent field says the recipient agreed. Reference: docs.tryready.com/api/messages and docs.tryready.com/api/bulk-messages.

Consent sync

Consent lives in your suite's profile data, and it should stay there. Ready stores no per-contact consent record (the exception is a sign-up on a Ready-hosted opt-in page). The attestation on a send is your statement that the recipient agreed, recorded for a bulk or API send that sets consent_attested: who sent it, to how many and when. It isn't a copy of when and how each person opted in.

So the rule for the connector is simple: the audience query is the gate. Build the SMS audience from profiles with a texting consent flag, and keep these things in the profile:

  • The consent timestamp and the form or channel it came from.
  • The exact wording shown at the time, or a version ID that maps to it.
  • The business name the person agreed to hear from.
  • A separate flag from email consent, since agreeing to one isn't agreeing to the other.

A connector that sends to anyone with a phone number and no consent flag is where enterprise programs get into trouble. Our SMS consent record schema for developers lays out fields worth storing.

Opt-out sync

Opt-outs run in both directions, and the direction people forget is inbound. When a recipient replies STOP, Ready honors it and blocks that number in the sub-account that received it. Clear phrases like "please stop texting me" are caught too. Your suite doesn't know any of that happened unless you tell it.

Three ways to close the loop:

MethodHow it worksTradeoff
Inbound webhookReady calls your connector on a reply, and the connector flags the profileNear real time, needs an endpoint
Check before sendThe connector calls GET /v1/opt-outs/:phone for each number before a deliveryAlways current, one extra call per number
Scheduled exportA job reads GET /v1/opt-outs and writes flags to profilesSimple, but only as fresh as the last run

Use more than one. The plain GET /v1/opt-outs list covers this account's opted-out contacts only. It leaves out a STOP from a deleted contact, a dialer do-not-call entry and a STOP held on another account in the same family, so it isn't a complete mirror on its own. Adding ?scope=all widens it to the account's whole Ban list, and the per-number check is the final word before a send, especially when you migrate from another provider. See handling SMS opt-outs and docs.tryready.com/api/opt-outs.

Inbound replies and the webhook setup are covered in receiving SMS with inbound webhooks, and the docs quickstart at docs.tryready.com/api#quickstart walks through creating one.

Registration, sub-accounts and quiet hours

Enterprise programs usually text for several brands or business units. Ready gives each its own sub-account with its own numbers and 10DLC registration, so a brand's opt-outs and reputation stay apart. The registration is $25 a month per customer (the brand and its first campaign), $20 a month for each extra campaign, and $2 a month per number. Most approvals take 2 to 7 days, and it can be filed through the API: see the 10DLC registration API guide.

Quiet hours follow the recipient's area. Campaigns wait up to 24 hours for the window, but an API text is held only if the window opens within 6 hours. Otherwise the API answers 409 QUIET_HOURS_BLOCK and the text isn't sent, unless the request carries hold_until_allowed: true. A suite that fires a delivery at its own scheduled time needs to handle that refusal.

Pricing is $0.0075 a segment plus a $0.0045 carrier fee. Enterprise terms are negotiated, so talk to us if your volume or contract needs differ.

A cutover checklist

Before the first live delivery:

  1. Run the audience query and confirm every row has a consent flag, a timestamp and a source.
  2. Send to a few test numbers you own, including one that then replies STOP.
  3. Confirm the STOP shows up in your suite's profile within the time you've promised.
  4. Re-send the same delivery ID and confirm nothing is sent twice.
  5. Check what the connector does with a refusal, such as an opted-out number or a quiet-hours refusal.
  6. Keep PHI, diagnoses and test results out of message bodies. Ready isn't HIPAA compliant and doesn't sign BAAs.

Frequently asked questions

Does Ready have a native Adobe Campaign connector?

No. You build a connector or use an automation layer that calls the Ready REST API. The API handles sends, replies, opt-outs and registration.

Where should consent be stored?

In your suite's profile data, with a timestamp, a source and the wording shown. Ready records the sender's attestation on a send, not each person's opt-in.

How do opt-outs get back into the suite?

Through an inbound webhook, a per-number check before each send, or a scheduled export of the opt-out list. Use at least two of them.

Next step

Start with one brand, one audience and one test delivery to your own phone, including a STOP reply. When the loop closes, sign up, add a card and a number, and run it.