Map each component to a target
Member-related services concern the eligible community, while views and reactions concern specified messages. Record those links separately and check the accepted format for each component. A channel URL should not be assumed to identify every message included in the package.
Compare quantities independently
Write the member quantity, views per message and reaction allocation on separate lines. Adding them into one engagement total obscures unlike units. Check whether message-level quantities are per post or shared across a defined list before calculating the complete campaign scope.
Review component conditions
Timing, minimums and coverage may differ across the bundle's parts. Ask how incomplete components are recorded and treated under the offer. A completed member component does not establish completion of the message actions, even if they share one checkout transaction.
Decision checklist
| Decision | What to check |
|---|---|
| Members | Community-level quantity |
| Views | Specified message allocation |
| Reactions | Action type and distribution |
Worked example
A hypothetical bundle includes 100 members, 500 views on each of two posts and 40 reactions on one post. Those are three separate specifications. Compare another offer only after matching the same targets, quantities and relevant conditions for all components.
Example figures explain the decision; they are not current prices or promised results.