Delivery Log

Every campaign writes one log entry per group. When something goes wrong, you can look for the pattern instead of guessing.

Status types

• Success: post live
• Pending: waiting in the group admin approval queue
• Rejected: declined by an admin or by policy
• Failed: technical or session error

Why marketers care

Without a status for each group, you cannot tell which communities saw your offer, which admins sat on it, or which rules you broke. The log answers all three. That protects your account health, because you stop repeating what got you rejected, and it gives you something concrete to change in next week’s copy.

Common mistakes

• Checking the log a week later, after the useful detail has gone stale
• Reporting pending posts to clients as delivered
• Leaving a group that fails every time in the bundle
• Assuming that “sent” in the composer means “visible in the group”

Example in practice

A launch campaign goes to 35 groups. The log shows 29 delivered, 4 pending, and 2 rejected. Both rejections give the same reason: links in the post body. You move the URL to the first comment for those groups, remove one group that has now rejected you three times in a row, and schedule a smaller follow-up. The next morning the four pending posts flip to success after admins approve them overnight. Sales gets a one-page summary of which groups actually saw the offer.

In MaherPost

The log updates live while a campaign composer run is in progress. Each row shows the timestamp, group name, status, and an error hint where one applies. Export to CSV for client reports, or filter by client workspace if you run campaigns for several brands at once. Failed rows count toward the Account Health score on your next campaign. History is kept for as long as the account is active. Check it within 24 hours so pending posts do not surprise you later.

Related reading

• Avoid Facebook group post rejection
• Agency client reporting playbook
• Post rejection glossary
• Group admin approval
• Facebook group marketing