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

Parents
  • 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.

Reply
  • 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.

Children
No Data