Bïrch Nested Rule Deployment for New Client Ad Accounts (Onboarding)

Bïrch Nested Rule Deployment for New Client Ad Accounts (Onboarding)

1. 01

   Connect the client's Meta, Google, TikTok, Snapchat, and Instagram ad accounts inside the Bïrch workspace

   Create a dedicated workspace per client so reporting and rule scope stay isolated. Confirm each platform shows a live connection before building any rule, since a broken token silently disables every downstream automation.

2. 02

   Open the Explorer and pull 30 days of historical campaign data

   Use Explorer to baseline spend, CPA, and creative performance before automation touches the account. This baseline becomes the reference point the agency cites in the first client review.

3. 03

   Draft the rule set using pre-built rule strategies as the starting template

   Start from a pre-built strategy, then add nested conditions (for example: pause ad when CPA exceeds target AND spend is above threshold AND creative age is past 14 days). Nested logic is the feature that separates Bïrch from single-condition rules in other tools.

4. 04

   Attach multiple actions to each rule rather than a single pause

   Pair a pause action with a Slack notification and a budget shift where the account supports it. Multi-action rules cut the number of separate rules the delivery team has to maintain per client.

5. 05

   Load new creative through the Launcher in bulk

   Use bulk ad launching to push the full creative batch across platforms in one pass. Tag naming conventions at launch so the creative insights view (top ads, fatigued ads) can segment by concept later.

6. 06

   Define custom metrics that match the client's reporting language

   Build custom metrics in the workspace so the client sees the numbers they contracted for, not raw platform defaults. This is what makes the monthly report defensible on a retainer.

7. 07

   Wire automated reports and Slack alerts to the client channel

   Schedule automated reporting and route rule-trigger alerts into the client's Slack channel. Confirm the Google Sheets, AppsFlyer, or Hyros integration is passing data if the client relies on those sources.

8. 08

   Run a 7-day supervised window before handing rules to autopilot

   Review the Activity page daily during week one to catch rules firing on the wrong conditions. Only after the agency signs off should the rule set run without daily review.