Source Tracking from Tess to Wordfly to Donate 2

Hi.

I am working in Wordfly to deploy emails that drive transactions on Donate2.

My list extractions can have 50+ different sources within Tess. 

Once I promote the extraction, Tessitura overwrites the original sources.

Any tips for how I can track engagement—i.e. opens, clicks, and ultimately transactions on Donate2—back to the original sources used when the extraction was created?

Thanks!

Parents
  • Got it! Thanks.

    My Tess team is getting more granular with their question. Feel free to opt out here, but if you happen to know the solution, that is welcome.

    **
    HERE'S AN EXAMPLE

    Bob Smith and Jane Doe are both pulled into a list for a General Fund plea: Bob because he was a donor last year (source code 123) and Jane because she is a member (source code 456). 

    Currently, we have those sources promoted to the records when the list is pulled, but because they are both receiving the same Donate2 link embedded in their emails, their giving is tracked back to that one generic source in the URL or on the form (we'll call that source 789), and we can't track back to sources 123 and 456. They would both be receiving the SAME link like this in their emails: https://donate2.app/HokBNE?source_no=789.

    Ideally, Bob and Jane would receive the same email, but WordFly would modify the Donate2 Links to match the original source from which they came: 

    To be clear: the links would not be unique to each email address, just to each source/promotion number. 

    **

    Any ideas?

  • Hi John, I'm not a Wordfly user so don't have a specific answer on that platform.  We use Prospect2. The solution for P2 is...

    During a list import into Prospect2 I can set a custom field that carries the source number for each patron(I'd probably do this via an output set).  The source code number for each patron would get populated from the custom field 'SOURCE_NUMBER' that I'd create.  Bob's SOURCE_NUMBER custom field would say 123, and Jane's would be 456.

    I would construct the Donate2 URL to look like this in the email builder:

    https://donate2.app/HokBNE?source_no=[%SOURCE_NUMBER%]

    So when the email fires Bob would get https://donate2.app/HokBNE?source_no=123 and Jane  would get: https://donate2.app/HokBNE?source_no=456

    I was thinking if Wordfly handles dynamic custom field content, then there would be a way to use the ?source_no= override trick?

Reply Children
No Data