Identify the page hierarchy
List the pages involved and their actual public references, including the parent brand and any separate business units. Similar names or shared logos are not sufficient identifiers. Confirm which entity owns each approved target before choosing an account-level or post-level service.
Budget each requested action
Assign a quantity and service ID to every supported target. If the brief covers reactions on posts from several pages, include those post links separately. A company-wide total does not explain how the purchase should be distributed across different publications or page identities.
Review results per target
Attach each order reference and observed result to its original row. Keep an aggregate campaign total only as an additional view. This makes it possible to identify a delayed or incorrect line without assuming that activity on the parent page resolves every subsidiary request.
Decision checklist
| Decision | What to check |
|---|---|
| Identity | Exact authorized page |
| Allocation | Quantity per target |
| Review | Order reference per line |
Worked example
For a hypothetical group with three business-unit pages, 300 requested actions could mean 100 each or a weighted allocation. The purchasing sheet must state which interpretation is approved and whether every line satisfies the selected service's target and quantity requirements.
Example figures explain the decision; they are not current prices or promised results.