Ta kontakt med oss

SEO

Dessa fyra verktyg för marknadsföringsautomatisering kommer att öka din webbplatstillväxt

Publicerad

Marketing Automation Tools will Boost Your Site Growth


There’s no denying a fact that most of marketing tasks we get to perform cannot (or should not) be automated. You cannot automate content creation and link acquisition. You’d better stay away from automating most of relationship building tasks. You cannot fully automate customer service, loyalty building and community nurturing.

However automation can reinforce your marketing efforts and a few powerful automation tools should definitely be on your marketing agenda (especially if you value your time and mind your budget).

1. Automate Your Email Marketing with GetResponse

GetResponse is the prime example of how automation not only saves your time but also discovers new marketing opportunities letting you engage customers exactly when they are ready to act.

It has the most advanced marketing automation features I am aware of allowing you to automate your emails using advanced workflows you can build using a powerful editor:

GetResponse

Automate your emails using advanced workflows you can build using a powerful editor

Here’s how you build the workflows using the visual editor:

GetResponse

That being said, you can send a customized and personalized email to someone who clicked a specific link, skipped your specific email, opted in on a specific date or using a specific landing page.

Annons

On top of that, there are more great online marketing features GetResponse offers:

I haven’t had a chance to play with those yet but it would be amazing if those two spoke to their email marketing automation settings too!

In short, it looks like Getresponse is turning into an all-in-one online marketing platform with powerful marketing automation features.

2. Automate Your Social Media Sharing with Viral Content Buzz

ViralContentBuzz.com offers you the most non-intrusive way to bring your content in front of the social media influencers and generate shares: You don’t have to beg for shares, you just add your project for those looking for interesting content to discover and share it.

VCB RSS sharing feature lets you save time on adding projects: You add your RSS feed and whenever you have a new article going live, it will be automatically added to VCB.

This means, as soon as you publish an article, it gets shared by someone outside your immediate following which gives it an immediate social media boost.

Mind that ALL VCB projects go through moderation before appearing on the public dashboards which means two things:

Annons
  • Automation in no way affects the quality of projects available for sharing
  • RSS projects are not immediately added (it takes up to 6 hours to go through the premium review)

3. Automate Your Social Media Updates with DrumUp

There are quite a few tools that allow you somehow automate your own social media sharing. I like and use a few. In this article I am sharing my most recent find which I ended up using more often than the others.

DrumUp has two features I use (which are probably not unique but I like how they are set up):

  • RSS to social media: Once you publish a new article, the update goes to your social media streams automatically. I wouldn’t rely too much on this feature though: It’s always best to share a new article manually (So you can make sure your post thumbnail looks nice or you can tag tools and people you mentioned in the article or you can immediately respond to the comments, etc. RSS to social media feature makes perfect sense when:
    • You share to branded accounts (Those that do nothing else but broadcast your site updates)
    • You plan a long trip and have a bunch of blog posts scheduled and want them to get shared on your social media accounts for more exposure.
  • Recurring tweets: Here’s one thing about Tweets you couldn’t help but notice: Their life span is extremely short. An hour after your tweet goes live, no one will ever see it in most cases. You’ve probably seen only a couple of your tweets that lived for a day or two thanks to continuous retweets but that’s extremely rare. That’s why recurring tweets come so in handy. You can automate your tweet to go live a few more times throughout upcoming days and weeks for more of your followers to be able to see it.

DrumUp

A powerful alternative to DrumUp is Mavsocial which I am using quite often as well, especially for scheduling to multiple Facebook brand pages. Here are more lead generation tips for Twitter.

4. Automate Your On-Site Advertising Campaigns with Finteza

Finteza is one of the most advanced and independent web analytics suites that comes with a powerful on-site ad management feature. Finteza allows you to create ads, calculate click-through, detect click fraud and even personalize your ads towards specific segments.

Powerful automation features:

  • An ability to target your ads to certain demographics (location, device, gender, etc.)
  • An ability to schedule ads to avoid having to manually remove them when the pre-paid period is over

finteza

Bonus: Automate More with Zapie

Another recent discovery of mine, Zapie offers much more automation opportunities than you could imagine. It works by making any two online apps work together. Some examples of automation opportunities using Zapie:

  • Automatically follow new Twitter users that mention search terms
  • Automatically create Trello cards from new (starred / labeled) Gmail emails
  • Automatically tweet posts from a Facebook page
  • Automatically add new Facebook posts to an RSS feed
  • Auto-share newsletter campaigns on your LinkedIn profile
  • More!

A powerful alternative to Zapie is IFTTT (which I know is awesome but I haven’t had a chance to play with it enough).

More marketing automation tools and trends to keep an eye on:

  • Automate your customer support with Nextiva’s Auto Attendant
  • Automate your social media customer support with Socialbakers
  • Automate your social media content creation with Lately

What do you automate in your marketing? What other powerful tools are you aware of? Please share!

The following two tabs change content below.
I am the owner of this blog as well as Brand and Community Manager at Internet Marketing Ninjas and Founder of MyBlogGuest, MyBlogU and ViralContentBee.com
Annons

Latest posts by Ann Smarty (see all)



Källlänk

SEO

WordPress Considers Historic Development Change

Publicerad

WordPress Considers Historic Development Change

Matt Mullenweg, developer of WordPress and CEO of Autommatic, proposed no longer adding new features to the WordPress, pivoting instead to a plugin-first policy.

This new approach to the future of WordPress has already resulted in a new feature intended for the next version of WordPress to be dropped entirely.

Canonical plugins are said to offer a way to keep improving WordPress on a faster schedule.

But some WordPress core contributors expressed the opinion that publisher user experience may suffer.

Canonical Plugins

First discussed in 2009, canonical plugins is a way to develop new features in the form of plugins.

The goal of this approach is to keep the WordPress core fast and lean while also encouraging development of experimental features in the form of plugins.

The original 2009 proposal described it like this:

“Canonical plugins would be plugins that are community developed (multiple developers, not just one person) and address the most popular functionality requests with superlative execution.

…There would be a very strong relationship between core and these plugins that ensured that a) the plugin code would be secure and the best possible example of coding standards, and b) that new versions of WordPress would be tested against these plugins prior to release to ensure compatibility.”

