Marketing site and Source Codes

Cross-posting this to the Marketing forum. 

Hello all,

If you're sending a Wordfly email, but the CTA button goes to a page on your marketing site, then has a CTA to TNEW that order and revenue are going to be attributed to the default TNEW source code. Does anybody know if there is a way to get the source code generated by Wordfly to apply to the subsequent TNEW session or should you just always try to send folks into a purchase path on TNEW whenever possible? Maybe this is a custom site thing. Thanks for your help.

Thanks, Greg

  • We ran into the same issue and found that we have to send to a TNEW page for the tracking to work. I think that there is a work around if you manually add the promo code BUT if you do that, you cannot pull the list from Tessitura. Don't quote me on the workaround though. Best bet is to send to TNEW directly. 

    By the way, we have a group that meets regularly to discuss and share best practices/come up with solutions for the Tessitura/Wordfly integration. Let me know if you are interested in joining us. 

    Good luck!

    Tracy 

  • Hi Tracy, 

    I'd love to be part of the Tessitura/WordFly group if you are letting people in. 

    Thanks, 

    Kevin

  • Tracy - I had to miss the last meeting, but I look forward to the next one. And I am very interested in this discussion because we are working on a new website and we need to think through where we will land someone for tracking purposes from emails etc... We were trying to eliminate having a ton of info on TNEW and adding the same info on our website. 

    Meghan

  • Count me in to the Tess/Wordfly group as well, if possible! Thanks!

    Cynthia

  • Happy to add others. If you can send me an email at tschneider@virginiahistory.org, I will add you!

  • Happy to add others. If you can send me an email at tschneider@virginiahistory.org, I will add you!

  • Meghan -

    this will be a good topic for us to discuss! talk to you soon!

  • I would love to join! 

    On Aug 6, 2021, at 10:33 AM, Tracy Schneider <bounce-tracyschneider5173@tessituranetwork.com> wrote:

    
    <Tessitura_2D00_Network_2D00_logo_5F00_1500x421-png_2D00_150x42-png>
    Update from Tessitura Network
    <default-png_2D00_70x70x2-png>
    Tracy Schneider

    We ran into the same issue and found that we have to send to a TNEW page for the tracking to work. I think that there is a work around if you manually add the promo code BUT if you do that, you cannot pull the list from Tessitura. Don't quote me on the workaround though. Best bet is to send to TNEW directly. 

    By the way, we have a group that meets regularly to discuss and share best practices/come up with solutions for the Tessitura/Wordfly integration. Let me know if you are interested in joining us. 

    Good luck!

    Tracy 

    View online

     

    You received this notification because you subscribed to the forum.  To unsubscribe from only this thread, go here.

    Flag this post as spam/abuse.

  • I'm super interested in joining your wordfly group! Thank you!

  • This is a common issue. But a few orgs have gotten around this in similar novel ways.

    After talking to the folks at Wheeler Centre who had done this, we had our current webdev add some js script to our marketing site that takes the promo query parameter (ie: ?promo=[code]) from the end of the url landing when it lands on the marketing site and holds it (as a cookie) - and when the session eventually goes to TNEW puts it back on again.  Essentially 

    • Use client-side JavaScript to detect the presence of a “promo” parameter in the URL on page load
    • Save that value to a cookie that expires after 3 days
    • Whenever a users clicks TNEW URL we augment that URL by adding a promo param and a premove param
    • The only exception to that is, to avoid sending the same promo param quickly in succession, we keep track of any promo param sent and avoid sending it for another hour (by setting a cookie that expires in 1 hour)

    Hope that helps

    [EDIT] just a note that I think GA tag appending on the site can get tangled in this so keep that in mind as well.

  • Heath has provided greater details about coordinating this, but I'll add a simple statement to concur/confirm: Having data appended information from the url of a www site pass along to your TNEW pages requires code on your non-TNEW pages to support this functionality. And, as Heath's points mention, you'll want the code to be held and passed along regardless of how many pages the user visits before starting to truly shop.

    I don't know what approach our web agency used; only that this was named as one of our business needs upfront. For anyone being creative on their own, or who likes to get background from their external web developers, do make sure to take a few minutes to ensure that your plan accommodates current trends in privacy around cookies and so forth. "Cross-domain cookie" blocking is really frustrating during testing--and could be a significant challenge if your TNEW urls are NOT set up like sub-domains of your main website. [Noting that TNEW has just added functionally--activated via support ticket only--to help with testing.] This isn't a point specific to promo code tracking, but I hope it's an example that helps folks have the conversations they need, or kick off the right research, on this topic as you explore new code investments.

  • ,

    So when your website does this, does the user see something like "Promo Code = 11111" on the TNEW page?  Or are you also then hiding that area of TNEW whenever the promo code is only a number (since most actual promo codes that people use are word-based)?

    In my initial testing on our TNEW instance, while the promo source number works as described above, it also ends up with the odd promo code view for a patron, which could be deemed "odd".  Not necessarily a deal breaker, for sure.  Just curious how you dealt with it.

    Either way, this is good stuff; thanks!!

    John

  • Hi John!

    Yes, I believe so. We did NOTHING to independently manage our TNEW appearance, as we used the Quick Start Template from Tessitura and it's fairly limited in terms of controls (a highly practical shortcut to getting your brand look on TNEW, but limited controls). 

    To be completely honest though, we did the majority of the finishing work and testing of our TNEW v7 upgrade during the pandemic so (a) all testing was a little funky because we were faking all events and situations and (b) it's been over a year since I've had to think about this sort of detail, as we've basically sold nothing. I feel like I saw this "odd" instance and shrugged it off as a just how things are/not especially noticeable on our particular page.

    It's not my particular world so I don't have precise terminology and am just assuming this is a valid thought, but I suppose one other (native; non-developer) way of addressing the appearance would be to add language to the source, like you would for an offer. It wouldn't necessarily make the number look less random itself, but it could give the general area a better feeling of legitimacy. [And perhaps if there's an option to do code, but presumably less elaborate stuff, there could be code that says "display 'Referred Session (ex)' if source but no promo details".  Then no one would have to take on adding text for each source.]

    Jamie

  • Yeah, chances are most people probably would just bypass that anyway and ignore.  But it never hurts to ask and ponder these things.

    Thanks again, Jamie!

  • Hi John
     
    I agree that it’s an odd user experience to show the source code in the Promo code box online.  We weren’t happy with that, so went down the route of hiding the promo code box using javascript in our TNEW template.
     
    The logic is that we hide the promo code if it was applied via an incoming “promo” URL parameter. If the visitor then clicks the button labelled “Add promo code” this removes the promo code that came from the URL and allows them to type in and apply a promo code manually. 
     
    Best wishes
    Alison
     
     
    Alison Atkinson
    Senior Commercial Systems Manager
    The National Gallery
     
    My usual working days are Monday - Thursday