Track Traffic From Each Post With Campaign Links

Check whether each post can carry a distinct link

Start with the placement, not the analytics. A post with its own clickable URL can use a unique campaign tag. Several posts that all say “link in bio” share one route, so a tag on that profile link identifies the profile placement, not the individual posts.

Changing the profile link’s tag whenever you publish does not solve this completely. Someone could discover an older post and then use the current profile link. Label that traffic as a profile link time window rather than assigning every visit to your newest post.

Referrers cannot reliably fill the gap. Browser policies can omit the referrer or send only the referring origin instead of a full page address. A platform hostname may tell you where a visit came from without identifying a particular post.

Choose campaign names you can read later

UTM parameters are labels added to a URL. Start with utm_source for the publishing platform, utm_medium for the channel, such as social, and utm_campaign for the distinction you want to compare. Google recommends those three parameters, and its parameter values are case-sensitive. Consistent lowercase names avoid unnecessary variations.

Use a compact pattern such as series_postid_angle. A musician might name two routes sessions_p01_rehearsal and sessions_p02_songwriting. A persistent profile link can have a separate name such as profile_instagram. The names should remain understandable after the posts are no longer fresh in your memory.

Some analytics systems support putting the post identifier in utm_content while keeping a shared campaign name. For this Unflaggable.bio workflow, put the post distinction in utm_campaign: page views can record that field. Do not assume every other UTM field has equivalent reporting support.

Build one URL and ledger entry per placement

Both posts should point to your existing creator page. Only their tracking labels need to change. For example, the rehearsal link could be https://creator.example/?utm_source=community&utm_medium=social&utm_campaign=sessions_p01_rehearsal. The songwriting link uses the same address with utm_campaign=sessions_p02_songwriting. Replace the example domain and source with your actual destination and platform.

A query begins with ?, each parameter connects to its value with =, and pairs are separated by &. If your page URL already contains a query, append the tracking parameters with & rather than adding a second ?.

Keep the links in a spreadsheet or notes document. Use content descriptions in campaign names, not audience members’ names or email addresses. A useful ledger makes publishing repeatable without requiring you to decode old tags.

• Record the post ID and its URL or identifying description.
• Save the campaign value beside the complete tagged creator page URL.
• Add the publication time and comparison window, such as each post’s first seven days.
• Leave fields for the test time, recorded page views and context such as whether the post received extra promotion.
• Create a fresh entry when you publish a new placement instead of reusing an old post’s tag.

Test the published route

A correctly written URL is only the starting point. Test it from the actual publishing placement so you check the route your audience will use, not just the version saved in your ledger.

Incomplete or incorrect tagging can leave campaign information unavailable. In Unflaggable.bio, missing campaign tags and referrers remain unknown. Keep those records separate instead of assigning them to whichever post seems most likely.

• Open the link from the published placement and confirm it reaches the intended page.
• Check that the destination URL retains the intended campaign value.
• Where the analytics interface exposes campaign information, look for the expected tag on a recorded view.
• Note your test time and any repeated tests so you can account for your own activity when reviewing small counts.

Compare recorded views with a consistent window

Illustrative worked example: a musician publishes two community posts with separate campaign links to the same unchanged creator page. During each post’s first seven days, sessions_p01_rehearsal records 48 page views and sessions_p02_songwriting records 30. Another 22 views have no campaign tag.

The rehearsal route recorded 18 more views, or 1.6 times as many as the songwriting route. That is a useful comparison of tagged traffic. It does not mean 48 different people arrived, and the 22 untagged views cannot be allocated between the posts.

Distribution matters too. Without knowing how many people saw each post, these counts cannot show which persuaded a greater share of viewers to visit. Record relevant context in your ledger, including different placements or extra promotion.

Use the result to choose a focused next test: publish another rehearsal excerpt with a fresh campaign tag and compare it over the same window. Preserve the original entry rather than rolling every rehearsal post into one label and losing the individual distinction.

Keep arrivals separate from later actions

Unflaggable.bio paid plans include analytics for page views and outbound clicks. Page views can record utm_campaign. Each recorded outbound click has its own link ID and can include the campaign and referrer hostname when available. For this task, start with campaign-tagged page views: they address the incoming route.

Outbound clicks answer a different question about what someone clicked on your page. Standard UTM parameters are forwarded to the destination, but forwarding does not establish a purchase or a cross-device journey. A recorded click is not a confirmed sale.

Unflaggable.bio is invite-only, and visitors can join the waitlist. Invited preview access should not be confused with paid analytics access.