The scope setting decides where a comment can start a campaign. A perfect keyword still produces the wrong experience if it listens on a post with a different offer. Choose scope by the promise in your content, rather than by how quickly you want to launch.
Use one post for a specific promise
A Reel offering a photography checklist should normally point to that checklist alone. Restricting the automation to the Reel prevents a later comment asking for a pricing guide from receiving the photography resource. It also makes testing easier because the expected source is unambiguous.
Choose the actual published media in AP3K, then compare its thumbnail and caption with the intended campaign. Similar covers and reposts are easy to confuse. A campaign name such as September camera checklist is more useful than New automation when several posts look alike.
Use Any post for a genuinely shared destination
An account-wide keyword can work for an evergreen menu or a central booking page that remains relevant across content. Its value is coverage; its cost is reduced context. Someone commenting MENU under an old announcement should still receive an appropriate menu.
Do not use Any post merely to avoid selecting media. First list every live campaign using the same keyword. Check whether a broad rule intersects with a more specific rule, and remove ambiguity before expanding scope.
Run a scope comparison
Use two posts and write down the expected result on each. For a specific-post rule, the qualifying comment should trigger only on its selected post. For Any post, verify that the same keyword makes sense on both. Use new comments from another account after activation.
- Selected post plus matching keyword: expected delivery.
- Selected post plus unrelated text: no keyword delivery.
- Different post plus matching keyword: outcome must match the chosen scope.
- Different account's post: not part of this account's configured campaign.
Expand deliberately
After the narrow campaign works, consider expanding only if the offer remains useful outside its original context. Keep a short record of which posts are meant to share the destination and who maintains it. If offers diverge, separate their keywords or scopes.
When a customer reports the wrong resource, check scope before rewriting messages. The message may be correct for the automation but the automation may be listening in the wrong place. That distinction saves a lot of unnecessary editing.
Turn the next comment into a conversation.
Choose a clear trigger, write a useful response and try your first AP3K campaign.
SHARE THIS ARTICLE
