Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
Syntax is correct then. Syntax is not the issue. Could be that the issue is probably how your domain resolves URLs. Does it allow parameters? Instead of clicking through to it from your email, try it organically with dummy values to see what happens. There are also other unknowns here, like, wha...
The first thought that came to my mind is that you need a "?" to start your very first parameter off right.Therefore, it should look something like this: www.website.com/stories/?{{my.UTM-Encoding}}&utm_content=campaign1#pic2
There are quite a few discussions on this topic in the community that I've seen. You can easily just do a search for category constraint and find many of them. Here's one: What are the email bounced categories?
what's the exact, full name of the file? apparent, FB doesn't like whitespace file names such as "file name.jpg" or "file%20name.png".
Try adding a filter for contains "mod" and then another filter for not contains "module". Filter logic should be ALL. You should get results for items such as "modular" and "modification" but not "module".
I'm sure that there are some caveats to what you're trying to do, but if it's as simple as I think it is, how about a single campaign with a single flow action of Send Email and a recurring schedule that runs on a monthly basis.
I felt the presentation was very clear and is your best bet (better than this response post I wrote) in getting a better picture of what you're trying to accomplish. It is not a step by step tutorial but assumes that you are familiar with all of the features, like tokens, assets, cloning, etc. My ...
If your templates use the global unsubscribe that is automatically appended, then simply remove the code for the footer which contains the unsub token and then it will start to automatically append your global unsub link again.If your templates use custom footer, then manipulate the template code to...
Click the + button and add values
There must be something in your custom form CSS that is causing this. I would start there. By default, they are not stacked.