Skip to main content

​
Check a published Flow

Select the correct App and use its published URL. Check the page on desktop and mobile, complete each relevant questionnaire path, and confirm the final destination. For a paid offer, verify price, currency, billing interval, trial terms, and the access the purchase provides. Use the intended payment-provider test mode for setup. Obtain approval before any live charge. Confirm payment in FloKit rather than relying on a browser redirect. See Stripe setup, Paddle notifications, and entitlements.

​
Review existing Initiatives

An Initiative can be draft, active, paused, or stopped. The available controls depend on its current state and your permissions.
If FloKit reports that paid delivery could not be fully confirmed, do not assume spending has stopped. Review the connected advertising account and resolve the reported problem with your FloKit contact. Pausing an Initiative does not unpublish its Flow or disable checkout.

​
Review reporting

Use the same App, date range, time zone, and audience or traffic filters when comparing reports. Separate manual testing from the paid campaign results you are evaluating. Advertising clicks, page visits, questionnaire participation, and purchases describe different events and should not be assumed to have identical counts. Check connection health and the latest available data before interpreting a missing value as zero. For a discrepancy, retain the date range, filters, relevant campaign or Flow reference, and a redacted screenshot. Do not send customer-level exports or questionnaire answers in a support request.