Server-side, nothing in the browser
Hits go from Letlink’s servers to your tracking server’s /b/ss/ endpoint, so they arrive when the visitor blocks trackers or opens the link in an in-app browser.
Adobe Analytics
Letlink records each short-link click and each approved conversion in your Adobe Analytics report suite through Adobe’s data collection request, sent from its own servers rather than the visitor’s browser.
Short answer
Adobe Analytics link tracking records link clicks as hits in a report suite so they can be analysed with the rest of your traffic. Letlink sends every recorded click as a custom link hit named after the short code, sales as purchase events with your order ID and revenue, and leads and sign-ups as the success events you choose, all server-side. It needs a tracking server and a report suite ID and is on Growth at $8.90 a month and Ultimate at $39.90.
Features
Hits go from Letlink’s servers to your tracking server’s /b/ss/ endpoint, so they arrive when the visitor blocks trackers or opens the link in an in-app browser.
Each recorded click is a custom link hit named Link click: <short code>, with the link name as pageName, the short URL and the referrer, plus your click success event when you set one.
Approved sales arrive as events=purchase with your order ID as purchaseID, the short code and value in products, and the currency. Adobe converts it if it differs from the suite’s base currency.
Name the success events — event1 to event1000 — for leads and sign-ups, enabled first on the report suite. Without one, that kind of conversion is skipped.
The visitor’s IP and user agent are forwarded in headers so Adobe resolves location and device, and the visitor ID is the same device fingerprint Letlink uses for unique visitors.
Separate report suite IDs with commas to send the same hits to all of them.
Custom conversion events are not sent — map them to a lead or sign-up event instead. Timestamp-required report suites drop these hits, so use a timestamp-optional one.
Use cases
Short-link clicks from email, print and social sit in the same Workspace projects as the rest of your digital traffic.
Sales reported by postback from a partner or marketplace reach Adobe as purchase events tied to the short code.
Scans of printed codes become custom link hits, so print campaigns appear next to online ones.
Copy the trackingServer value from your AppMeasurement or Web SDK setup, for example example.sc.omtrdc.net, and the report suite ID.
If you want leads, sign-ups or clicks counted as success events, enable them under Admin → Report suites → Edit settings → Conversion → Success events.
On Growth or Ultimate, open Integrations → Adobe Analytics, enter the tracking server hostname, the report suite ID and any success events, and save.
Press Send test event and check Real-time reports or the Experience Cloud debugger — Adobe answers every request with a 1×1 pixel even when it discards the hit.
Pricing
Start free with no card. Paying yearly takes 20% off every paid plan.
| Plan | Free | Solo | Growth Most popular | Ultimate |
|---|---|---|---|---|
| Price per month | $0 | $3.90 | $8.90 | $39.90 |
| Active links | 1,000 | 3,000 | 8,000 | 15,000 |
| Tracked clicks a month | 1,000 | 10,000 | 100,000 | Unlimited |
| Custom domains | — | 1 | 3 | 50 |
| Team members | 1 | 1 | 5 | 50 |
| Click history | 7 days | 30 days | 365 days | Unlimited |
Mobile app
Create short links, watch clicks arrive live and design QR codes from your phone. Free on iPhone, iPad and Android.
Connect Adobe Analytics under Integrations with your tracking server and report suite ID. Letlink then sends every recorded click to the suite server-side as a custom link hit named after the short code, and approved conversions as purchase or success events. It is on Growth at $8.90 a month and Ultimate at $39.90.
Yes, always — Adobe receives approved conversions even when the workspace does not forward them to the ad platforms. Sales arrive as purchase with order ID and revenue; leads and sign-ups arrive as the success events you set, and are skipped when none is set. Custom events are not sent.
No. Nothing runs in the visitor’s browser. Letlink sends Adobe’s data collection image request from its own servers, forwarding the visitor’s IP and user agent so Adobe can resolve geography and devices.
Adobe answers every image request with a 1×1 pixel, even when it discards the hit, so a successful test only proves the server is reachable. Check that the report suite is not timestamp-required and that any success events you named are enabled on it, then confirm in Real-time reports.
Yes. The integration forwards the visitor’s IP address and user agent so Adobe can resolve location and device, and you are responsible for having a lawful basis for that. Check your privacy notice and regional rules before enabling it in production.
Get started
The free plan needs no credit card and has no trial clock. Upgrade when you need your own domain, more links or your team.