How do I connect a custom checkout to Decisa?
If your store or payment platform isn't one Decisa connects natively, open Custom Site under Integrations: install the pixel, then have your checkout's backend report each order to Decisa using your Site key — the page's AI prompt helper writes that code for you.
Before you start
- A workspace with the Attribution module active.
- Access to the website your buyers land on (or someone — human or AI assistant — who can paste a snippet into it).
- Someone who can touch your checkout's backend code. The page generates a ready-made prompt, so an AI coding assistant counts.
- The Admin role if you need to view the Site key — other members see a notice asking an admin instead.
Steps
Open Custom Site
Go to Sidebar → Integrations → Custom Site. The page is a two-step guide: Choose pixels, then Install & track.
Choose your pixels
Pick one or more pixels — the destinations this site reports to. Every snippet and example on the later steps updates to match your selection.
Use Automatic for the full integration
Keep Automatic (marked Recommended), then click Copy prompt and paste it into Claude, ChatGPT, or Cursor. The prompt points the assistant to Decisa's live Markdown installation guide, includes the selected pixel keys, API base, and server key, then asks it to install
pixel.js, preserve thedcs_vidvisitor id, and send real backend conversions/events.Use Manual when you want to code it yourself
Pick Manual to see the technical guide URL, browser snippets, your Site key, conversion examples, and the
/eventssignal reference. Treat the Site key like a password; it belongs only in server-side code and must go on every conversion/event request your backend sends.Confirm events are arriving
On the Live events card, click Send test event. The status flips to Receiving events and the test appears in the list below within seconds.
What happens next
- Each order your checkout reports appears in your conversions list, joined to the click and campaign that drove it.
- Live events keeps showing the last five clicks captured by your pixel, refreshing automatically.
- Your ROAS report starts crediting real revenue to campaigns.
- The technical guide lives at
https://api.decisa.ai/v1/docs/attribution-installation.mdin production and is the source of truth for/conversions,/events,/identify, visitor continuity, and event quality fields.
Gotchas
Amounts must be sent in whole cents — 19990 means R$199.90. If your backend sends a decimal like 199.90 in the wrong field, the order still arrives but with no revenue, and your ROAS report shows conversions worth nothing. The copied prompt spells this out — don't edit that part.
The rotate option next to the Site key invalidates the current key immediately. Orders sent with the old key are rejected until your backend is updated — rotate only when you can update both at once.
If the visitor's cookie is missing (ad blockers, purchases from another device), the order is still recorded — it just isn't linked to a click. A few unlinked conversions are normal.