Guides

Guides are organized by what you’re trying to do. Before the list, three rules carry across every task — internalize them and the rest is predictable:

Scope first. Almost everything runs within a team + country scope, and Pulsy resolves it from your account, not from anything you pass. An empty or rejected result is usually missing scope, not missing data. (See What PulseAd is.)
One active profile. Data is pulled against a single active Amazon profile; if you have several allowed, a fresh session may ask you to pick one first.
A chat reply is not a confirmation. Anything that changes a campaign is proposed and waits for approval — see Capabilities.

By goal

Ask & analyze

Get real answers out of chat. Ask a concrete performance question and Pulsy routes it to the right analyst, runs the query, and streams the answer. What changes the result: your active profile, the scope, and which analyst the question implies (Sponsored Ads vs. DSP are separate — a cross-channel question needs both).

Build a report

Turn an analysis into a report or a saved dashboard. Once a data question has returned, ask Pulsy to make a report from it; reports are composed from a fixed set of building blocks (KPI bands, insight cards, charts, tables), so their shape is predictable. The Overview Dashboard and Event Monitoring surfaces can also plan a dashboard from a prompt, preview it, save/edit it, and retain execution history.

Reporting workflows

The recurring reporting surfaces — weekly reports, custom AI reports, report templates/schedules, and shared reports. Chat answers can also be shared as links, but sharing is team-scoped rather than public: a same-team member can read it, while a member viewing from another current scope is asked to switch. Creating a schedule is one of the few writes a viewer-role user can make, because it touches only Pulsy’s database, not Amazon.

Campaign agents

Work with campaigns, budgets, bids, targets, monitoring, and execution history. Changes proposed by chat follow the propose → approve → apply flow: Pulsy proposes, you approve, and a separate step applies the mutation via pulsead-agents. The Keyword Optimizer now lives under Campaign (the legacy Planning URL redirects there); its explicit Apply control dispatches grouped keyword changes directly and reports applied, pending, and failed groups.

Optimization (optimize-cycle)

The structured, multi-step budget/bid optimization run, with its own staged approval gates (and optional auto-approval). Remember the live caveat: autonomous budget changes reach Amazon for one pilot brand today; for everyone else the cycle computes and previews but doesn’t send.

Set up your workspace

Teams, country, connecting Amazon accounts/profiles, and team channels (and off-Amazon data — see Data & coverage). This is the prerequisite for everything above: no resolved scope, no answers.