1.1 Meet Marcto

What Marcto is

Marcto is an AI marketing workspace for cross-border sellers and marketing teams. It is not just a chat box. It organizes work around brands, products, projects, resources, skills, connectors, and automations so agents can produce useful marketing work from real business context.

Think of Marcto as an AI marketing team with memory and tools. Brand context defines how the team should speak. Product context provides facts and benefits. Projects hold concrete marketing goals. Resources store reusable materials. Chat and skills turn that context into plans, copy, creative directions, reports, and execution checklists.

Who it is for

Marcto is useful when your team needs to produce marketing work repeatedly, manage multiple products and campaigns, and reduce the time spent re-explaining context.

Common users include:

• Shopify and DTC sellers preparing launches, PDP copy, ad creative, email, and social content.
• Small brand teams keeping voice, product benefits, and project assets in one place.
• Operations, content, ads, and design teammates who need AI outputs to become reusable assets instead of loose chat history.
• Teams that want to automate repeated work such as competitor monitoring, content planning, inventory checks, and ad review.

Core workspace objects

These objects appear throughout the help center.

Object	What it stores	Common use
Brand	Positioning, audience, voice, constraints, logo, colors, durable facts	Keep outputs consistent
Product	Name, benefits, specs, proof, audience, images	Generate PDPs, ads, FAQs, scripts, creative directions
Project	One marketing goal, channels, timeline, deliverables, linked products	Manage launches, promotions, ad tests, content plans
Resource	Images, documents, links, generated outputs, final deliverables	Reuse materials and track versions
Chat	Temporary tasks or page-level assistants	Generate, analyze, revise, summarize, and save work
Skill	Fixed workflows and specialist capabilities	Make agents follow stable steps
Connector	Authorized external platform data	Read stores, ads, analytics, sheets, and documents
Automation	Scheduled or repeated tasks	Generate reports, check risks, send reminders

Recommended first path

Do not start with “do my marketing” before the workspace has context. Spend 15-30 minutes setting up the basics first.

1. Create a brand with positioning, audience, voice, banned phrasing, colors, and logo.
2. Create a product with description, benefits, specs, audience, use cases, and images.
3. Create a project with a clear goal, channels, deliverables, timeline, and linked products.
4. Upload existing assets such as product images, reviews, competitor links, manuals, or brand books.
5. Open page chat from the project detail page and ask the agent to summarize the context first.
6. Save useful outputs as resources so future projects can reuse them.

Example workflow

Suppose you want to test TikTok creatives for a new travel bottle:

1. In Brand, define the voice: light, trustworthy, and not exaggerated.
2. In Product, save benefits: leakproof, lightweight, car-cup-holder friendly, capacity, material, cleaning notes, warranty.
3. Create a project named “Travel Bottle TikTok Creative Test”.
4. Upload product photos, competitor screenshots, reviews, and visual references.
5. In project chat, ask the agent to summarize brand, product, and project context.
6. Generate scripts, visual angles, shot lists, and review checklists in stages.
7. Save final scripts to project resources and write durable customer insights back to the product profile.

When to use chat and when to use a project

General chat is good for temporary questions, brainstorming, and lightweight discussion. A project is better for formal marketing work such as launches, ad tests, PDP optimization, content calendars, and campaign reviews.

Use this rule: if the work needs brand context, product facts, reusable assets, team review, or future revision, put it in a project.

Pre-flight check

Before asking an agent for formal marketing output, check:

• Does the brand have audience, voice, and banned phrasing?
• Does the product have concrete facts, not only words like “premium” or “best”?
• Does the project define goal, channel, deliverables, and deadline?
• Are uploaded assets named clearly enough for teammates to understand?
• Will public claims, pricing, customer messages, legal, financial, or compliance-sensitive output be reviewed by a human?

Next step

If this is your first time using Marcto, continue with “Set up brand and product basics”. It walks through the most important workspace context setup.