Overview
Relay links sit between a user and your destination page. When someone clicks, Relay records the click, fires any configured ad platform pixels, appends UTM parameters, and redirects to your final URL. All of this happens in under 100 milliseconds so the user never notices they passed through a redirect.
The result is attribution you can count on. Even if the destination page has ad blockers, CSP restrictions, or a CMP that blocks pixels on first load, you still captured the click signal at the Relay layer. For ad conversion tracking that needs to fire regardless of the landing page's quirks, Relay is the reliable path.
Navigate to Links
Open Relay > Links from the left sidebar. The Links page shows every short link you've created in the current property, with click counts, destination URLs, and campaign assignment visible at a glance. Search and filtering make it easy to find a specific link in a long list.
Click Add Link to start a new one. If you've already created a campaign, select it early so the pixel defaults pre-populate.
Enter the destination URL
Paste the full URL where users should end up after clicking. Include the protocol (https://) and any existing query strings. Relay preserves existing query parameters and merges its own UTM stamping on top, so you don't have to strip anything first.
If the destination URL changes later (a landing page redesigns, a product page moves), edit the link rather than creating a new one. All existing short URLs keep working; only the target updates. This is one of the core reasons to use Relay instead of hardcoding ad destinations.
Configure pixels
Select which marketing pixels fire when a user clicks this link. Supported platforms include Meta, Google Ads, TikTok, LinkedIn, and Floodlight. Every pixel fires server-side from the Relay redirect handler before the redirect is issued, which means pixel calls aren't subject to the destination site's CSP, ad blockers, or CMP state.
For each pixel, configure the specific event or conversion action. On Meta that's typically a Lead or ViewContent event. On Google Ads it's a conversion action label. Relay deduplicates per-session so a user clicking the same link twice in quick succession doesn't double-fire your conversions.
Add UTM parameters
Set UTM source, medium, campaign, term, and content. Relay appends these to the destination URL so your analytics (GA4, Lens, whatever) attributes the session correctly. Consistency matters here: pick a taxonomy (lowercase, underscores, no spaces) and stick with it, because GA4 treats google_ads and Google Ads as separate sources.
Relay also captures GCLID and FBCLID automatically if they're present on the incoming click. These IDs are what Google and Meta use to reconcile ad spend with on-site conversions, and preserving them through the redirect keeps that attribution chain intact.
Save and share
Save the link. Relay generates a short URL on the pxl.me domain (something like https://pxl.me/abc123) that you can share anywhere. The URL is clickable on any platform that accepts links, and the tracking fires no matter who clicks.
Every click streams into the Relay dashboard in near-real-time. You can watch clicks roll in from a live campaign launch and confirm the pixels are firing by checking the respective ad platform's events manager within seconds.
Organize related links into campaigns to share pixel configurations across many links and get rollup reporting. Every link automatically generates a QR code, which is handy for bridging offline surfaces like print ads, packaging, and event signage into your digital attribution. For partner or exclusive content, password-protect the link so only intended viewers can continue past the redirect.
Troubleshooting
Clicks tracked but ad platform conversions missing
This usually means the pixel configuration is off. Verify the correct Pixel ID or Conversion Action is selected, and confirm the event name matches what the ad platform expects (case-sensitive on some platforms). Use the ad platform's Test Events or diagnostic tool to confirm Relay's server-side calls are landing.
UTM parameters missing on the destination page
Check whether your destination URL already had conflicting UTM parameters. Relay merges, but if you hardcoded UTMs into the destination, those win. Leave the destination clean and let Relay do the stamping. Also verify the destination page isn't stripping query parameters via a server redirect or single-page app router quirk.
Link redirects to the wrong destination
You probably edited the destination but are looking at a cached browser result. Short URLs are cached aggressively by browsers and intermediate proxies. Force a refresh or test in an incognito window to confirm the live behavior.