Developer overview

Flowfy receives events from your store, works out where each order came from, and forwards those events on to your advertising platforms. This section covers how to send them yourself.

If your store is on Salla you do not need any of this — the Flowfy app installs the tracking script for you. These pages are for custom storefronts, headless setups, and server-side tracking.

Two ways in

Most stores use both: the SDK for what the shopper does, and the API for what happens after the order leaves the browser.

Three things to know first

A source is your store. Every event belongs to one source, and you create it in Flowfy before sending anything.

A write key identifies that source. It is the only credential involved, it lives on the source's page in Flowfy, and it goes in every request. It is not a secret in the browser — it names your store, it does not grant access to your data — but keep your server-side copy out of public repositories anyway.

An event is one thing that happened. It has a name and a set of properties. The names are fixed: Flowfy matches Order Completed to a purchase on Meta, TikTok and Snapchat, so use the names from the event reference rather than inventing your own.

Where events go

your store  →  edge.flofy.co  →  Flowfy  →  Meta / TikTok / Snapchat

Events are accepted at https://edge.flofy.co and answered immediately, before any processing. A success response means the event was received, not that it was understood — open Live events on the source's page in Flowfy to see what actually landed.

Property names use snake_case

Every property in these docs is lower-case with underscores: order_id, product_id, payment_method. Flowfy reads order_id; it does not read orderId, and an order sent that way arrives with no order attached to it.

Next

• Install the SDK — the script tag and the load call
• Tracking — track, identify, page and the rest
• Event reference — all 30 events and their properties
• HTTP API — sending events from a server