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
Gregory Campbell,
At Liberty science center we had a custom cart but used tnew to complete the sale. If I remember correctly we had a way to have the marketing site recognize the source code in a url coming from the marketing email or frankly anywhere, It was done in the same was as tnew expected the source code. When we saw that a the marketing source code was part of a url we would create a cookie with a relatively short life time; like a day or two. Once you completed our custom cart or frankly browsed the site and then build the cart, we would transfer the cart to tnew. As part of that process of transferring the cart to tnew we would read the cookie and apply the source code if it was still valid. This was an approach that was good for any source not just email.
Tom Brown (Past Member),
That sounds like an interesting approach for a custom site, and I like it! Do you know how exactly that was done? Some JavaScript which parsed the e-mail from Wordfly or something like that? I know our Marketing team is interested in looking for better methods of tracking our e-mail communication, and this sounds like a path worth exploring.
John
John A. Moskal II
LSC has what I would call a semi custom site. The carting process is definitely a custom, build your own experience process. I don’t remember all of the details of how we created the cookie. It’s been several years now and the actual coding was done by our web development partner Rawnet. I do remember that it was a source=###### approach added to the url from external sources like wordfly or other sites like Facebook and the like.
To create the cookie, I don’t remember if this was something added to Concrete5 CMS / web serve. Or if it was part of an include that showed up on all pages as part of a common header or footer. I suspect this later approach. You might “inspect” one of the LSC.org pages and take a look. (I’m on an iPad right now) Or find one of their links with a source = in the way tnew did/does it and see if this is still working. You should also be able to see the source code pass through on the tnew pages. As I remember it, this approach significantly improved our ability to make attributions both for tickets and membership renewals.
oops I weighed in on the Marketing thread version :)
Thanks for the reply Tom! Very helpful!
Heath Wilder,
Hey Heath, would you ever be willing to share the JS for that cookie? I could deploy it to our site via google tag manager.