How to Track Trade Show QR Codes by Placement in GA4

A booth sign and a takeaway card can point to the same lead form. If you print the same QR code on both, the destination URL gives you no way to tell them apart later. Before sending the artwork to print, decide which placements you want to compare, give each one a tagged URL and scan the actual proofs.

Give each printed placement its own URL

Suppose a booth offers a product sample. Both the counter sign and the card in the sample bag take visitors to the same request form. Keep the landing page, source, medium and campaign consistent. Change one value, utm_content, to identify the printed piece.

Replace the example domain and labels with your own. A short, recognizable campaign name makes it easier for the person running the report to find it after the show. Keep one list pairing each artwork filename with its final URL. Google treats campaign values as case-sensitive, so a capital letter can split what you intended to be one row. Google's campaign URL guide

Give the printer a different QR image for each row. Two separately named image files can still contain the same link. If the form itself is still being designed, the trade show lead capture form template covers the fields to ask for at the booth.

Scan the proof before approving the print run

1. Scan the counter sign from the printed proof. Open the link on a phone, allow any short-link redirect to finish and check the address of the landing page. Compare the campaign and placement values with your list.
2. Repeat with the bag card. Both should reach the same form, with a different placement value for each. If a redirect drops the tags before the analytics tag sees them, fix that redirect or encode the tagged destination directly.
3. In a test property or a marked test session where analytics consent is granted, inspect the landing page view and its page location. If the site deliberately cleans the address bar after measurement, this captured URL is a better check than the address bar alone.
4. Test one submission using a destination your team controls. Confirm that the receiver accepted it. Record the material, landing URL and outcome separately so the preflight can be excluded from the event results.

A QR generator's preview tests the link you entered into the generator. Scanning the proof also catches a layout mistake, such as the counter code being placed on both pieces.

Read the placement in GA4

After the campaign data has been processed, open Traffic acquisition in the GA4 property for the landing site. Find the event's Session campaign and check Session source / medium against your planned pair, such as expo / qr. To compare the pieces, use a free-form exploration with Session manual ad content as the row and Sessions as the metric. Filter to the campaign and the same event dates. Google maps the utm_content parameter to that placement dimension. Google's traffic-source dimension reference

Use a fresh session when testing each placement's session attribution. Someone who follows both codes in one visit can open two different tagged URLs within the same session. Also, a visitor can forward the link on the bag card to a colleague. A row labeled bag_card tells you which link brought a measured session. It can't tell you who physically scanned the card.

Work out which question your numbers answer

If the question is “Which material sent people to the form?”, compare measured sessions by placement. A camera preview that never opens the page cannot produce a landing-page view. Visits that your analytics setup does not collect are also missing from this report.

If the question is “Which material produced sample requests?”, verify where the placement is stored with each accepted submission. Inspect one test record from each code. A UTM value in GA4 doesn't automatically create a matching field in your lead list. If your form doesn't retain it, report the sessions you can attribute and keep accepted requests as a separate total until that link exists. The popup lead tracking checklist explains how to verify the accepted-request event.

Write down how many signs and cards were distributed and where they were used. A counter sign might be available all day while a bag card only goes to people who have already stopped for a sample. That context matters when you decide what to print for the next show.