Good afternoon, Pedro.
Here’s where your money is working — and where it isn’t. See what needs a decision below.
Decisa connects paid clicks, server-side conversions, and attributed revenue so you can see which campaigns are earning money — then review changes safely before they touch your ad accounts.
Budget change proposal is ready for approval. Evidence: attributed revenue and recent spend.
Sample workspace · today
Here’s where your money is working — and where it isn’t. See what needs a decision below.
Browser pixels miss context, platform reporting can disagree with backend revenue, and spreadsheet checks get stale. Decisa gives your team a first-party attribution layer without pretending every conversion can be matched.
Capture paid clicks, UTMs, gclid, fbclid, ttclid and visitor_id, then connect them to conversions sent by your backend.
See attributed revenue by source, medium, campaign and content. Add ad spend manually where sync is not available yet.
Recommendations and audits become drafts. Your team submits, approves, applies and reviews every change with a record.
Decisa is not an autonomous campaign operator. It is an attribution and campaign-control workspace for teams that want evidence before action.
The pixel captures visit context and stores a visitor_id that can later be sent with backend conversions.
Your backend posts conversion events to /v1/conversions. Matching depends on the visitor_id and available click context.
Use dashboards, click lists, conversion lists and UTM builder data to understand performance.
Pause, enable, create and budget edits are proposed as reviewable changes, then approved and audited.
No invented matchesEvidence before action
Clicks, conversions and matching logic are visible, including what could not be attributed.
Create consistent campaign links and keep source, medium, campaign and content clean.
Recommendations explain why a change is suggested and show confidence before asking you to act.
Draft, submit, approve or reject, apply, and keep a record of who changed what.
If platform sync is not ready for a workflow, enter spend manually to keep ROAS useful.
The product combines attribution views, raw event lists, recommendations, permissions and audit history.
Decisa separates what is attributed from what is not. That makes the dashboard less flashy, but more trustworthy.
Campaign edits are not automatic. They become drafts your team can inspect before applying.
AI recommendations are useful only when the evidence is visible. Decisa shows the reasoning before the action.
Plans should match tracked order volume, ad-account control needs and team permissions. The product is built to be reviewed before it acts.
For teams that need first-party click capture, server-side conversions and ROAS views.
For teams that want attribution plus reviewable campaign changes and AI Advisor.
For teams connecting ad accounts and managing proposed campaign edits with approval flow.
No autonomous campaign changesEvidence before approvalExportable event data
No. Decisa can suggest changes and prepare drafts. Your team reviews, approves and applies them through changesets.
No. Decisa connects clicks and conversions when compatible visitor_id and click context exist. Unmatched conversions remain visible as unattributed.
The pixel is a front-end snippet, but server-side conversion tracking requires your backend to POST conversion events to Decisa.
The app supports OAuth connection flows for Google, Meta and TikTok. Campaign edits should be handled through reviewable changesets and audit logs.
You can enter ad spend manually so ROAS views remain useful while platform sync coverage evolves.
Start with the first-party pixel and server-side conversions. Turn recommendations into reviewable drafts when your team is ready.