team raiser registration discount code in url?

Shana Masterson:

Hi Alex,

 

I usually use URLs that look something like this to track both in GA and in TR reporting. No discount code needed, unless I'm missing something. 

 

tour.diabetes.org/site/PageServer?pagename=TC_homepage&utm_source=Twitter&utm_medium=Share&utm_content=tdc2012_tweet-this&utm_campaign=TDC&s_src=tdc-twitter&s_subsrc=tdc2012_tweet-this

 

The last two pieces get picked up in TR reporting in the source code text and subsource code text columns (registration or donation reports).

 

Happy tracking!

Shana

Thanks Shana! The utm_ gets Google Analytics, which is lovely. And the s_src will attach a source code to a brand new constituent, but as far as I know it won't affect a constituent who's already in the system, because there's just one 'source' per constituent.

So if I'm looking at a report of registrations system-wide, some offline, some online from a physical kiosk and others online driven by content on a microsite, s_src won't tell me where the transaction was driven from. And Google Analytics data isn't integrated in to TeamRaiser reports, which means I can't correlate it later to the constituent's performance/contribution. 

Discount codes seem like a clever way to segment people later in their participation cycle, because the discount code is attached to the registration transaction. So the question is - is it possible to integrate the discount code at the beginning of the sales cycle, without actually requiring the registrant to do something other than click...

Hopefully that clarifies the situation...

Shana Masterson:

Hi Alex,

 

If you are looking to tie the information to the constituent record, I don't have an answer for you.

 

I use TeamRaiser and transaction reports to track sources for registration and donations (and for segmentation later on if needed - for example people who registered for my event via a Facebook post or similar) for my TeamRaiser events.

 

The source and subsource fields in TeamRaiser/Transaction reporting is for that particular action only. So the reports do tell me if someone came to my event from a link I've coded with source/subsource, an email message, google, etc. Source and subsource can change from action to action and do not affect the origination source code - of which there can only be one.

 

Discount code columns can also be found in the TR reports and I don't believe they can be found on the constituent record itself though, without a special customization.

 

Sorry if I'm mangling your request. Feel free to give me a ring (I'm pretty sure you have my card?)

 

Shana

Aha!  I didn't realize that src and subsrc were tied to the transaction in TR. If so, then that's almost definitely the right way to do it. I'll look into that more closely with my colleague who handles the TR setup and reporting.

Thanks, Shana