Projects are like folders where you organize products and keywords. They improve how you run your Product Research, Tracking, and Market Analysis within DataHawk.

A Project could be any of the following:

  • a collection of all products you are selling and those you compete with, with the keywords attached to them.

  • a collection of niche-specific products you are currently selling and those you compete with, with the keywords that are attached to them.

  • a collection of niche-specific products you plan to start competing with upon a new product launch idea, with the keywords that are attached to them.

  • any of the above combinations, and basically, however you like organizing your work!

To start using DataHawk, create a new project and track your desired Keywords and ASINs.

DataHawk automatically checks the Products you're tracking and sees how they rank for each Keyword you're tracking within the same Project, that way, you don't need to waste time assigning keywords for each Product. Ensure you enter relevant Keywords and ASINs within the same Project as a best practice.

Note that you can also check Product Keyword rankings per marketplace, in case you skip projects.

Important Considerations

A few considerations are important to keep in mind when organizing your workspace into projects to ensure optimum usage. If you're time-constrained, you could ignore our recommended best practices and start with a single project.

Usability

Stuffing a single project with thousands of products is a sure way to lose usability by reducing the load speed of the web application and making it harder for you to analyze things with a zoomed-out view.

Tip: Organize products into as many projects as possible and relevant, and avoid putting thousands of products into a single project.

Keywords Ranks

When using the keyword tracker in the web application, the platform will show you how the product you're analyzing is ranking for each keyword contained within the same project.

Having too many products and keywords that are irrelevant to each other within the same project makes analysis a bit disorganized.

Tip: Organize keywords into projects where they are relevant relative to the products contained within those projects. In DataHawk, you don't assign keywords to products, you assign them to projects.

Alerts

When setting up alerts, you can elect to be alerted on changes in all the products contained within one or multiple projects.

Tip: A well-organized workspace with relevant multiple projects facilitates setting up alerts on a project level.

Reports and Exports

Various reports and exports analyze data on a project level.

Tip: A well-organized workspace with relevant multiple projects facilitates analysis of reports and exports and makes their generation much faster.

Best Practices

An optimal workspace setup is one in which a **combination of the following best practices is applied** in terms of projects.

By Brand

You could create one project for each important brand you're monitoring or operating. It is definitely recommended you create a project in which you put all the products of your brand or at least the most important ones. This would come in addition to the other types of project organization outlined below.

Tip: Create a project in which you put all the products of your brand or the most important ones. It's always gonna be helpful when you'll want to quickly analyze or export your entire catalog. You can also put your main competitor(s)' brand in distinct projects.

e.g. "My Brand", "My Competitor Brand".

By Category

You could create one project for each product category you're monitoring. For instance, an apparel brand could create one project for shorts, another one for t-shirts, another one for socks, and so forth.

Tip: Create as many projects as product categories you operate in. Combine this with segmentation by brand, notably when monitoring competitors.

e.g. "My Brand - Shorts", "My Brand - T-Shirts", "My Competitor Brand - Shorts".

By Use Case

You could create one project for each use case or goal, or actual project or task you're working on. For instance, you may be working on a product launch, a promotion campaign, or a market research project, in which case you could create a DataHawk project pertaining to such a project.

Tip: Create as many projects as use cases you have in mind or tasks you're temporarily working on. Combine this with segmentation by brand and category when needed and relevant.

e.g. "Top-Selling Products - Shorts Category", "Product Launch - Running Short", "Prime Day - Products with Lightning Deal".

By Product

You could create one project for each parent SKU you're monitoring or operating. This is particularly relevant when you don't have a large catalog and you may have multiple variations.

Tip: Create as many projects as products you monitor or operate if you have a small catalog and multiple variations.

e.g. "My Hero SKU", "My Main Competitor's Hero SKU".

Creating a Project

There are various ways you can create a project

* When adding a new product or keyword

* From the projects list by clicking on *Create project*

* From the Quick Actions menu in the bottom-left side of the left navigation panel

* Via the Bulk Import functionality from the projects list after clicking on *Workspace actions*

Did this answer your question?