I have a customer, that defines the newsletter straight in their CMS. And then sends them by importing them from the web.
Is there a tag I can use in the template, that tells CampaignMonitor to skip importing parts of the newsletter?
Hi Soeren, is your customer using 'Champagne for ExpressionEngine', or a similar 3rd party app to import content from their site/blog? Your best bet is to contact the CMS' support team, or whoever created the import software - they will be able to advise on this.
nope, the CMS is Umbraco. There's several reasons why the customers newsletters are created within the CMS:
- The customer is already used to create new content within Umbraco, so they don't need to log in to a separate system just to create their newsletters.
- Allows the customer to have a good, well-formed newsletter archive build in to the website.
- Some of the content for each newsletter is auto generated from an ecommerce plugin called uCommerce.
The customer creates their newsletter from within the system they are used to work with, and then logs into CampaignMonitor to create a campaign and Imports it straight from their website.
This is wreaking a bit of havoc in the customers Google Analytics account, as they often place a link from Facebook to these newsletters. And since we can't have GA tracking installed on these newsletters, the source of this traffic is lost within Google Analytcs (or to be more exact, counted as "Direct traffic").
So a special tag to tell the Import function to ignore a section of the HTML would solve this problem.
PS.: If you want to see the newsletter archive it can be found on this address (in Danish unfortunately)
Hi SoerenS, this is something you'll largely have to take up with Umbraco, I'm sorry to say. We don't have control over the behaviour of 3rd party applications and having a 'hide from import' tag on our end could be problematic.
The bottom line is that you'll have to talk to the support team at Umbraco, and/or the integration developer - if they can use the webversion of the sent campaign in the archive you have there (instead of the version hosted on the CMS), then you'll be able to get around these tracking issues.
Doesn't seem like I explained the situation right.
The newsletter NEEDS to be created on the website itself, as some of the content is generated by the system (fx. Top Selling products this month).
Having the webversion of the sent campaign as the archive version is also not a viable solution, as we then would loose some of the SEO advantages of having it entirely integrated into the site.
Anyways, let's now discuss this any further as I've found a way to solve the problem: I've included the Google Analytics tracking code in the hosted newsletter template, but am excluding it if the UserAgent string contains "CreateSend". Which is what the import funciton identifies itself as.
That way I've kind of created my own "do not import" method :-P