Maintenance
Part of Campaign management tools: what they take over, step by step
What platform support means: five depths to test before buying
What campaign management tools mean by platform support: the five depths of connection, why access can be withdrawn, and how to test coverage yourself.
Every campaign management product in this market claims to support the platforms you work on, whether that is Instagram, TikTok or YouTube. This page does not rank vendors; it gives you the test to run on any of them. The word support covers at least five different depths of connection, and the difference between them decides whether your team is reading numbers automatically or pasting screenshots into a folder.
Nobody lies about this. They simply use one word for five things, and buyers rarely ask which one they are being sold. The wider job these products do is set out in the pillar guide to campaign workflow tools.
What to take away
- Ask what the connection actually doesread metrics, capture posts, publish, or spend money. The four are unrelated capabilities.
- Every connection is permission granted by somebody else, and it can be narrowed or withdrawn without notice.
- A tool that handles manual entry gracefully is more useful than one that assumes every connection will keep working.
Five depths behind one word
What you can actually do
- A link field
- Store a URL and open it. Nothing is read
- Manual capture
- A person records what went live, with a screenshot and a date
- Read access to metrics
- Pull public or granted figures on a schedule
- Content capture and monitoring
- Detect posts as they appear, keep a copy, notice deletions
- Publishing and paid amplification
- Post on behalf of an account, or run its content as advertising
What takes it away
- A link field
- Nothing, and nothing is gained either
- Manual capture
- Only staff time
- Read access to metrics
- A change to what the platform exposes, or a revoked permission
- Content capture and monitoring
- Access limits, private accounts, and unsupported formats
- Publishing and paid amplification
- Account type restrictions, permission scopes, and approval from the account holder
Every row above the second depends on an API somebody else publishes and can withdraw. Most buyers assume they are getting the fourth row and are actually being sold the third for some platforms and the second for others.
Five depths of platform support
Depth
- Link field
- Store URL, open it
- Manual capture
- Person records post
- Read metrics
- Pull figures on schedule
- Content monitoring
- Detect posts, notice deletions
- Publishing and ads
- Post or amplify
What you can do
- Link field
- Nothing gained
- Manual capture
- Staff time only
- Read metrics
- Exposure change, revoked permission
- Content monitoring
- Access limits, private accounts
- Publishing and ads
- Account type, scopes, approval
What takes it away
- Link field
- Manual capture
- Read metrics
- Content monitoring
- Publishing and ads
Ask for the answer platform by platform, in writing, because the coverage is almost never uniform across a vendor's supported list. Where a campaign runs on tracked links and codes rather than posts, the connection question becomes a reconciliation one, covered in the guide to affiliate tracking.
Permission is the thing you are actually buying
A connection is not a technical feature owned by your vendor. It is access granted by a platform, usually delegated by a creator, and it comes with conditions attached.
Three consequences follow. First, the creator must grant something. A connection that requires their cooperation will not cover those who decline.
Second, grants expire and break silently. A dashboard can show last week's number as current. Third, the platform can change what it exposes anytime, affecting every vendor at once, not merely the one you chose.
Even where access holds, rate limiting decides how fresh the numbers can be, which is why a dashboard refresh interval is a contract term in disguise.
YouTube shows both points in its own YouTube Data API overview for developers. Projects that enable the YouTube Data API get a default quota of 100 search.list calls, 100 videos.insert calls and 10,000 units per day combined for all other endpoints, and Google states that the default quota is subject to change. Every request costs at least one quota point, including invalid ones. A tool that reads YouTube for many creators shares that daily budget across all of them, so ask the vendor how it allocates quota and what happens to your refresh rate when it runs out.
Ask what happens on the day a connection fails: whether anyone is told, whether the record shows a gap or an old value, and how the tool backfills once access returns. A silent gap is worse than an obvious one, because the report still looks complete.
The same dependency shapes the search side of the stack, where an index built on granted access can only see the creators who granted it, as described in the guide to how discovery data is built.
Manual capture is a feature
Vendors are embarrassed by manual entry and they should not be. Some platforms will never be readable, some creators will not connect their accounts, and some formats disappear before anyone captures them.
Judge the manual path properly. Can a person record a post with a link, a screenshot, a date and a note in under a minute? Do manually entered posts appear in reports beside automatically captured ones, or in a second-class list nobody reads? Can a client tell the difference, and should they?
The teams that stay accurate are the ones whose tools make the fallback fast. The teams that drift are the ones whose tools treat manual entry as a failure state.
Testing coverage claims
Do this in a trial, on your own accounts, not in a demo.
Test coverage claims in a trial
- Connect most-used and least-used platforms
- Have a creator connect their own account
- Post something, then delete it
- Compare tool metric with platform view
- Try an unmentioned format
- Revoke a permission on purpose
- Write results down with the date
- Connect the platform you use most and the one you use least. The second is where the claim breaks.
- Have a creator connect their own account, and watch how long the grant takes and what it asks them to approve. If the flow is confusing, half your partners will not complete it.
- Post something, then delete it. Does the tool notice the deletion, and does the record keep what was there?
- Look at a metric in the tool and the same metric in the platform's own view on the same day. Differences are normal and the explanation matters, since definitions and time zones move numbers, which is the argument in the guide to analytics layers.
- Try a format the vendor did not mentiona live broadcast, a story that expires, a collaborative post. Coverage claims are usually written around standard formats.
- Revoke a permission on purpose and see what the tool does about it.
Write the results down with the date. This is exactly the area where a six-month-old note is worthless, because platform access can change without notice. A useful record has one line per platform and vendor, with six fields:
- Platform
- YouTube, Instagram, TikTok or whichever you tested, by name.
- Vendor
- the tool on trial.
- Depth reached
- one of the five depths above.
- Account type tested
- business, creator or personal.
- Date tested
- the day of the test, not the day of the demo.
- Revocation result
- whether the tool flagged the gap or kept showing the old number.
Coverage is not the same in every market
A tool that reads everything in one country may read far less in another, and this rarely appears in a feature list. Account types matter too: business, creator and personal accounts expose different things, and a partner who runs a personal account may be unable to grant what your reporting assumes.
Where content is being licensed for you to re-run rather than just tracked, none of this connection depth helps, since the question becomes rights and delivery of files rather than monitoring, which is covered in the guide to licensed content.
Buy for the seams, not the badge list
A long list of supported platforms is a weak signal, because it counts the first two depths alongside the last two. What separates products is what happens at the edges: failed connections, deleted posts, unusual formats, and the day a platform changes something for everyone.
That is also where a purchase should be scoped, since a tool bought for tracking alone leaves contracts, payments and rights somewhere else, and each of those boundaries is a place your record splits.
Common questions
Is an official partnership with a platform worth paying for?
It usually means more reliable access and sometimes access to data that others cannot read. It does not guarantee continuity, and it should not be the deciding factor on its own.
Should we require creators to connect their accounts?
Ask, explain what it grants, and accept refusal gracefully. Making it a contractual requirement narrows your candidate pool for a reporting convenience, and represented creators will often decline as a matter of policy.
Our numbers do not match the platform's. Which is right?
Usually both, under different definitions. Compare the definitions, the date boundaries and the time zones before you compare the figures, and settle which version goes in client reports.
How much should platform coverage weigh in the decision?
Heavily if tracking is your bottleneck. Barely at all if your bottleneck is contracts and payment, which it more often is.
