Courtny_Edwards

@hermana Hi Alexa, I did what Amy suggested too - used a text token, and added it to our email & landing page templates in design studio. We use a token for the whole copyright line, not just the year - in case we then want to change the wording of our copyright in the future too. So we use {{my.copyright-year}}. You can name it anything you'd like - but I'd recommend expanding beyond just {{my.footer}} for two reasons:  1. The more tokens you start to build, its better to have a bit more description to what each is and 2. {{my.footer}} makes me think it could be updating the whole footer section rather than just the year. But that is completely personal preference!  We use EM- before email specific tokens, and LP- in landing page specific tokens too. I've seen quite a few people do this too, or something similar to identify tokens.  ... View more

yes, @SanfordWhiteman to the rescue with the most streamlined solution!  😎   🕺 ... View more

Thank you @Chris_Wilcox - I've bookmarked the blog, will be reading it all over the holidays ... and am going to take it step by step (and test by test by test by test) and will come back if (when!) anything specific pops up. ... View more

Thanks so much @SanfordWhiteman - this is quite a collection, excited to dive in! Blog is bookmarked for all my holiday reading free time 🎄 ... View more

Hi @dhughes007 - you're right, with the trigger campaign it will check your filter to see if they purchased the product at the time the trigger fires (ie. when they visit the product page), then assuming they hadn't purchased prior to visiting the page it would add them to the flow then and not check again before sending the email.  To combat this you could create a batch campaign that sends daily ... filters being "visited webpage - in time frame - yesterday" & "not purchased product " (using whatever field you are using to track orders) and then just ensure each person can only go through flow once. For added security, once they purchase a product or once promotional email is sent you could add them to a list, and add "member not in list" filter to your promotional send campaign.  You could also use multiple trigger campaigns and move them from smart list to smart list based on visiting the page, then purchasing or not purchasing, and then send email off the last smart list.  Both are a bit of a multi-step flow but it ensures you buy that time to allow them to purchase before following up. Happy to jump on a call if you wanted to talk through further if it would help!  (Also long-term if you wanted to expand number of promotional nurture emails you send people who visited the site you could look to build an engagement program and add them to a stream based on product page they visited. Once they purchase a product they can be removed from the stream (or program) - but that would work best if you'd want to send them a few different emails over a period of time. It would also give you a built in audience for that product if you ever ran a promotion that you wanted to target to set people who hadn't purchased) ... View more

We are seeing this same issue when an adblocker is enabled on a customer's browser, and its my mission over the next few days to investigate and fix. Will share anything I find, in case it may help you too @Eve_Yu  ... View more

Thank you both @Jo_Pitts1 & @SanfordWhiteman  - this is really helpful, and going to be a game changer as our instance continues to grow! (also so glad I didn't actually imagine the webhook solution - ha!) ... View more

Hey @Guitarrista82 - just brainstorming ideas: 1. Are the employees continuously testing emails, or is it more of a one-off when creating a new template? Could you have a triggered campaign which removes employees at a specific time after person create date, just within the brand partitions?  2. Do they need to test to their individual employee address or could you set-up a set of brand-specific test email addresses within your domain with a shared inbox, or email loop, linking directly to all the employees addresses who need access (I guess one downside is everyone in the loop would see all tests...) Appreciate both of these are workaround fixes, rather than a smooth process, but could save you time manually adding each.  ... View more