By AP3K · English guide
Separate Delivery Health From Business Performance
An automation can deliver reliably while the offer performs poorly. It can also have a strong offer undermined by a technical failure. Report delivery health and business outcomes separately so the team chooses the right remedy.

The decision to make
Build one view for trigger matches, sends, failures and skipped actions, and another for destination engagement and qualified outcomes. Link the views by campaign where reliable identifiers exist. Do not infer a sale from a successful DM.
A practical workflow
- 1Step 1Check the technical path first.
- 2Step 2Review the destination and offer when delivery is healthy.
- 3Step 3Use actual booking or sales records for final outcomes.
Worked example
If messages send successfully but visitors abandon the landing page, rewriting trigger rules is unlikely to fix the destination problem. Inspect the page's promise, usability and next step.
What to avoid
Do not report a single blended success rate without defining its stages. Different denominators can conceal where the real problem occurs.
Where AP3K fits
Use AP3K activity to inspect the supported interaction and action stages, then use the appropriate destination or sales system for off-site outcomes. Successfully sent public replies and DMs are automated actions; they do not prove that someone read a message, booked an appointment or paid. Keep dates, units and source limitations visible. Examples in this guide illustrate reporting methods and are not AP3K customer results or forecasts.
How to judge the result
Track stage-specific rates and absolute counts. Use the weakest verified stage to choose the next investigation.
- Every metric names its source, unit and reporting period.
- Tests, incomplete observations and unknown attribution are labeled.
- The next action addresses the stage supported by the evidence.
Continue with a related guide
Use the next guide for a related decision, or browse the topic library to choose a different workflow.
Topics