Using multiple revenue source codes in LO?

JD Piland · August 2016

In our current system, we are able to use URL parameters to attach what we call a revenue source code to each transaction. So, we can use one donation form for a multichannel campaign and see where exactly the associated transactions are/were coming from. For instance, one code could specify a transaction came from Twitter while a separate code could signify a transaction came from email, even if the same person made both of those gifts. And all of this on the same donation form.

To be clear, what we call source codes are attached to the transaction and therefore one person could have multiple transactions from different channels (specified by source code). From what I can make out, Luminate's source codes are for record origin and, once there, are not editable (except manually by an admin). Right now, we're kind of thinking we'll need to create/clone donation forms for each channel in the campaign so we can attached the appropriate revenue source code, but also hoping that is not the case.

We're relatively new to Luminate, and would love to know if our version of transaction source code tracking is still doable within Luminate. We're either not getting or not finding good solutions. Any ideas and how-tos would be very much appreciated.

Thanks in advance!

PS - I've heard of cross reference tables, so I'm looking into those. But would those be a viable option for the purposes laid out above? Are there best practices for x-ref tables somewhere I'm missing?

Brian Mucha · August 2016

The s_src and s_subsrc URL parameters are stored on transactions and other interactions, so you could use those. They are also stored on a constituent record if the record is new. (You can have Luminate set to continually overwrite the source and subsource in cons records if you want, but the default is to use them as the record's origin.)

https://kb.blackbaud.com/articles/Article/64205

And the cool thing is that they are session tags, so they will follow the user over many pages and still get saved when they finally make a gift.

I usually pair these with matching Google Analytics campaign, source and medium tags.

JD Piland · August 2016

Brian Mucha:

The s_src and s_subsrc URL parameters are stored on transactions and other interactions, so you could use those. They are also stored on a constituent record if the record is new. (You can have Luminate set to continually overwrite the source and subsource in cons records if you want, but the default is to use them as the record's origin.)

https://kb.blackbaud.com/articles/Article/64205

And the cool thing is that they are session tags, so they will follow the user over many pages and still get saved when they finally make a gift.

I usually pair these with matching Google Analytics campaign, source and medium tags.

Great. Thanks, Brian! I have arelated question, though, about reporting.

I know I can do Donations by Transaction and Donations by Source Code reports. I even tried some Report Writer reports. But, all I'm seeing reported is Origin Source, not the source that would have been on a second transaction by the same donor. And the Donations bu Source Code is just shows totals, not individual transactions.

Is there any way to get a report that shows indidivual transactions, but with the source code that was attached to that transaction?

Brian Mucha · August 2016

Yes, the Report Writer Transaction Details report has an Interaction Source section with Source Code Text, and Sub Source Code Text fields. I think those are what you are after.

JD Piland · August 2016

I tried that, and it appeared to be the same as the Origin SOurce. Maybe it was just a fluke. I'll keep trying it all the same. Thanks again!

Brian Mucha · August 2016

Or another bug. Let us know!

EDIT: I just ran it against my own test account and found many transactions with different source codes. Seems to be working for me.

Using multiple revenue source codes in LO?

Comments

Categories