You speak like custom fields are definitely coming back - is that the case?

@Tyson Yes, you will be able to use custom fields again at some point in future. Google is aware of the issue and is taking steps to resolve it. I am merely giving this alternative so that we can still have this data in the meantime.

Great, just read Shawns article. Simple to setup and should produce the association between referrer and transaction that is likely to save me a heap of time.

@Richard:

Thanks for reading! We actually use that method ourselves and have found it to be a great help. I hope it proves as useful to you!

If and when we're able to use custom fields again, would there be any reason to switch back to Shawn's original filter setup? If Jeremy's filters work equally well, I'd imagine we could just stick with those.

BTW, thanks *very* much for the workaround. We're trying it out today...

@Winooski: No, there would be no reason to switch back. Both filter sets function exactly the same. Similarly, once custom fields start working again, anyone using Shawn's filters shouldn't bother switching to mine.

You're welcome :)

I just added these filters without success. Will the data be 'granfathered' into the previous transactions or only work from here on out?

@Marco:

These filters, just like all filters within Google Analytics, only apply to the data moving forward. Your historical data is not affected. In a day or two you should see results from the filters.

The filters seem to be working fine, they are gathering the source, keyword etc but the unique transaction id no longer appears, it is just the source, etc.

Any ideas?

@Dan: Without seeing your setup, I can't say for certain what the issue is. I would double check the first filter and make sure that it matches the one I gave. Leaving out the parentheses on the first field or something like that could potentially cause the issue. You might also what to create a raw profile and see what the transaction id looks like without filters.

@Jeremy:

I removed the filters and the tracking returned to normal. Our transaction ID's are simple unique numbers (TS-5373262).

The filters were exact, I triple checked them and got others to check for me.

Everything worked fine, except it overwrote the unique ID.

@Dan: Have you tried Shawn's filter set? It's function is the same as this one and should work fine now that custom fields are working again. There may be a temporary issue that's causing these to not work anymore. Also see this article which gives you a way to segment reports by transaction id, allowing you to get much of the same data without the need for filters.