Track website campaign links with UTM parameters
Use separate links for placements and forward UTM parameters to your website. Compare link requests with website sessions, leads and purchases.
19 October 2026 · PAD team
On this page
Separate the shared link from website attribution
A campaign path gives you a distinct GoToApp address and request history. Website analytics needs campaign information on the destination URL. In your website project, open Advanced settings and enable Forward URL parameters before sharing a URL with UTM tags.
Example: a newsletter promoting an offer
These are illustrative addresses. Configure your real page as the project destination, and publish the GoToApp URL in the newsletter.
| Part | Example |
|---|---|
| Saved website destination | https://example.com/offer |
| Shared campaign link | https://gotoapp.store/your-project/newsletter?utm_source=newsletter&utm_medium=email&utm_campaign=october_offer |
| Check at the destination | The final page URL contains the intended utm_source, utm_medium and utm_campaign values |
Keep source, medium and campaign names consistent. Google Analytics uses these campaign parameters in acquisition reporting; see Google’s campaign URL documentation. Verify the final URL if the destination already contains campaign parameters or an email platform adds another redirect.
Which report answers which question?
| Question | Report | Limit |
|---|---|---|
| Which shared address received requests? | GoToApp link statistics | May include bots and repeat visits |
| Which campaign brought website sessions? | Website analytics acquisition report | Depends on tags, consent and analytics configuration |
| Which campaign produced leads or purchases? | Website conversion reporting or your order system | Requires the relevant events and attribution setup |
| Which link led to an app install? | Store or attribution-provider reporting | Website UTM reporting alone does not establish installs |
Test before sending the campaign
- Publish the exact tagged URL in a draft email or test placement.
- Open it from that placement and inspect the final page URL.
- Confirm the intended parameters remain after every redirect.
- Complete the form or purchase test using your own test workflow and check the appropriate website events.
- Compare the same date range and reporting timezone when reviewing results. Record the test so it is not mistaken for customer activity.
When clicks and sessions disagree
A link request may come from an email security scanner, preview bot or repeat visit. A website analytics session depends on its own collection rules and consent. A difference between these counters does not by itself prove a broken link. Test the route and inspect each system’s event definitions before estimating a loss.
Avoid personal data in shared URLs
URLs can appear in browser history, analytics and server logs. Use campaign labels rather than email addresses, names or payment details. Keep authentication and sensitive state in the destination application.
Set up your link
Use email and message campaign links and follow the website destination setup.
Questions
Does a campaign path automatically label website sessions?
Use UTM parameters and enable Forward URL parameters for website attribution. A campaign path by itself separates GoToApp request history.
Does GoToApp measure purchases?
No. Measure purchases in website analytics or your order system.
Why are link clicks higher than website sessions?
Repeat visits, automated requests, consent and different counting rules can all contribute. Check the route and both reporting definitions.
Create a GoToApp link with your destinations, then test it on the devices and channels you plan to use. Free for up to three projects.