Free tool
Pick the outcome. Read the metric.
Clicks, follows, leads, or replies. Each one maps to a number DripDM can show.
3 minute read
Watch link taps. DripDM counts a tap on each tracked link. That tells you which keyword earns the click.
How to read the result
Likes are the wrong score when the post exists to send a link.
The tool runs in your browser. It does not send the numbers to DripDM.
Choose the outcome before reading a dashboard
Select clicks, follows, leads, or replies. The widget gives a short recommendation based on that choice; it is not a scored examination, account audit, or automated analytics report. The useful question is what the next post asks someone to do. If the offer is a guide link, taps are relevant. If the purpose is a callback request, captured contact information matters. Replies can show whether the conversation is continuing, but they are not automatically qualified leads.
Using the inputs and result
Write a one-sentence campaign objective, choose the closest option, and define the observable completion event. A booking-link tap should be distinguished from a confirmed appointment. A lead record should be distinguished from later marketing consent. Follower changes should not automatically be attributed to a gate. Decide where the confirming evidence lives: the DripDM handoff, the lead record, the booking system, or the commerce destination. Keep that definition consistent throughout the campaign.
Limits and result checks
Use secondary metrics to diagnose the journey without replacing the primary outcome. Public likes can help describe response while failing to explain a broken private link. A successful send can still produce no destination action. Review eligible requests, delivery problems, the message, and the landing page before blaming one number. This quiz does not promise that every suggested measurement has a dedicated unique-user or causal-attribution dashboard. Check the implemented product count and label exactly what you observed.
Write a completion definition for the chosen outcome
For clicks, identify the link and reporting period. For leads, define the required field and disclosed purpose. For replies, distinguish useful conversation from a generic reaction. For follows, explain how you observed a change without assuming causation from a gate. Keep that definition beside the chosen campaign objective. If the desired event happens in a booking or commerce system, inspect that system too. This turns the recommendation into a useful measurement plan rather than assuming one selector created all the analytics needed to evaluate a launch.
Questions
No. Copy the result into your caption, bio, or a DripDM rule.
It can answer a narrowly defined objective, but it rarely explains the whole journey. Pick one primary outcome and a few diagnostic steps. Verify purchases or bookings in their own systems rather than treating likes, replies, or taps as interchangeable proof of success.
No. The implemented widget is an outcome selector with a short recommendation. It does not grade knowledge, fetch account performance, or create a dashboard. Define and verify the completion event in the relevant system.