Setting up Flowpeek: how to prepare your store and sign off the setup

1. Start with the store and your team's questions.

Write down the store addresses, the e-commerce platform and the person responsible for technical changes. Include separate domains for language versions and currencies. This matters more than a list of every possible report: it tells us which store the results should come from and what needs to be connected.

Pick two questions to start with. For example: which devices need a checkout review, and which products attract interest without sales? Add the ad accounts you use and your customer communication platform. Not every connection has to be part of day one. Set the order based on those questions.

• Domains, store platform and currencies.
• People responsible for the store, ads and communication.
• Two questions you want answered in the first week.

2. Agree on what will be measured.

Browser tracking describes recorded visits, pages and interactions. The store integration can deliver supported information about orders and their changes. These sources complement each other, but receiving an order doesn't reconstruct the customer's earlier clicks. The scope depends on the platform and how the connection is configured.

Agree with us whether tracking runs on a Flowpeek domain or on your own domain's infrastructure. We check compatibility with your store's consent mechanism separately. A custom domain and server-side tracking don't mean every behavior will be available. At sign-off you need a clear answer: what data arrives, since when and with what limitations.

3. Walk through one identifiable test visit.

Note the test start time and the device. Open a category, then a product, add it to the cart and go to the checkout form. Use a test scenario agreed with your team. Check together whether the available events match the actions actually taken and don't show up twice.

In live traffic you're looking for confirmation of activity; in event analytics, for specific actions. A page view doesn't always replace a checkout-start event. If something is missing, write down the page, time, device and the step you took. A description like this makes checking the setup much faster than a report that “the report is empty”.

4. Confirm the order, its amount and currency.

If the test includes an order, compare its ID, time, currency and value with your store admin. Find out which statuses and adjustments the integration supports. Don't treat the mere presence of an amount as full confirmation: what that amount means and when it was updated matter just as much.

Separate two questions: did the order arrive, and could it be linked to a visit and a traffic source? An order with no assigned channel can still be a valid sales record. When comparing tools, keep the same period and currency. If there's a difference, check the definitions and sync status first.

5. Note the limits of history and hand the dashboard to your team.

Ask which historical data the integration delivered. Importing past orders doesn't automatically give you journeys from before the tracker went live. Mark the tracking start date in your notes so your first week-over-week comparison doesn't set a full period against a few days of data collection.

Finish the sign-off with a short list: confirmed data, known limitations and items to check. Decide who will come back to the reports. In your first month you get a consultation with the Flowpeek team — bring questions about your store and one example of a discrepancy, rather than trying to cover every feature at once.