Stijn_Heijthuij

From my personal experience I have noticed that in some cases it can take a while before the link is added. Click it a couple of times, wait an hour and then it should appear.

Hi Amanda,What you could try is to have your map be a Bulletproof background images | Campaign Monitor​.Then you can add a table with widths and heights in such a way that it appears to be a map with names/links over it. When actually it's just a table over a background image.

It's pretty easy to do if you're knowledgeable about Smart Lists and CSS.For mechanics:Create fields and Smart Lists based off those fields. Have someone check or uncheck the 'newsletter' field and create a Smart List of anyone who has the 'newsletter' field as checked. When sending a newsletter mak...

This is what I haveEdit the Admin role and see if you have this:

Hi Evan,Going into the Admin section of the instance, you will find the Users & Roles section. Going over to the 'Roles' tab you will be able to add a new role. Give this role a name and select everything under API.Now create a new user. Select the API role and tick the 'API Only' box.This should ge...

Hi Mahesh,Disabling the 'Export Leads' functionality will also block the downloading of leads from Static and non-subscribed Smart Lists, correct? I can see a case where we'd want to keep this and still disallow the automatic sending of Smart Lists.On your 2nd point; How do we activate the feature w...

Hi Andrew,Read up on this post Solution to using UTM parameters & cookies to capture lead source information​ .

That's how I've done it previously and has more flexibility than a Segmentation. When enforced with Smart Campaigns it might just be the best way.

Hi Samantha,You could create a segmentation with 28 possible values (default). Then you could create a signature snippet that is segmented on this Account Manager segment. Each segment would then have the account manager's information and image.You can then add this snippet to an email by replacing ...

Minor issue that we've noticed; if you have a token that is a URL (from start to finish) it won't be tracked in the reports. That's why we always break the http:// section out of the {{my.token}} to become http://{{my.token}}