Track website visits from your social posts.

Tag the website link you share, test the landing page and find those tags in your analytics. Reuse one naming convention to compare posts.

Reviewed · Sources

Put it into practice.

  1. Choose the landing page.

    Link to the page that answers the post’s promise. Open it on a phone. If the caption cannot provide the link you need, choose an available profile or other placement and label it accurately.

  2. Build a tagged link.

    Google recommends utm_source, utm_medium and utm_campaign when adding campaign parameters to website URLs. Use the link builder on this page. Name the source for the platform and the campaign for the activity. UTM parameter values are case sensitive. Keep names lowercase and reuse the same spelling.

  3. Test the actual route.

    Open the link from its intended placement. Check that redirects preserve the tags and the correct page loads. Verify the test visit in your analytics, allowing for its processing delay and your site’s consent settings. Record which visit was your test.

  4. Read the campaign report.

    In Google Analytics, the Traffic acquisition report includes Session source/medium and Session campaign. Compare equivalent date ranges. For Sprid’s social traffic view, follow the PostHog setup guide: This view requires connected PostHog and the app’s website URL.

One link for a release post.

Fictional app and campaign. Replace the example address with your own working page.

Destination
https://example.com/new-feature
Campaign tags
utm_source=linkedin · utm_medium=social · utm_campaign=autumn_release
Content label
utm_content=feature_demo distinguishes this creative in reports that expose it.
Check
Find linkedin / social and autumn_release in the report after a verified test visit.

Use the website address readers should open. The link is built in your browser.

Try it with your agent.

Paste into your agent
Create a tagged website link for [page] shared on [platform and placement]. Use source [source], medium [medium], campaign [campaign] and content [creative]. Keep our existing naming convention. Explain how to verify the tags in [analytics provider]. When reviewing results, separate measured sessions from signups and purchases. State missing tracking and avoid assigning shared profile-link visits to one post.

Use the right link for the question.

The builder labels campaigns. For Sprid’s per-post matching, use its dedicated post link; adding utm_content alone does not identify a Sprid post. Sprid keeps shared bio-link traffic at channel level; identifying one publish requires its dedicated tagged link.

Do UTM tags track sales or app installs?

Website campaign tags identify a traffic source. Purchases and native installs need their own measurement and attribution. Define the outcome before reporting a conversion rate.

Can I add tags after a post is live?

You can update a link where its placement allows editing. Start evaluating the new tags from that change; they cannot recover the tags missing from earlier visits.

Sources and what was checked.

  1. Google recommends utm_source, utm_medium and utm_campaign when adding campaign parameters to website URLs.

    Documentation reviewed · Checked

    GA4 website campaign reporting

    Does not establish attribution for native app installations.

  2. UTM parameter values are case sensitive.

    Documentation reviewed · Checked

    GA4 URL parameters

    Lowercase is a naming recommendation; it is not a technical requirement.

  3. In Google Analytics, the Traffic acquisition report includes Session source/medium and Session campaign.

    Documentation reviewed · Checked

    GA4 website manual campaign reporting, including utm_content as a creative label.

    Analytics must collect the visit; tags alone do not install tracking or prove a purchase. Reports can expose different dimensions.

  4. This view requires connected PostHog and the app’s website URL.

    Implementation reviewed · Checked

    Sprid social traffic comparison specifically; general website totals can use other providers.

    Code and documentation inspected. No live tracking or connected report was tested for this guide.

  5. Sprid keeps shared bio-link traffic at channel level; identifying one publish requires its dedicated tagged link.

    Implementation reviewed · Checked

    Sprid social traffic per-publish attribution; ordinary UTM creative labels alone are not Sprid publish IDs.

    Website session evidence cannot establish native installs or joined purchase attribution.