Annons

This approach to features and options is also referred to as Plugin First, to emphasize how features will first appear in the form of plugins.

These plugins are called canonical because they are developed by the WordPress core development team as opposed to non-canonical plugins that are created by third parties that might limit features in order to encourage purchase of a pro-version.

Integration of canonical plugins into the WordPress core itself would be considered once the plugin technology has proven itself to be popular and essential to the majority of users.

The benefit of this new approach to WordPress would be to avoid adding new features that might not be needed by the majority of users.

Plugin-first could be seen to be in keeping with the WordPress philosophy called Decisions, Not Options, which seeks to avoid burdening users with layers of technical options.

By offloading different features and functionalities to plugins, a user won’t have to wade through enabling or disabling functionalities they need, don’t need or don’t understand.

The WordPress design philosophy states:

“It’s our duty as developers to make smart design decisions and avoid putting the weight of technical choices on our end users.”

Canonical Plugins the Future?

Matt Mullenweg published a post titled, Canonical Plugins Revisited, in which he made the case that this is the way that WordPress should be developed moving forward.

Annons

He wrote:

“We are reaching a point where core needs to be more editorial and say “no” to features coming in as ad hoc as they sometimes do, and my hope is that more Make teams use this as an opportunity to influence the future of WordPress through a plugin-first approach that gives them the luxury of faster development and release cycles (instead of three times per year), less review overhead, and and path to come into core if the plugin becomes a runaway success.”

The first casualty of this new approach is the cancellation of integrating WebP image conversion into the next version of WordPress, WordPress 6.1, currently scheduled for November 2022.

Plugin-First is Controversial

The shift to a plugin-first development process was subjected to debate in the comments section.

Some developers, such as core contributor Jon Brown, expressed reservations about the proposal to switch to developing with canonical plugins.

They kommenterade:

“The problem remains that there are too many complicated plugins standing in for what would be a simple optional feature.

Plugins are _not_ a user-friendly option to core settings. First users have to discover there is a plugin, then they have negotiated yet another settings screen and updates and maintenance of that plugin.”

The commenter used the example of a commenting functionality that is currently served by mutliple bloated plugins as a less than ideal user experience.

They noted that having one canonical plugin to solve a problem is preferable to the current state where desirable options can only be found on bloated third party plugins.

Annons

But they also said that having a settings option within core, without the need for a plugin, could present a better user experience.

They continued:

“Now, I do think Canonical plugins are a better situation than 6+ bloated plugins like exist here, but so would a single checkbox added to the settings page in core to do this. Which would further improve the UX and discovery issues inherent in plugins.”

Ultimately, the commenter expressed the idea that the concept of canonical plugins seemed like a way to shut down discussions about features that should be considered, so that the conversation never happens.

“Canonical plugins” seems like a weaponized tool to derail discussions the same way “decisions not options” has become for years.”

That last statement is a reference to frustrations felt by some core contributors with the inability to add options for features because of the “decisions, not options” philosophy.

Others also disagreed with the plugin-first approach:

“Canonical plugin sounds grand but it will further increase maintenance burden on maintainers.

In my opinion, it’s no go.

It will be much more better to include some basic features in core itself instead of further saying – It’s a good place for plugin.”

Someone else pointed out a flaw in plugin-first in that collecting user feedback might not be easy. If that’s the case then there might not be a good way to improve plugins in a way that meets user needs if those needs are unknown.

Annons

They skrev:

“How can we better capture feedback from users?

Unless site owners are knowledgeable enough to report issues on GitHub or Trac (let’s be honest, no one reports plugin issues on Trac), there’s really no way to gather feedback from users to improve these recommended/official plugins. “

Canonical Plugins

WordPress development is evolving to make improvements faster. Core contributor comments indicate that there are many unresolved questions on how well this system will work for users.

An early indicator will be in what happens with the cancelled WebP feature that was previously intended to be integrated into the core and will now become a plugin.


Featured image by Shutterstock/Studio Romantic

Källlänk

Fortsätt läsa

MISSA INTE NÅGRA VIKTIGA NYHETER!
Prenumerera på vårt nyhetsbrev
Vi lovar att inte spamma dig. Avsluta prenumerationen när som helst.
Ogiltig e-postadress

Trendigt

sv_SESvenska