Meta Autolaunch
Template-based campaigns through a browser extension, personal buyer keys and current Meta statuses in the tracker.
Autolaunch uses the Micator · Autolaunch extension in the browser profile where you are signed in to Meta. Templates, keys, history and Facebook automation rules are managed in the tracker. A Micator license with Autolaunch is required; contact support for access.
Personal key and profile
- Open Autolaunch → Keys in the tracker using your own account.
- Create a key for the browser profile. Save it: the full key is displayed only once.
- Download the extension from the tracker and install it in that browser profile.
- Open Logs and settings («Логи и настройки») in the extension, enter your tracker's HTTPS address and key, then save and reconnect.
- Open Ads Manager in the same profile, wait for it to load, select the ad account in the extension and sync accounts.
Each buyer uses their own key. Data belongs to that user and profile. A team lead can see their permitted team; an administrator can see the workspace. Permissions in Micator do not grant additional Meta permissions.
The Micator key grants limited Autolaunch access. The Meta token stays in the browser profile and is not sent to the tracker. You may need to enter the session key again after restarting the extension. Revoke keys you no longer use.
Template and creation
Save campaign settings as a template or fill the form from an existing template. Check the account, Facebook page, objective, country, placements, URL, creative and budget. A lifetime budget requires a future end date. Form dates use the browser time zone; Meta reporting uses the account time zone.
Start with a draft and paused objects. Open the result in Ads Manager and review the campaign, ad set and ad. Publishing submits it to Meta review; enabling delivery can incur spend. A successful creation request does not mean approval or delivery.
Templates do not contain tokens or creative files. The selected profile must have the required files and page access.
History and current statuses
History keeps the creation result separate from the current Meta status. While the profile is open, the extension checks saved campaigns and ads approximately once a minute, up to 20 campaigns per cycle. Larger histories are checked in rotation.
The panel shows campaign and ad statuses and the last successful check time. If Meta is temporarily unavailable, the last snapshot is retained and marked as failed or stale. Rejection is a Meta decision, not a failure to save history in Micator. Unpublished drafts may be unavailable through the Graph API; check them in Ads Manager.
Connection issues
Reload Ads Manager in the same profile and check the session and account permissions. Then reconnect the extension. For a key error, check the tracker address, license and your key's validity. Closing the profile stops status updates and rule execution.
After an uncertain response, check Ads Manager and history before creating again: the request may have completed before the connection failed. Moderation, missing payment methods and account restrictions are handled in Meta.