Connecting Maxio to Attentive

Architecture

How Maxio and Attentive actually connect

Two systems that know nothing about each other. Everything below exists to give them one shared reference.

1. Step 1

   Maxio holds the truth

   An annual contract paid upfront is one cash event and twelve revenue events. Which one you report changes every efficiency ratio you compute, and neither is wrong as long as you say which it is.

2. Step 2

   Attentive needs a click to match

   Attentive needs the subscriber's phone number, the event name and its properties. It also needs the subscriber to have consented — an event about someone who never opted in cannot legally be messaged, whatever the event says.

3. Step 3

   The identifier is the bridge

   The subscriber's phone number, captured at the visit and carried into the Maxio subscription. Without it there is nothing to join on and no tool fixes that.

4. Step 4

   The event source decides reliability

   Send new subscriptions at annual contract value, and state in the report whether the figure is billed or recognized.

5. Step 5

   Deduplication at the destination

   Attentive does not deduplicate for you. A purchase sent twice can trigger a journey twice, and the customer receives two texts. Unlike an email, a duplicate SMS costs you money per send and irritates the recipient measurably more.

Diagnose it honestly

Working vs. broken, side by side

Both states look identical from the Attentive dashboard, which is why this runs for months before anyone notices.

Diagnostic sequence

Diagnostic order

Each step rules out a class of cause. Run them in order and the last one usually has a single explanation standing.

1. 1

   Count subscriptions carrying the subscriber's phone number

   The ceiling on everything else. Do this before debugging anything downstream.

2. 2

   Follow one real conversion end to end

   From the ad click through Maxio and into Attentive.

3. 3

   Establish which basis the conversion value uses and write it down

   This is a documentation fix rather than a technical one, and it resolves more arguments than most tracking work.

4. 4

   Verify that events for non-consented customers cannot trigger a send

   Check the journey's entry conditions, not the event pipeline. The pipeline will happily deliver an event about someone who never opted in; the journey is what must refuse to act on it.

5. 5

   Read the match rate, not the success message

   Attentive shows the event on the subscriber record and the journey it triggered. Check the subscriber's consent status alongside, because that is the field that decides whether anything should have happened.

Source-of-truth validation

How it gets proven

Against Maxio's own records, not against either platform's dashboard.

• The subscriber's phone number confirmed present on a live subscription.
• A real conversion followed from click through Maxio to Attentive.
• Events confirmed on subscriber records with consent state verified, and a test proving a non-consented profile does not trigger a send.
• New subscription contract value reconciled against imported conversions, with the basis stated explicitly.
• Reconciled over a fully closed window, matched per record rather than on totals.
• Re-checked 30 days later.

Straight talk

When you don't need this

Worth reading before paying anyone, including us.

• If Attentive already reports conversions that reconcile against Maxio's records within a few percent, this join is working and there is nothing to buy.
• Measure identifier coverage yourself first — pull your last hundred subscriptions and count how many carry the subscriber's phone number. Ten minutes, free, and it tells you whether any of this is worth doing.
• For monthly-billed businesses the two figures nearly coincide and this distinction costs more to maintain than it returns.
• If you do not have a consented SMS list, the integration is the least of the work. Building the list compliantly comes first, and no event pipeline substitutes for it.