Getting started: from signup to verified events

This guide takes you from a fresh account to verified conversion events flowing to your ad platforms. Most stores finish in under 30 minutes. The path is always the same five steps, in this order:

1. Create your workspace
2. Add your website and install the tracking snippet
3. Connect your ad platforms as destinations
4. Send your orders and leads
5. Verify events end to end

1. Create your workspace

Everything in RoasProof lives inside a workspace: websites, platform connections, API keys and event history. One workspace per brand is the rule of thumb; agencies create one workspace per client so credentials, reporting and billing stay cleanly separated.

Sign up, name your workspace after the brand, and you land in the dashboard.

2. Add your website and install the snippet

Under Websites, add the site you want to track: a display name, the primary domain (without protocol, e.g. mystore.com), and the list of allowed domains: every origin that may send tracking data. Include www and any checkout subdomains here, or events from those pages will be rejected.

Saving the website generates a site key. The Setup & API keys page shows the ready-made snippet for each active website; add it to every page of your site, just before the closing </head> tag:

<script async src="https://app.roasproof.com/js/track.js" data-site="YOUR_SITE_KEY"></script>

The script records page views, link clicks and form submits automatically, and captures UTMs, click IDs (fbclid/gclid/ttclid) and the Meta _fbp/_fbccookies on the visitor's first touch. Placement details, the JavaScript API, consent gating and first-party domains are covered in Install the tracking script.

3. Connect your ad platforms

Under Destinations, create one destination per platform per website. Each destination is a pair of credentials that lets us deliver events on your behalf:

• Meta: Pixel ID and a Conversions API access token. See Connect Meta via the Conversions API.
• Google Ads: Ads customer ID, conversion action ID and developer token. See Connect Google Ads.
• TikTok: pixel code and an Events API access token. See Connect TikTok via the Events API.

A destination only receives events while its status is active. You can pause a destination at any time without touching the others.

4. Send your orders and leads

Page-level activity arrives through the snippet on its own. The conversions that matter (purchases, leads, signups) need a connection from wherever orders happen:

• Shopify: install the RoasProof app and authorize your store, and orders and checkouts flow in automatically. See Connect a Shopify store.
• WooCommerce: install the RoasProof plugin, paste your API key and site key, and paid orders send themselves. See Connect WooCommerce.
• Anything else: one authenticated request to the events API from your backend.

POST https://app.roasproof.com/api/v1/events
Authorization: Bearer YOUR_API_KEY

{
  "event": "purchase",
  "event_id": "purchase_10023",
  "value": 249.00,
  "currency": "EUR",
  "user_data": {
    "email": "[email protected]",
    "visitor_id": "value of the _sgnl_vid cookie"
  }
}

API keys are created on the Setup & API keys page and shown exactly once, so copy it immediately. The full payload reference and the visitor_id join that recovers browser identifiers are in Send orders and events from your backend.

5. Verify events end to end

Open Conversion events and watch your first events arrive. Each row shows the destination, the event_id and a delivery status; opening an event shows the exact payload sent and the platform's response. For Meta, add a test event codeto the destination while validating, and confirm the events in Events Manager's Test Events tab.

Only go live on real budgets once you have seen sent events for every destination and confirmed deduplication against your pixel. If anything shows failed, the error is stored on the event, and Verify delivery and troubleshoot failed events walks through the common causes.

What happens from here

From the moment events flow, every conversion is matched to the click that caused it, enriched with hashed identifiers, delivered with retries, and deduplicated against your browser pixel via a shared event_id. The signal-quality dashboard shows delivered vs. failed counts and match rates per destination. Check it after the first 24 hours, then let it run.