Skip to main content
A project in DevTune is your workspace for one product or brand. This guide walks you through creating your first project using the activation wizard.

​
Starting the Project Wizard

There are two ways to create a project:
  1. During onboarding - After creating your account and team, you are guided directly into the activation wizard
  2. From Account Home - Click Create Project

​
Project Setup Steps

The activation wizard walks you through seven steps. Every integration step can be skipped with Skip and configure later and connected afterwards from Settings › Integrations.

​
Step 1: Product

Enter the Product name and the Primary domain, for example example.com. If your product lives on a path of a larger company’s site, enter the full product URL, such as aws.amazon.com/amplify. DevTune tracks that path as your product’s home instead of the whole domain. Competitor URLs entered here are saved as their domain; set a competitor’s product path later in Settings › Brands. DevTune starts a website analysis from that domain and uses it to generate the product context, competitor suggestions, and prompt suggestions in the next steps.

​
Step 2: Competitors

DevTune proposes Suggested competitors from the website analysis. Add at least one competitor brand to enable share of voice and competitive comparisons. If the analysis is still running, has failed, or is taking longer than expected, you can add competitors manually, retry the analysis, or skip the step. You can expand or refine competitors later from Settings › Brands.

​
Step 3: Prompts

Review the Brand context DevTune generated — the product, its audience, main use cases, and differentiators — and edit it so it is accurate. Better context leads to better prompts and stronger recommendations. Then select the search queries to test how AI models recommend the product. Confirming the prompts starts the first probe run. Prompts are locked once that run has started; you can review them but not change them until it completes. You can add or revise prompts later from the Prompts tab in Insights › Visibility.

​
Step 4: Search Console

Select the Search Console property that matches your primary domain. DevTune rejects a property whose domain does not match, because a mismatched property would attribute another site’s search data to this project. Search Console supplies the classic-search clicks and impressions that Audit compares against AI citations.

​
Step 5: GA4

Select a GA4 property and the key event that counts as a conversion. This is what lets Results attribute conversions to AI-referred sessions. If you use PostHog, skip this step and connect PostHog from Settings › Integrations afterwards. If you use neither, choose Use the DevTune tracking snippet instead and install the snippet on your site.

​
Step 6: Cloudflare

Enter a read-only Cloudflare API token to load your active zones, then select the zone for your primary domain. Cloudflare supplies AI crawler and answer-fetcher requests for proxied hostnames. If your site is not behind Cloudflare, skip this step and configure edge middleware later from Settings › Integrations.

​
Step 7: Finish

The final step confirms the project is ready. It shows:
  • Measurement sources - which sensors you connected
  • First probe results - prompts mentioning the product, citations, and platforms covered
  • First prioritized action - the highest-priority recommendation to open next
Platform coverage in that first run depends on your plan:
  • Plus - ChatGPT, Perplexity, Gemini
  • Pro and above - ChatGPT, Perplexity, Gemini, Google AI Mode, Microsoft Bing Copilot

​
What Happens After Creation

Select Open project to go to the project’s Home. If your team has no plan yet, the finish step offers Start 14-day free trial instead. Get started on Home lists the steps left in your first pass through the loop: first answers, accepting a fix, connecting a sensor, and marking a fix live. See Get started. Once the first run completes:
  1. Open Insights › Visibility to review the baseline
  2. Review the first suggestions in Actions, or on the Suggested actions card on Home, and select Accept on the one you want to work on
  3. Scheduled runs build trends over time

​
Editing Settings

After creation, use Settings in the project sidebar for ongoing setup:
  • General - Project name, description, product context
  • Context - Company context and agent preferences
  • Brands - Brands, tracked URLs, brand terms
  • Platforms - Enabled AI Search engines
  • Integrations - Sensor and tracking snippet setup
See Settings for every tab.

​
Project Organization Tips

​
One project per product

Create separate projects for distinct products, even if they belong to the same organization.

​
Keep context current

If the product positioning changes, update Settings › General first. If the content footprint changes, update Settings › Brands.

​
Next Steps

  1. Explore Home - Learn the interface
  2. Understand Key Concepts - Learn DevTune terminology
  3. Actions queue - Review suggested fixes