Skip to main content
FloKit leads this setup. For the initial web acquisition test, the customer does not need to add a new SDK or build a separate integration. Reserve one two-hour working session with the people who can administer Meta and Stripe. If that is inconvenient, nominate one technical owner and FloKit will work directly with that person. FloKit-assisted launch setup

​
What the customer prepares

The customer keeps ownership of both the Meta ad account and Stripe account. FloKit receives the permissions required to configure and operate the agreed launch.

​
What FloKit handles

FloKit will:
  • provision the Company and App workspace;
  • connect and validate the selected Meta and Stripe accounts;
  • select and qualify the exact Meta ad account, Page, Instagram identity, and Dataset;
  • import the Stripe Product and Price catalog;
  • map the first subscription offer;
  • provision the Stripe webhook back to FloKit;
  • configure the approved Pixel and Conversions API event path;
  • prepare the first Meta campaign, ad set, creative, and ad in a paused state;
  • run the controlled checkout and campaign-readiness tests; and
  • report any remaining provider-side blocker with a clear owner.

​
Launch phases

1

Confirm the first test

Agree on one market, one language, one offer, one daily cap, and the Meta placements to use. A small initial budget is sufficient for the technical canary.
2

Prepare the Meta account

Create or confirm the dedicated client-owned ad account, add its payment method and spending limit, and share the required Page, Instagram account, and Dataset with FloKit.Follow Prepare a Meta account for FloKit.
3

Connect Meta delivery and signals

FloKit completes the production system-user connection and selects the exact account and identities. The browser Pixel and server-side Conversions API are configured separately against the selected Dataset.See Connect Meta Ads with a system user and Meta Pixel and Conversions API setup.
4

Connect Stripe Direct

Confirm the subscription Product and recurring Price, decide whether Stripe Tax is active for the launch, connect the matching Stripe keys, sync the catalog, provision the webhook, and run a test checkout.Follow Connect Stripe Direct.
5

Run the canary

FloKit verifies that the campaign destination, Pixel and CAPI events, checkout, Stripe webhook, and reporting path work together. Meta objects remain paused until the agreed activation approval.

​
Ready to activate

The first launch is ready for approval when:
  • the selected Meta account, Page, Instagram identity, and Dataset are visible and validated in FloKit;
  • the Stripe connection is ready, its catalog is synced, and its webhook is provisioned;
  • the selected recurring Price is mapped to the first offer;
  • one controlled test checkout is reflected in FloKit from the Stripe webhook;
  • the campaign hierarchy has been created and read back in a paused state; and
  • the daily cap and activation owner are recorded.
A custom domain can be added before or after the initial test. The FloKit fallback domain is available immediately, so DNS does not need to block onboarding.