Welcome!
Welcome to the Marin Software Support Center. We're glad you're here. Here's what you can look forward to:
  • Real-time search so you can find what you need faster than ever.
  • Easy-to-follow video guides for our most popular articles.
  • Interactive simulations and Live Screenshots to make learning easy.
  • Regular content updates to ensure every word you read is accurate and up-to-date.
Home > English > Your Marin Account > Account Activation, Linking & Settings > How To Articles: Account Activation, Linking & Settings > Seven Steps to Optimal App Speed and Efficiency

Seven Steps to Optimal App Speed and Efficiency

Working with large amounts of data within the application at any one time can lead to long load times. This article will run through, in no particular order, seven steps to help you minimize the time it takes pages to load within the platform.

We also encourage clients to use the SmartGrid tab to more quickly view keywords and creatives. Feel free to review our Help article for more details on this feature.

Step one: Optimize your column usage

To minimize the amount of data viewed at any one time, it is recommended that you only include columns you need for the action you are performing. Any unnecessary columns will increase the time a page takes to load. Removing metric columns to leave only attribute columns (Campaign, Group, etc.) means you'll be able to see the the full grid much more quickly, which may be useful when creating a report to perform bulk/copy actions that do not require metrics.

Step two: Minimize your date ranges

Generally the longer the date range selected in the calendar, the longer it will take for pages to load. Therefore, when navigating between tabs keeps a short date range selected e.g., one day. If you accidentally navigate to a page with a large date range selected which is not required, simply navigate back to the channels page (as it has the least items and will load the grid faster) and change the date range, before navigating back to the original tab as desired.

Step three: Make the most of custom views

If there are certain views that you need on a regular basis, it would help to save these. Saving views will stop you from having to navigate through the view builder and will only pre-populate columns that you need. In addition, you can save these views as widgets for the dashboard providing fast access to the data as required.

Step four: Delete unnecessary dimensions

A large number of dimensions can increase overall load times. Therefore we recommend removing any dimensions that are not being used and to set any dimensions which do not require a roll up in the dimension tab to Tagging Only.

Step five: Adjust your default view

To minimize load times, most accounts will by default only show keywords with one click or more in the last twelve months. However, for some high traffic accounts it might be appropriate to increase this threshold to five clicks or more in the past year, in order to further increase load speed. Please contact your platform representative if you think this may be a good option for you.

Step six: Use the Advanced View Builder

When creating a report with multiple filters, it is advisable to create this within the Advanced Builder (located in the View Builder). Here you can specify filters, date ranges and sort by columns all at once, reducing the need to build each filter one by one in the interface. This will help you avoid the wait time for each column to reload with the new data as specified in the newly applied filter.

Step seven: Sort your bulk files alphabetically

If you use the bulk upload feature for adding keywords, creatives, or any other objects to the platform, you can save a lot of time by sorting your bulk sheets alphabetically. You can decrease processing and posting time by up to 25% by sorting bulk files alphabetically by (in the of case of a keyword bulk upload): Account. Campaign, Group and Keyword.

Last modified

Tags

Classifications

This page has no classifications.

 

wiki.page("Internal/Mindtouch_Launch_Sandbox/js.cookie.js")