There are 15 default Activities in Automation Studio. These are:
Data Copy or Import
Uses an external file to update your subscriber list or Data Extension by either:
You can create an Import Definition in Marketing Cloud Contact Builder. This is where you select things like the destination for your data, the file you want to import from the FTP (with the right naming conventions!), server, or existing Data Extension, as well as mapping your headers and choosing how you want the imported data to be handled.
You might use this activity when you have new data to import to Marketing Cloud, perhaps from a third-party system.
Data Extract
As the name suggests, this activity extracts the data from your chosen source within Marketing Cloud Engagement and creates it in a new file. It can also transform file formats. For example, from an XML to a comma-delimited file.
You might use this activity to extract data into a new file in your FTP that can then be used outside of Marketing Cloud. For example, you might use it to extract engagement activity metrics for a series of journeys you have running.
File Transfer
This one is straightforward. The ‘File Transfer’ activity unzips or decrypts a file in your Marketing Cloud FTP Site. You could use this to securely transfer the file to a new location.
SQL Query
SQL is an industr-standard language for manipulating data sources to meet your needs. In Marketing Cloud Engagement, SQL Activities allows you to extract data from one or more data tables (Data Extensions) and put the results into a new table.
This is super useful for creating clean, understandable data for marketers to use effectively. For example, if you have a table of customers and a table of purchases made by customers, you can merge the two tables together and provide a neat single table listing out all your customers, and the last product they purchased.
SQL Queries should also be used when you have advanced filter logic, as the Filter activity (see below) can often become hard to read and understand when using multiple fields from multiple objects.
Filter
For those with straightforward data segmentation needs, a ‘Filter’ does the job. Much like SQL Query, a ‘Filter’ applies a set criteria to your database to create a new table of data containing only the filtered records. You’ll need to create the ‘Filter’ in Email Studio before automating it within Automation Studio.
This option is great for quickly creating Data Extensions or Groups of select contacts, for use within Journey Builder or Email Studio. For example, whittling out all those interested in a specific product or service, or based on demographic information.
Refresh Mobile Filtered List
Much like the above, this activity is specifically applied to Mobile Studio lists (used for SMS and chat message sends), refreshing any filters you have already defined and ensuring the list remains up to date.
Verification
It is best practice to put Verification steps in your Automation Studio to ensure that each automation runs correctly and efficiently. For example, you may run an SQL Activity that identifies new orders received in the last 15 minutes. If the query finds no orders have been received in that time period, you can add a Verification step to prevent any future actions from being run - which can be a crucial timesaver.
Wait
Sometimes, placing multiple automation ‘Activities’ one after the other can cause errors. It’s best to include a ‘Wait’ between steps to give the system time to process. You can set your ‘Wait’ by time duration or select a specific time for the automation to continue.