How the Campaigns area organizes your operation

Where Campaigns fits in the operation

Campaigns is where the team monitors what is published on Meta Ads and Google Ads for the selected client. It brings campaigns created by Agencify and campaigns imported from the providers into one operational view.

This view does not replace the ad account. Agencify reads and synchronizes data, organizes agency context, and provides authorized actions. The provider remains the external destination where delivery actually happens.

Why this matters

An agency needs to compare platforms, periods, and states without losing sight of the client. Bringing that view together reduces tool switching and makes it easier to see where there is spend, a result, a failure, or a pending decision.

The same centralization increases responsibility. Changing status, budget, or structure can produce a change in the provider. The client, date range, origin, and campaign state therefore need to be confirmed before an action.

Mental model

Think of Campaigns as a control desk. The table shows inventory and metrics for the current context. Filters and columns change how that inventory is analyzed. Operational actions change a campaign only when the person's role, subscription, integration, and current state allow it.

Client and date range

The selected client defines which campaigns may appear. The date range defines the metrics window. Changing either can start a new read and synchronization, so a comparison is meaningful only when the context is clear.

Created and imported campaigns

Campaigns created by Agencify preserve a configuration that may support editing or duplication in the product. Imported campaigns were discovered in Meta Ads or Google Ads and may have limited structural actions. Origin explains why two similar rows do not always provide the same controls.

Data and actions

Viewing metrics and expanding the hierarchy are read activities. Pausing, activating, adjusting budget, editing, or deleting can change the provider. Some operations run in the background and are complete only after the result has been confirmed again.

A realistic scenario

At the start of the day, a manager selects a client and the current week. She filters active campaigns, compares Meta and Google, and expands a campaign to understand its ad sets and ads. A campaign created in Agencify needs an adjustment, while an imported campaign is used only as a reference. Before changing budget, she confirms origin, state, and impact in the correct context.

Main capabilities

• Client and date range selection to define the analysis context.
• Search, quick and advanced filters, sorting, and column settings.
• Meta Ads and Google Ads metrics, with fields that vary by platform.
• Hierarchy expansion for reviewing ad sets and ads.
• Synchronization and refresh of available local data.
• Status, budget, edit, duplicate, and delete actions when permitted.
• Related access to History, Reports, and AI recommendations.

Limits and recovery

Metrics can arrive at different times or depend on pagination, caching, and provider availability. An expired integration, an inaccessible account, or the wrong date range can produce partial data. Imported campaigns do not have the same editing contract as campaigns created in Agencify.

If an action remains in progress or fails, do not repeat it immediately. Refresh the view, review notifications and History, and confirm the state in the provider. If the data looks wrong, review the client, date range, platform, and integration before concluding that a real change occurred.

Up next

After understanding the Campaigns overview, learn about experiment groups, which organize variations for comparison and provide a different lens on resources, budget, and performance.