
Ads Suite
Automated Campaigns: Build and Preview Campaign Templates from a CSV Feed
Automated Campaigns is a CSV-based templating tool. You upload a CSV feed, create an automation mapping columns to campaign fields, set filter rules, and preview the draft objects it would generate. Learn the current capabilities, the CSV size limit, and how preview differs from live creation.
Automated Campaigns: Build and Preview Campaign Templates from a CSV Feed is part of the authenticated Revenue Proven workspace. The current sidebar label is Activate > Automations. Feeds and JSON templates generate local previews; no worker automatically publishes live LinkedIn campaigns. The page is documented against the current production interface rather than a mockup or an obsolete navigation path.
What this guide covers
Automation detail binds sample feed rows into a JSON campaign template and previews the filtered generated objects. The controls and values shown depend on the signed-in workspace, its connected providers, plan entitlements, member role, and any data already synchronized or seeded for demonstration.
Use this article to understand the page’s purpose, where its data comes from, and the safest next action. Revenue Proven separates read-only analysis from explicit mutations so that opening a page never implies that an external write has occurred.
Current product workflow
Automation detail binds sample feed rows into a JSON campaign template and previews the filtered generated objects. This screenshot was captured from the current production route while signed in to the populated Shawn Brown demo workspace.

Review feed row count, filter rules, distinct campaign and ad-set fields, template placeholders, and the preview output before using any generated draft workflow. Interface labels and availability follow the current plan, role, connection, and workspace context.
Preview runs locally against seeded sample rows. Materialization and LinkedIn publishing are not automatic. Confirm the active workspace and understand whether a control reads data, changes local configuration, or calls an external system before using it.
Data, access, and permissions
Preview runs locally against seeded sample rows. Materialization and LinkedIn publishing are not automatic. Real synchronized values can change after a scheduled sync, while seeded demo rows are deterministic examples and must not be presented as customer benchmarks.
Feature availability is enforced on the server. A button may be hidden or disabled when the workspace lacks the required plan, add-on, OAuth scope, account role, owner permission, or rollout flag. Team membership never bypasses owner-only write guards.
Operational guidance
Before changing anything, verify the active workspace, selected account, date range, provider filters, and saved configuration. If a screen looks incomplete, allow asynchronous charts and grids to finish loading and check Workspace > Connections for sync health.
Use read-only preview, filter, export, and drill-down controls freely. Treat controls labelled Save, Submit, Apply, Resume, Sync, Send, Publish, Delete, Reconnect, or Regenerate as state-changing actions and confirm their effect before continuing.

