Anata Intelligence
Shipping OS
Advertising integration
Connect Meta advertising data to your workspace.
Authorize a Meta Ads account, select the ad account you manage, and bring supported campaign performance into Anata Intelligence.
One connected path from channel activity to the work your team carries forward.
What connects
The context that makes the workflow useful.
The connection carries the specific order, account, campaign, or shipment context the next step needs.
01
An authorized Meta ad account
02
Supported campaign performance
03
Account connection and sync status
04
Advertising context in Anata Intelligence
How it moves
A clear handoff from connection to action.
1
Authorize
Sign in through Meta and grant access to the applicable advertising account.
2
Select
Choose the ad account to connect. The account identity is checked before it is bound to your workspace.
3
Review
Follow the first sync and use supported campaign reporting when data is available.
What it changes
Less fragmented work after the connection.
A first supported channel for a new software subscription
Meta performance visible in the connected workspace
A clear connection and first-sync status
Before you connect
Have these pieces ready.
- A Meta advertising account
- Permission to authorize and select that ad account
- The workspace and plan you want to use
A practical boundary.
A new subscription trial starts only after the provider identity is verified and the first supported data channel is connected. Available data depends on the permissions granted and the account's reporting history. This connection does not promise automated changes to Meta campaigns.
Questions
What teams usually want to know.
Can Meta Ads start my software trial?
Yes. Meta Ads is an eligible first data channel for a new subscription. The 14-day trial begins when the verified account is connected, not when you create a login.
What if this ad account is already connected elsewhere?
The same account cannot be connected to another workspace at the same time. You can request to join the workspace that already owns the connection.
Continue from here