TNEW: promo codes and tracking parameters

Passing promo codes and tracking data from your Basker site through to TNEW involves two separate layers. Understanding which layer handles what helps when configuring campaigns or troubleshooting.

Promo code capture (Basker)

When a visitor arrives on any Basker page with ?promo= in the URL, Basker automatically captures the promo code and stores it in a short-lived browser cookie. This happens automatically — no configuration is required.

Example: a visitor arrives via yoursite.org/events/show?promo=19541. Basker captures 19541 and holds it in a cookie for 30 minutes.

Injecting the promo into the booking link (your theme)

Basker does not append the captured promo code to the TNEW booking URL automatically. Your site theme must read the cookie and append its value to the booking button link before the visitor clicks through to TNEW.

This is a theme-level implementation step. If promo codes are not passing through to TNEW, confirm with your implementation team that the cookie-read step has been built into the theme.

UTM parameters

UTM parameters (utm_source, utm_medium, utm_campaign, and others) are not forwarded to TNEW at the platform level. If you need UTMs to survive the handoff to TNEW for attribution, this requires a custom implementation in your site theme.

Promo codes through redirects

If a visitor arrives via a vanity URL or redirect, query parameters including promo codes and UTM tags pass through the redirect automatically. A redirect from /NYCHA to /events/your-event forwards ?promo=19541&utm_source=flyer to the destination without any extra configuration. See Redirects.