Passing Luminate Source and Subsource from a non-Luminate landing page

Reid Dossinger

How can you pass specific/dynamic source codes from a non-Luminate landing page (in our case, a page in our Drupal CMS that's the target for ads) to a Luminate (TeamRaiser) page?

We have a signup page in our CMS that allows users to select an event state and specific event, which then puts them on the correct TeamRaiser event page. If we point directly to the TR event page from our ads, we can easily use the s_src and s_subsrc parameters to capture the registrants who come from those ads. However, we want to point out our CMS's landing page, but still find out how many registrants we're getting from those ads.

One thing I've tried is to use Google Tag Manager to look for the s parameters and then append them to the outbound URLs if the parameters are there. But I ran into some interference, and it was inconsistent (possibly due to a modal that pops up if there's more than one event per state).

Anyone have any advice? Thanks!

Brian Mucha

One thing I've tried is to use Google Tag Manager to look for the s parameters and then append them to the outbound URLs if the parameters are there.

That's what I would do, except I'd do it in the Drupal page itself using JavaScript. It should added to your locator widget/tool. For whoever made that, it would be super easy to just append all of the URL parameters present, but you could get a bit fancier and only pass the s_src and s_subsrc values.