— queue · uploaded to FB in the last 14 days
Ad Sets
Ad Set
Ad Setup
Ads · 0 creatives for this ad set
| Creatives | Ad set | Campaign | User | Ads | Launched | Start | Time | Status |
|---|
| Creatives | Ad set | Campaign | User | Ads | Launched | Start | Time | Status |
|---|
Pre-filled on every new launch of this ad account. Each value can still be changed per launch.
Where each task goes (Launch map) and the ABO budget of the chosen product.
One value for the whole ad account; a Launch map rule can override it. The token reads Facebook pages but not Instagram names.
How the new ad set is named and when it starts.
What the platform may do in Meta and in Slack for this ad account, and when Reports call an ad a winner or a loser.
Writing to Meta and the tasks source (media library or Slack) apply at once (owner/admin); Pixel source is saved with Save.
For the whole organization, not only this ad account: your own Slack bot for report reactions and a Telegram chat for failed launches and token warnings.
Used by Insights → Reports for this ad account.
One organization on the platform, its workspaces (one Meta connection each) and the people who work in them.
Who can open this panel, which ad accounts they see and what they may do. An invite is a one-time link valid 7 days; deactivating a member ends their sessions at once.
A role is a preset of permissions that an Admin can edit here; any member can still be adjusted per section on top of the role. The Owner is one person, cannot be removed or demoted — ownership is transferred as a separate confirmed action.
Saving applies the preset to members of that role who have no custom permissions; custom ones keep theirs.
What this panel did and who did it: launches and duplicates (with Meta's answer), setting changes, invites, role changes, account grants, deactivations.
Newest first; the last 500 entries are kept.
The organization's plan and usage, the details printed on its invoices, and the invoices themselves.
—
Printed on every invoice as the buyer. An issued invoice keeps the details it was issued with.
—
Open one to see it in full; print it or save it as PDF from the browser.
The documents that apply to Ad Launch, who accepted which version and when, and your own choice about marketing e-mails.
When a document gets a new version, everyone it applies to is asked to accept it once, at their next visit.
Your own choice, recorded with the date. Ad Launch sends no marketing e-mails today; invitations and password resets are service e-mails and do not depend on it.
—
| Member | Terms of Service | Privacy Policy | Data Processing Agreement | Marketing e-mails |
|---|
Every client organization on this platform. Suspending blocks its members at once and pauses its background work; deleting removes its data from Ad Launch. Neither touches anything in Meta.
—
| Organization | Owner | Members | Ad accounts | Launches · month | Meta | Plan | Last activity | Status | |
|---|---|---|---|---|---|---|---|---|---|
| Loading… | |||||||||
Organizations created, suspended, resumed, deleted and self sign-ups. Only platform admins see this log.
Your own sign-in, details and devices. Organization-wide settings live under Organization.
How your team sees you in launches, the audit log and invites.
You sign in with this address; password resets go to it. Changing it needs your current password.
Changing it signs out every other device; this one stays signed in.
Browsers signed in to your account. A session ends after 30 days without a visit.
A JSON file with your account, memberships, sessions and the audit entries made by you.
Delete your account from this organization. This cannot be undone.
You are the first user. Connect Meta and invite your team afterwards.
Use the email and password of your Ad Launch account.
You become the owner of a new, empty organization. Connect Meta and add an ad account next.
To keep using Ad Launch, accept the current version of:
As an owner or admin you accept the Data Processing Agreement on behalf of the organization.