Published 2026-11-16
For an SMM panel reseller, UTM links help distinguish visitors arriving at your own sales page from different social posts. Use them to compare sources of enquiries, then follow those enquiries through your customer records. Keep that acquisition work separate from the views, followers or other quantities submitted as panel service orders.
This guide follows a fictional reseller sharing a page about its managed ordering service through LinkedIn and Telegram. It covers link naming, enquiry checks and interpreting results. If you are still choosing your offer, first read the guide to selling SMM services to local businesses.

You need a destination page you control, access to its analytics and a working enquiry route. If a partner owns the destination, agree what reporting they can provide first. Adding labels to their URL does not give you access to their results.
Decide what a useful result means. For the reseller, it is a successfully received service enquiry, not a click on “Ask a question.” Someone can click that button, encounter a validation error and leave without sending anything.
Google lists generate_lead as a recommended event for a submitted form or information request. Recommended events require implementation; they are not automatically created by adding UTMs. Ask whoever manages your measurement to trigger the event at the confirmed success step and verify it before using the count.
A reseller landing page should explain the service scope, order requirements and support route before asking someone to enquire. Link readers to the relevant details rather than sending every campaign to a generic sign-in screen. If you use a branded storefront, the child-panel guide explains how that differs from a regular customer account. This article uses analytics on a site you control; it does not claim BulkFollows supplies enquiry tracking or a UTM builder.
Google’s campaign URL guidance recommends including utm_source, utm_medium and utm_campaign. Use utm_content to distinguish a placement or creative. Values are case-sensitive, so agree spelling before people start distributing links.
| Field | Our example | Team decision |
|---|---|---|
| Source | linkedin or telegram | Where this particular link is shared |
| Medium | social | Our label for these unpaid social placements |
| Campaign | reseller_enquiries | One name shared by both links |
| Content | launch_post or pinned_message | Which placement the link belongs to |
Keep a small link register with the destination, these four values, the planned placement and publication date. Copy the approved values rather than reconstructing them from memory. A colleague typing “Reseller_Enquiries” instead of “reseller_enquiries” creates a separate value. Agree one spelling, including capitalisation, before sharing.
The following are illustrative addresses, not live reseller pages. Both lead to the same destination, but their labels identify different distribution points.
https://example.com/reseller-services?utm_source=linkedin&utm_medium=social&utm_campaign=reseller_enquiries&utm_content=launch_post
https://example.com/reseller-services?utm_source=telegram&utm_medium=social&utm_campaign=reseller_enquiries&utm_content=pinned_message
For a fresh URL, the question mark starts the parameters; ampersands separate them. If the destination already has a query, such as ?language=en, append the tags with an ampersand instead of adding a second question mark. Google also provides a Campaign URL Builder linked from its documentation.
Give the person publishing each placement its exact link. If the LinkedIn link is accidentally used in Telegram, the labels describe what you supplied, not where you intended it to go. The link register makes that mistake easier to trace.
Test the published placement again once it is available. An editor may have shortened, replaced or copied the wrong URL between approval and publication. Checking the link in your document alone misses that last step.
For this fictional reseller setup, assume GA4 is already collecting data on the landing page. Follow Google’s Traffic acquisition instructions:
linkedin / social and telegram / social. Use Session campaign to examine reseller_enquiries; do not substitute a first-user dimension.A UTM link cannot configure a missing generate_lead event. If your measurement owner has not implemented and tested it, report visits only and keep received enquiries in a separate record. The table below assumes you have also established which sessions contained a successful enquiry; do not copy raw event totals into that column.
Illustrative report: over seven days, the reseller records the following sessions. For this example, each enquiry is counted once, each is associated with its submitting session, and no session has more than one successful enquiry. These are teaching figures, not BulkFollows results or benchmarks.
| Tagged source | Recorded sessions | Sessions with an enquiry | Enquiry-session share |
|---|---|---|---|
| 120 | 6 | 6 ÷ 120 = 5% | |
| Telegram | 80 | 8 | 8 ÷ 80 = 10% |
| Combined | 200 | 14 | 14 ÷ 200 = 7% |
The combined figure is 7%, not the simple average of 5% and 10%. The channels contributed different numbers of sessions. These figures also do not establish 200 different people or 14 paying customers.
Telegram has the higher enquiry-session share in this small example. Before moving resources, review whether those enquiries match the services the reseller can deliver, whether both placements ran for comparable periods and how much work each took. Eight enquiries can justify a closer look; they do not establish a permanent channel winner.
Suppose the same illustrative campaign produces 14 distinct enquiries, but only four customers subsequently place paid orders. Keep those four orders in your customer ledger, linked to the relevant enquiries where your records support that connection. Do not report 14 customers because the form received 14 enquiries, or count an account top-up as a completed service order.
A supplier order marked completed answers a different question: what happened to the service the reseller submitted? It does not prove which campaign acquired the customer. Use the first-order guide to understand the order workflow, and maintain campaign, customer and supplier-order records as distinct records. A UTM label is not an order ID.
If the customer returns through another route or you cannot connect their enquiry to payment reliably, record the attribution as uncertain. Do not assign the sale to whichever social post was most recent. The broader guide to marketing outcomes explains why delivered activity and customer demand need separate measures.
If a campaign row is missing, check the link actually shared, the selected date range and whether measurement worked on the destination. If visits appear but enquiries do not, check the success-event setup and the received enquiries before concluding the campaign failed.
Do not force social-platform click totals to match recorded website sessions. They are different records, and a discrepancy is a question to investigate rather than proof that either source is fraudulent. Likewise, an unrecorded enquiry is not automatically zero demand.
Finish each review with a decision and its reason: fix a broken form, correct a tag, improve the service explanation or gather another reporting period. Clean labels are useful because they help you choose the next task, not because they make every number certain.