Track Bitly and other shortened links
Create the complete labelled destination first, then shorten that link in Bitly or another service. Attriboo reads the labels on the final website page. It does not need a Bitly account connection for this basic flow, and it does not import Bitly click counts.
Instructions reviewed
Build first, shorten second
- Open Settings → Tracking links in Attriboo.
Choose the actual sharing source, such as LinkedIn post or X / Twitter post. Bitly is the shortening service, not the original marketing source.
- Enter your destination and campaign, then create the link.
Use a different campaign label for each placement you need as a separate revenue row. The optional post label is recorded but does not split campaign revenue on its own.
- Paste the entire completed URL into Bitly’s destination field.
Shorten that full URL, including the question mark and all campaign labels. Use the equivalent destination field in another shortener.
- Publish the resulting short link.
Keep a record of its destination and intended placement. Changing a short link’s destination later can change which labels future visitors receive.
https://example.com/offer?utm_source=linkedin&utm_medium=social&utm_campaign=linkedin_post_01&utm_content=founder_postDo not rely on tags added after the short link
A URL such as bit.ly/example?utm_source=linkedin is a request to the shortening service. Whether those extra parameters reach the destination depends on that service’s forwarding settings. Putting the labels in the stored full destination avoids relying on that extra forwarding behavior.
Test every redirect in the published path, including a branded short domain, HTTP-to-HTTPS redirects, a landing-page redirect and a language or device redirect. The final page must retain the source, marketing type and campaign before the tracker reads them.
What the source report will show
| Final page information | Expected result for a new visit |
|---|---|
| utm_source=linkedin and utm_medium=social | Social → LinkedIn, even if no usable browser referrer arrives. |
| utm_source=facebook and utm_medium=paid_social | Paid Ads → Meta Ads. |
| A t.co or lnkd.in referring domain without labels | The recognized social platform, with no guaranteed individual post or campaign. |
| Only a bit.ly referring domain, with no labels | A referral from that domain; it does not prove which platform originally shared it. |
| No usable source label, referrer or recognized ad signal | Direct. The original placement cannot be reconstructed from the short code alone. |
Find the visits and sales in Attriboo
- Choose the same website and dates.
Include the test visit and any later payment. Keep the same attribution model when comparing campaigns.
- Check Sources, then Campaigns or Ad ROAS.
Sources shows the platform label. Campaigns groups visits and credited revenue by utm_campaign. A campaign label is not proof that the activity was a paid ad.
- Use distinct campaign labels for separate post revenue rows.
If two posts share a campaign label, their campaign totals are combined. The optional utm_content label is recorded with activity; it does not create a separate per-post or per-ad revenue report. For paid ads, keep the campaign ID or name that matches the imported cost.
- Check a missing sale separately.
A payment can be imported without a matching visit. Consent, blocked tracking, country controls, another device, a cleared identifier or missing checkout metadata can prevent matching. A tagged link does not fix those gaps.
Test the published link
- Copy the final link from the actual post, profile or ad.
Test the published destination you control, including any shortener or redirect, rather than only the URL in your draft.
- Open it in a fresh test browser session.
Check the address after redirects. It must retain utm_source, utm_medium and utm_campaign. Give consent only through your normal website choice. Use a test location permitted by your saved country controls.
- Check a new recorded visit.
Select the matching dates and find the expected source and campaign. If you are using a browser-ignore setting, an ad blocker, cookieless mode or excluded country, the expected result may be no visitor-level journey.
- Check checkout matching only when needed.
Use your payment provider’s supported test setup or an existing payment you are authorized to inspect. Do not make an unnecessary live purchase. A working link test does not itself prove revenue matching.
Why clicks, visitors and sales will differ
A shortener measures requests to its link. Attriboo measures activity that reaches a page with its tracker and passes your collection controls. Preview bots, repeat clicks, blocked scripts, consent choices, country controls and redirects can make the counts differ.
A click is not automatically a distinct person, a recorded website visit or a payment. Attriboo needs a permitted standard visit and supported payment matching to credit revenue. Cookieless totals do not create a visitor-to-sale link. Do not add a shortener’s clicks to Attriboo’s visitor total.
You are done when
Your short link reaches a tracked page with the intended labels intact, and new permitted visits appear under the expected source and campaign.
Still need a hand?
Send a question without needing to sign in.