Wordfly Promotion Source conflicts with Source in link-embedded promo code

Wondering if anyone else has had this experience! We have discovered that if our Wordfly emails are promoted to Tessitura, and the email contains links that include an embedded Promo code, even if the source code numbers are the same, the two source codes seem to compete with one another and the link fails--there is a "too many redirects" error.

This is extremely frustrating since we often would prefer to embed the promo code rather than having the customers enter it themselves. Our current workaround is to have the email link to a landing page with a series of links on it, and embed the promo code in THOSE links (the ones on the landing page).

My understanding is that we can turn off Tessitura promotion on Wordfly, but doing so would mean losing open rate information and other important data. It also is my understanding that this would be a global setting, not per-email.

Has anyone else come up against this? Any advice or workarounds would be most welcome!

Parents
  • My solution may not fit your situation in a practical sense, but on the occasions when we distribute a promo code to our own lists (eg a Cyber Monday), I basically flip the script:

    - Do the import to Wordfly and generate the source code with it promoted to records

    - Set up the promotion to work with that source code.

    This can feel a bit onerous because it forces a very specific order of operations, and probably means that it has to be done in a pretty limited window. It's normal for us to decide our promotion needs in bulk, get them set up, and then do the distribution as applicable. If you have to do the work involving the constituent records before doing the pricing pieces, it shifts this, especially as we have a best practice of generating our counts and etc as close to send time as business hours allow.

Reply
  • My solution may not fit your situation in a practical sense, but on the occasions when we distribute a promo code to our own lists (eg a Cyber Monday), I basically flip the script:

    - Do the import to Wordfly and generate the source code with it promoted to records

    - Set up the promotion to work with that source code.

    This can feel a bit onerous because it forces a very specific order of operations, and probably means that it has to be done in a pretty limited window. It's normal for us to decide our promotion needs in bulk, get them set up, and then do the distribution as applicable. If you have to do the work involving the constituent records before doing the pricing pieces, it shifts this, especially as we have a best practice of generating our counts and etc as close to send time as business hours allow.

Children
No Data