Write each action separately
Treat every included metric as its own line item. A package labeled total engagement may combine unlike actions or use a definition that differs from your reporting. Ask for a breakdown instead of interpreting the largest displayed number as the quantity of your preferred action.
Match conditions as well as counts
Compare compatible targets, quantity limits, timing and any replacement coverage for each component. Two packages with the same action quantities may still have different requirements. This matters when one component is essential to the brief and others are optional.
Report component completion
Keep the order record tied to each stated action where the panel provides that detail. A rising view counter does not establish delivery of the repost component. Describe the evidence available for each metric without treating one completed component as proof of the entire bundle.
Decision checklist
| Decision | What to check |
|---|---|
| Views | Separate measured unit |
| Likes | Separate requested quantity |
| Reposts | Separate delivery scope |
Worked example
A hypothetical bundle includes 2,000 views, 100 likes and 20 reposts. Calling it 2,120 equivalent engagements hides the different units. Compare its cost against the same three requested components, and state the quantities separately in the client brief.
Example figures explain the decision; they are not current prices or promised results.