> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flokitai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Assisted Meta and Stripe launch

> The practical FloKit-led setup for a first controlled Meta campaign and Stripe checkout.

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.

<img src="https://mintcdn.com/flokitai/_yCXj6dyS1aLllX7/images/guides/assisted-launch-map.svg?fit=max&auto=format&n=_yCXj6dyS1aLllX7&q=85&s=b38fd4758566f37c3180090683565b2c" alt="FloKit-assisted launch setup" width="1600" height="620" data-path="images/guides/assisted-launch-map.svg" />

## What the customer prepares

| Area   | What is needed                                                                                                                                                                                                          |
| ------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Meta   | A Meta Business administrator, a client-owned ad account dedicated to FloKit-managed campaigns, the Facebook Page, the linked Instagram Professional account when used, and the website Dataset or Pixel                |
| Stripe | A Stripe administrator, a matching secret key and publishable key for the selected environment, an active recurring Product and Price, and decisions about Stripe Billing, trial terms, promotion codes, and Stripe Tax |
| Launch | The first target market, language, daily budget cap, Facebook or Instagram placements, initial offer, and activation approver                                                                                           |

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

<Steps>
  <Step title="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.
  </Step>

  <Step title="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](/guides/meta-managed-account-setup).
  </Step>

  <Step title="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](/guides/meta-system-user-setup) and
    [Meta Pixel and Conversions API setup](/guides/meta-pixel-capi-setup).
  </Step>

  <Step title="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](/guides/stripe-direct-setup).
  </Step>

  <Step title="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.
  </Step>
</Steps>

## 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.